From owner-freebsd-current Sun Dec 17 00:38:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA06703 for current-outgoing; Sun, 17 Dec 1995 00:38:41 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA06678 Sun, 17 Dec 1995 00:38:32 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id JAA15769; Sun, 17 Dec 1995 09:30:06 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.6.12/8.6.12) with SMTP id JAA00787; Sun, 17 Dec 1995 09:22:15 +0100 Date: Sun, 17 Dec 1995 09:22:15 +0100 (MET) From: Andreas Klemm To: current@FreeBSD.org, hackers@FreeBSD.org cc: cracauer@wavehh.hanse.de, jkh@FreeBSD.org Subject: FreeBSD-current-stable ??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk Hi FreeBSD core team ! [ Possibly I'm speaking for many other people here ] Generally I would be interested to help testing and debugging new FreeBSD-current features. But when reading the -current mailing list, FreeBSD-current, so to say FreeBSD-2.2 in it's early days, seems to be an instability nightmare. Perhaps this expression is a bit oversized, but please understand my point of view. I read in -current very often messages like, can't boot, can't compile, unreferenced symbols, ... and so on ... Nothing on which you would want to run your home system (news, mail, www). Since I only have one PC and one harddisk, as many other people, it's not possible for me to switch to -current, because I need a certain level of stability. When speaking with people like Martin Cracauer, then I get the impression, that possibly more people would be interested to help in FreeBSD developement. Perhaps developing additional features, too. But they only have one machine, which shouldn't get into a very unstable state. So how could one attract more people, to work on the bleeding edge, without loosing stability too much ??!! Could FreeBSD-current developement be made more attractive to more people by splitting -current into 2 branches ? FreeBSD-current FreeBSD-experimental The FreeBSD-experimental tree should be for typical alpha software for equipped hackers with two systems or two harddisks ... If there is a brand new driver with a risk of crashing the systemm it should be added and tested there. If the new driver doesn't cause crashes or such it shoud move to FreeBSD-current, to introduce it to a larger audience that is willed to test the bleeding edge. Such newly introduced feature should be tested well in -current and should get to a stable state in -current. If it is stable, then a) it can be added to the -stable branch. b) you have a stable -current with the newest "tested" features This would have the advantage, that more people could work on -current, since it could be more stable then now. And ... the developers would work on a developement platform, that has incorporated the newest features. What about that ? Too much admin overhaead ? Perhaps that bit more on administration overhead regarding the newly introduced source branch can be justified with a certain increase of FreeBSD-current developers ?! Would it be possible to start with such a "beast" by simply leaving current as it ->> "experimental branch" and by introducing something like a FreeBSD-beta branch and adding current-changes to it, that are known to be stable ? So you'd have a release branch - the last good one stable branch - fixes for last -release and stable new features from beta branch beta branch - new features, something like SNAPSHOT in it's early hours ;-) alpha (current) branch - current for hackers as it is Would/could you agree with such a change ? If you would offer a more stable -current as described, I'd immediately switch to sup the new beta-branch to see what's new and to give feedbacks... So I can't :( Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Sun Dec 17 00:52:55 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07488 for current-outgoing; Sun, 17 Dec 1995 00:52:55 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA07480 for ; Sun, 17 Dec 1995 00:52:52 -0800 (PST) Received: from mordillo (oberon.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id JAA14082; Sun, 17 Dec 1995 09:52:39 +0100 (MET) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id XAA06983; Sat, 16 Dec 2000 23:58:42 +0100 From: Thomas Graichen Message-Id: <200012162258.XAA06983@mordillo> Subject: Re: todays -current To: hsu@clinet.fi Date: Sat, 16 Dec 100 23:58:41 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <199512161606.SAA03529@katiska.clinet.fi> from "Heikki Suonsivu" at Dec 16, 95 06:06:15 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > > BTW, I would like to get ctrl-alt-del to shutdown the machine cleanly for > problems like this to avoid fsck on next boot, should this be possible? We > use pcvt, if that matters. > i think in pcvt there is something like cpu_reset (or was it reset_cpu ?) which is called if ctrl-alt-del is pressed and the ctrl-alt-del options is set in the config - now (i think) you should try to replace this with shutdown_nice - should work (but can't guaranty - i use syscons - and mostly X :-) t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-current Sun Dec 17 01:10:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA08852 for current-outgoing; Sun, 17 Dec 1995 01:10:56 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA08820 Sun, 17 Dec 1995 01:10:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id BAA07750; Sun, 17 Dec 1995 01:10:07 -0800 To: Andreas Klemm cc: current@FreeBSD.org, hackers@FreeBSD.org, cracauer@wavehh.hanse.de, jkh@FreeBSD.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Sun, 17 Dec 1995 09:22:15 +0100." Date: Sun, 17 Dec 1995 01:10:07 -0800 Message-ID: <7748.819191407@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > When speaking with people like Martin Cracauer, then I get > the impression, that possibly more people would be interested > to help in FreeBSD developement. Perhaps developing additional > features, too. But they only have one machine, which shouldn't > get into a very unstable state. > > So how could one attract more people, to work on the bleeding > edge, without loosing stability too much ??!! I think the answer is pretty simple: People committing to -current need to get their acts together and stop destabilising it so much. Yes, that's a somewhat sharply worded statement, but I think that the split into 2.1 and 2.2 has been taken by some to be implicit permission for a "free for all" in -current, and that was NEVER the intention of that branch! If you've got something truly whacked-out experimental to bring in then you're supposed to test it out on your own machine(s) to the level where it, as an absolute minimum, does not make the system unusable. If you can't reasonably guarantee this, then it should stay in your local tree until you can. As Andreas notes here, having an unstable -current is very counter-productive and only leads people away from wanting to run it at all (I haven't updated my own -current system for a week or so, for exactly this reason). That somewhat defeats the purpose of -current, which is to be a *final* testing ground for features. It's not a dumping ground for half-baked and untested ideas that break existing functionality. If you've got something truly left-field that you want to bring in and it doesn't effect other parts of the system as a whole, then the rules are perhaps somewhat more flexible, but this definitely doesn't apply to changes to existing features. I think that the idea of further branching of FreeBSD into -experimental and -current is not a good one, for various reasons: 1. It would only encourage more mayhem in -experimental, quickly leading to an unmanagable mess that nobody in their right minds would want to run anyway (and if that's the case, then what's the point of committing something to a central location? Just keep it in your own tree until it's ready). 2. It would fragment work even more. People would be confused as to where to commit, what with all these possible options. 3. Somebody would be stuck with merging changes between 3 branches instead of two, and two is already becoming close to unmanagable (just ask David). Sorry to be so acidic, but I really do think that this needed to be said, and messages like Andreas's here would only serve to indicate that -current is way out of control. We need to regain some of the credibility we've lost here, not make the problem even worse! Jordan From owner-freebsd-current Sun Dec 17 03:39:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA22615 for current-outgoing; Sun, 17 Dec 1995 03:39:05 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA22594 Sun, 17 Dec 1995 03:38:57 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id MAA19398; Sun, 17 Dec 1995 12:30:10 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.6.12/8.6.12) with SMTP id MAA00620; Sun, 17 Dec 1995 12:14:04 +0100 Date: Sun, 17 Dec 1995 12:14:04 +0100 (MET) From: Andreas Klemm To: "Jordan K. Hubbard" cc: current@FreeBSD.org, hackers@FreeBSD.org, cracauer@wavehh.hanse.de, jkh@FreeBSD.org Subject: Re: FreeBSD-current-stable ??? In-Reply-To: <7748.819191407@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Sun, 17 Dec 1995, Jordan K. Hubbard wrote: > > When speaking with people like Martin Cracauer, then I get > > the impression, that possibly more people would be interested > > to help in FreeBSD developement. Perhaps developing additional > > features, too. But they only have one machine, which shouldn't > > get into a very unstable state. > > > > So how could one attract more people, to work on the bleeding > > edge, without loosing stability too much ??!! > > I think the answer is pretty simple: > > People committing to -current need to get their acts together and stop > destabilising it so much. Yes, that's a somewhat sharply worded > statement, but I think that the split into 2.1 and 2.2 has been taken > by some to be implicit permission for a "free for all" in -current, > and that was NEVER the intention of that branch! Well, thanks Jordan for that statement. I don't think this isn't only a sharply worded statement, it was really needed. > If you've got something truly whacked-out experimental to bring in > then you're supposed to test it out on your own machine(s) to the > level where it, as an absolute minimum, does not make the system > unusable. If you can't reasonably guarantee this, then it should stay > in your local tree until you can. I'd love to see this to become true. > As Andreas notes here, having an unstable -current is very > counter-productive and only leads people away from wanting to run it > at all (I haven't updated my own -current system for a week or so, for > exactly this reason). So you should have raised your voice, too, Jordan, weeks and perhaps months ago ;-) Perhaps you remember the German phrase "Ist der Ruf erst ruiniert, dann lebt's sich voellig ungeniert" ;-) Concerning FreeBSD it means, that Unix engaged people like Martin, come to the clue, that -current developement isn't manageable, because you have an instable basis. What's even worse, Martin is one of our local Unix gurus in de.comp.os.unix. He is someone who "talks no shit". I think two months ago I got a report from him, that tries to compare the different PD Unixes .... I remember some statements, where he talks about the problem, that it's impossible to share the current developement, because it's done on an unstable system. And if you don't have two system, a production and a test (current) system, then you are stuck on release. I think other people may have been come to the same conclusion. You have the power to change this. I think it's really necessary. Little comparison with the dark side of Unix -> Linux :-> The have a as well a stable and a hackers branch, as we all know. When I was in the Linux camp several months (years?) ago, then I noticed, that the Linux hackers kernels are relatively stable, even the alpha stuff. Believe me or not. I think that having a well running -current branch would certainly bring - more 'happy home hackers' with - many new ideas - more feedback - a fresh drive (hehehe, join my excellent English here ;-) into the -current developement to the -current branch... I think it's a good possibility to find some new workhorses with many hp's ;-) > That somewhat defeats the purpose of -current, > which is to be a *final* testing ground for features. It's not a > dumping ground for half-baked and untested ideas that break existing > functionality. If you've got something truly left-field that you want > to bring in and it doesn't effect other parts of the system as a > whole, then the rules are perhaps somewhat more flexible, but this > definitely doesn't apply to changes to existing features. > > I think that the idea of further branching of FreeBSD into > -experimental and -current is not a good one, for various reasons: But it was perhaps a good idea, to describe the current scenario. Namely "That wishes arise because of the currnet bad situation". I already thought, that noone really wants a new branch, but people should start to think over their changes, if they are good or bad for those people, who are supping current. > 1. It would only encourage more mayhem in -experimental, quickly leading > to an unmanagable mess that nobody in their right minds would want to > run anyway (and if that's the case, then what's the point of committing > something to a central location? Just keep it in your own tree until > it's ready). > > 2. It would fragment work even more. People would be confused as to where > to commit, what with all these possible options. > > 3. Somebody would be stuck with merging changes between 3 branches instead of > two, and two is already becoming close to unmanagable (just ask David). Yeah, more work, less productivity. > Sorry to be so acidic, but I really do think that this needed to be > said, and messages like Andreas's here would only serve to indicate > that -current is way out of control. We need to regain some of the > credibility we've lost here, not make the problem even worse! So what could be done now ??? Reading Jordans comments we have to manage three things - keep the compiler happy code freeze and kick things out of current that are known to be so buggy, that the system panics or crashes or that badly influences other system services. Test them locally or in certain teams. make -current useable for a larger audience - keep the current-user happy keep in mind to add only tested things to -current which shouldn't be too difficult, since there aren't much people who are allowes to commit changes. - re-gain credibility, which means polish the somewhow damaged picture of -current Well after work is done, a big announcement in mailing lists and Newsgroups to motivate people for supping current. BTW: If you think there were too many changes made in current... So that one might come to the conclusion, that the next stable -current release will be FreeBSD-2.2-RELEASE ;-) What would you think about restarting over now. Get a fresh 2.1-stable source tree and make a project plan, what could go from old-unstable-current into the new current based on -stable without breaking it ?! If this would be done immediately, it would have the great advantage, that we all could immediately begin to sup current and to bring the new baby to work ! Then much more people could work on things like ext2fs, linux emulator and things like that. Like to hear your comments on that Good sunday you all Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Sun Dec 17 06:34:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA02629 for current-outgoing; Sun, 17 Dec 1995 06:34:36 -0800 (PST) Received: from mail.netvision.net.il (mail.NetVision.net.il [194.90.1.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA02617 for ; Sun, 17 Dec 1995 06:34:30 -0800 (PST) Received: from Burka.NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mail.netvision.net.il (8.7.3/8.6.10) with SMTP id QAA07946 for ; Sun, 17 Dec 1995 16:34:45 +0200 (IST) Message-ID: X-Mailer: XFMail 0.4-alpha [p0] on FreeBSD MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.0.4-alpha.p0.FreeBSD:951217163555:5493=_" Date: Sun, 17 Dec 1995 16:25:21 +0200 (IST) Reply-To: gena@NetVision.net.il X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: current@FreeBSD.org Subject: ep0 failure Sender: owner-current@FreeBSD.org Precedence: bulk This message is in MIME format --_=XFMail.0.4-alpha.p0.FreeBSD:951217163555:5493=_ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello! I think i sent this report before but got no answer. Whenever my machine (FreeBSD 2.2-current) starts to work under high network load (like when doing dump) the system is being disconnected from network immediatly. (even ping does not work). The only thing that fixes the problem is ifconfig ep0 up. But this helps only for a few seconds and then the problem comes back untill network load become low again. -current started to behave this way approximately starting at Dec 3. I'm using standard 3C509 combo ISA Ethernet card, which works perfectly under 2.0.5 and 2= .1. I attached to this mail my kernel config adn output from dmesg. Any help will be appreciated. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena This message was sent at 12/17/95 16:25:21 by XF-Mail --_=XFMail.0.4-alpha.p0.FreeBSD:951217163555:5493=_ Content-Description: dmesg output Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; name=dmesg; SizeOnDisk=1685 FreeBSD 2.2-CURRENT #0: Fri Dec 15 12:50:26 IST 1995 root@Burka.NetVision.net.il:/usr/src/sys/compile/BURKA CPU: Pentium (89.97-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 41943040 (40960K bytes) avail memory = 39387136 (38464K bytes) Probing for devices on the PCI bus: chip0 rev 0 on pci0:0 chip1 rev 0 on pci0:1 pci0:8: CMD, device=0x0640, class=storage (ide) [no driver assigned] vga0 rev 0 int a irq 255 on pci0:9 ahc0 rev 0 int a irq 9 on pci0:12 ahc0: 2940 Single Channel, SCSI Id=7, aic7870, 16 SCBs (ahc0:0:0): "HP C3725S 4299" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) sd0(ahc0:0:0): with 3703 cyls, 9 heads, and an average 127 sectors/track (ahc0:3:0): "TOSHIBA CD-ROM XM-3401TA 0283" type 5 removable SCSI 2 cd0(ahc0:3:0): CD-ROM cd0(ahc0:3:0): NOT READY asc:3a,0 Medium not present can't get the size Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface pca0 on isa pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp[*UTP*] address 00:60:8c:b6:f8:b1 irq 10 npx0 on motherboard npx0: INT 16 interface new masks: bio c0000240, tty c003009a, net c003049a --_=XFMail.0.4-alpha.p0.FreeBSD:951217163555:5493=_ Content-Type: text/plain; charset=us-ascii; name=BURKA; SizeOnDisk=1824 Content-Transfer-Encoding: 7bit Content-Description: Kernel config # # BURKA -- my desktop machine # # $Id: BURKA,v 1.1 1995/01/26 11:38:00 gena Exp $ # machine "i386" cpu "I586_CPU" maxusers 20 ident BURKA options "CHILD_MAX=128" options "OPEN_MAX=128" options INET #InterNETworking options GATEWAY #Host is a Gateway (forwards packets) options SCSI_REPORT_GEOMETRY options FFS #Berkeley Fast File System options NFS #Network File System options PROCFS #Process File System options QUOTA #enable disk quotas options MSDOSFS #MS DOS File System options "CD9660" #ISO 9660 filesystem options "COMPAT_43" #Compatible with BSD 4.3 options COMPAT_LINUX #Linux compatibility options SYSVSHM options SYSVSEM options SYSVMSG options UCONSOLE #X Console support options KTRACE #kernel tracing config kernel root on sd0 swap on sd0 dumps on sd0 controller isa0 controller scbus0 controller pci0 controller ahc1 device sd0 device cd0 #SCSI CD-ROMs controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ep0 at isa? port 0x300 net irq 10 vector epintr device pca0 at isa? tty pseudo-device snp 1 #Snoop device - to look at pty/vty/etc.. pseudo-device loop pseudo-device ether pseudo-device log pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device speaker pseudo-device bpfilter 4 #berkeley packet filter pseudo-device gzip #Exec gzipped a.out's pseudo-device vn --_=XFMail.0.4-alpha.p0.FreeBSD:951217163555:5493=_-- End of MIME message From owner-freebsd-current Sun Dec 17 06:37:58 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA02941 for current-outgoing; Sun, 17 Dec 1995 06:37:58 -0800 (PST) Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA02920 Sun, 17 Dec 1995 06:37:51 -0800 (PST) Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id OAA13800; Sun, 17 Dec 1995 14:36:18 GMT From: Paul Richards Message-Id: <199512171436.OAA13800@server.netcraft.co.uk> Subject: Re: FreeBSD-current-stable ??? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 17 Dec 1995 14:36:17 +0000 (GMT) Cc: andreas@knobel.gun.de, current@FreeBSD.org, hackers@FreeBSD.org, cracauer@wavehh.hanse.de, jkh@FreeBSD.org In-Reply-To: <7748.819191407@time.cdrom.com> from "Jordan K. Hubbard" at Dec 17, 95 01:10:07 am Reply-to: paul@netcraft.co.uk X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > People committing to -current need to get their acts together and stop > destabilising it so much. Yes, that's a somewhat sharply worded > statement, but I think that the split into 2.1 and 2.2 has been taken > by some to be implicit permission for a "free for all" in -current, > and that was NEVER the intention of that branch! I think me and Jordan are going to vehemently agree for a change :-) I'm in exactly this position, installed 2.1 on my new box (yes I've finally got myself a box again) and I want to upgrade to current to try out all the new toys but it's so broken that I'm going to get myself cut off from the world if it's on my one and only box. > If you've got something truly whacked-out experimental to bring in > then you're supposed to test it out on your own machine(s) to the > level where it, as an absolute minimum, does not make the system > unusable. If you can't reasonably guarantee this, then it should stay > in your local tree until you can. Absolutely, the vm headers are a good example. Peter was fixing code for a while after this commit because some parts of the tree WOULDN'T EVEN COMPILE! Was a make world done before this commit, I somehow doubt it given the glaring problems that Peter fixed. Missing the odd bug when changing the filesystem to allow 1Tb files is one thing and is what -current is for, not doing even a basic sanity check to make sure the tree still compiles is a totally different case and one we used to be a lot more stern about when it happened. I think the core team has become a little too soft when dealing with it's cotributors :-) -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Sun Dec 17 08:32:25 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA07604 for current-outgoing; Sun, 17 Dec 1995 08:32:25 -0800 (PST) Received: from jhome.DIALix.COM (jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA07453 Sun, 17 Dec 1995 08:30:58 -0800 (PST) Received: (from julian@localhost) by jhome.DIALix.COM (8.7.3/8.7.3) id XAA02873; Sun, 17 Dec 1995 23:42:39 +0800 (WST) From: Julian Elischer Message-Id: <199512171542.XAA02873@jhome.DIALix.COM> Subject: Re: FreeBSD-current-stable ??? To: andreas@knobel.gun.de (Andreas Klemm) Date: Sun, 17 Dec 1995 23:42:38 +0800 (WST) Cc: current@FreeBSD.org, hackers@FreeBSD.org, cracauer@wavehh.hanse.de, jkh@FreeBSD.org In-Reply-To: from "Andreas Klemm" at Dec 17, 95 09:22:15 am X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > > Hi FreeBSD core team ! > > [ Possibly I'm speaking for many other people here ] It's possible. > > Generally I would be interested to help testing and debugging new > FreeBSD-current features. But when reading the -current mailing list, > FreeBSD-current, so to say FreeBSD-2.2 in it's early days, seems to be > an instability nightmare. Perhaps this expression is a bit oversized, > but please understand my point of view. I do dissagree. -current is exceptionally stable for what it is... It's the integration of a bunch of new code that is destined to give the 'feature set' of 2.2.. If we cound create 2.2 without any integration we would, but as we are trying to produce a kernel in 2.2 that has many many new facets, it is inevitable that new code be integrated in -current.. I run -currrent (up until last week) on my machine at TFS.com and I have had NO troubles with it... > > I read in -current very often messages like, can't boot, can't compile, > unreferenced symbols, ... and so on ... > Usually this is pilot error. It usually requires the user to compile more or check their configuration..... Sometimes it's something due to the symbol space cleanup going on, but I tyhink this is vastly overstated.. the -current kernel is in a successfully compilabel state 90% of the time.. from my commercial experience I'd say this is a REMARKABLE achievement.. > Nothing on which you would want to run your home system > (news, mail, www). If you want to do that run 2.1 > > Since I only have one PC and one harddisk, as many other people, > it's not possible for me to switch to -current, because I need > a certain level of stability. you should be able to do all your initial development with 2.1 You can also have two kernel trees (for example) and compile and run 2.2 kernels froma 2.1 tree.. you will have to compile 2.2 versions of some utilities (ps etc) but it's quite doable.. I do it here > > When speaking with people like Martin Cracauer, then I get > the impression, that possibly more people would be interested > to help in FreeBSD developement. Perhaps developing additional > features, too. But they only have one machine, which shouldn't > get into a very unstable state. you don't need to totally upgrade.. you can.. 1/ do development on 2.1 2/ make a chroot tree, filled with 2.2 binaries 3/ use the 2.1 reee with a 2.2 kernel for testing -current is by definition kinda unstable.. it's a feature, not a problem.. > > So how could one attract more people, to work on the bleeding > edge, without loosing stability too much ??!! > > Could FreeBSD-current developement be made more attractive > to more people by splitting -current into 2 branches ? no. > > FreeBSD-current > FreeBSD-experimental > > The FreeBSD-experimental tree should be for typical alpha software > for equipped hackers with two systems or two harddisks ... > If there is a brand new driver with a risk of crashing the systemm > it should be added and tested there. No the code that is SO green that it cashes the systems should be tested in people's private trees.. > If the new driver doesn't cause crashes or such it shoud move to > FreeBSD-current, to introduce it to a larger audience that is > willed to test the bleeding edge. i.e just like now.. > > Such newly introduced feature should be tested well in -current > and should get to a stable state in -current. If it is stable, then > a) it can be added to the -stable branch. > b) you have a stable -current with the newest "tested" features and who is going to 'make' this branch? I run -current... I don't have problems.. if it aint broke don't fix it.. > > This would have the advantage, that more people could work on -current, > since it could be more stable then now. And ... the developers would > work on a developement platform, that has incorporated the newest > features. you should freeze your own environment at a stable point if you want isolation from what'sm going on.... it just means that you will have more to 'catch up' when you merge your changes.. > > What about that ? Too much admin overhaead ? > yes > Perhaps that bit more on administration overhead regarding the > newly introduced source branch can be justified with a certain > increase of FreeBSD-current developers ?! > > Would it be possible to start with such a "beast" by simply > leaving current as it ->> "experimental branch" and by introducing > something like a FreeBSD-beta branch and adding current-changes to > it, that are known to be stable ? > > So you'd have a > > release branch - the last good one > stable branch - fixes for last -release and stable new features > from beta branch > beta branch - new features, something like SNAPSHOT in > it's early hours ;-) > alpha (current) > branch - current for hackers as it is > > Would/could you agree with such a change ? If you would offer a > more stable -current as described, I'd immediately switch to > sup the new beta-branch to see what's new and to give feedbacks... > So I can't :( > It would require almost doubling the work.. after doing your import of changes, youd then have to wait a few hours anf then move the changes to alpha (or whatever) what we have now is working fine... if you can't cope with the TINY hickups happenning then you should tay with -dtable (2.1) and develope with that.. and 'merge the new driver to -curent later. > Andreas /// > > -- > andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH > Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - julian.... > \/ > ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz > apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< > From owner-freebsd-current Sun Dec 17 08:55:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA08472 for current-outgoing; Sun, 17 Dec 1995 08:55:54 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA08467 for ; Sun, 17 Dec 1995 08:55:52 -0800 (PST) Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with SMTP id IAA10418 for ; Sun, 17 Dec 1995 08:45:06 -0800 (PST) Received: (from bugs@localhost) by freebsd.netcom.com (8.6.12/8.6.12) id KAA08740 for current@freebsd.org; Sun, 17 Dec 1995 10:38:28 -0600 From: Mark Hittinger Message-Id: <199512171638.KAA08740@freebsd.netcom.com> Subject: Re: FreeBSD-current-stable ??? (fwd) To: current@freebsd.org Date: Sun, 17 Dec 1995 10:38:28 -0600 (CST) X-Mailer: ELM [version 2.4 PL24 ME8b] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > People committing to -current need to get their acts together and stop > destabilising it so much. Prior to 2.1 going gold a free for all in the 2.2 tree was perfectly ok. The strategy of having a stable platform (2.1) has served us very well and a lot of new people are trying it out. Now that 2.1 has gone gold, the time is probably right to start a freeze on the goals for 2.2 functionality and 2.2 performance improvement. ** I didn't say freeze - I said start-to-freeze-the-goals!! ** heh We will have many people who after playing with 2.1 will go ahead and try to bring down 2.2 out of curiosity. This is part of the fun of FreeBSD, that you can get the newest version and play with it. I would actually consider it a sign of (FreeBSD 2.1) success if enough satisfied consumers tried to look at 2.2! The danger is that they might see a lot of problems with it and loose some confidence. I didn't worry about this prior to 2.1's release because 2.1 *was* the next version. Since 2.1 has been released the next version is assumed to be 2.2 by default (I realize we might have a 2.1.5). Perhaps we need a 2.1-stable, 2.2-performance, and a 2.3-boom :-) 2.3-boom could be the new wild west :-) I know there is a disk space issue. Regards, Mark Hittinger Netcom/Dallas bugs@freebsd.netcom.com From owner-freebsd-current Sun Dec 17 09:31:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09425 for current-outgoing; Sun, 17 Dec 1995 09:31:28 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09419 Sun, 17 Dec 1995 09:31:27 -0800 (PST) From: John Dyson Message-Id: <199512171731.JAA09419@freefall.freebsd.org> Subject: Re: FreeBSD-current-stable ??? To: paul@netcraft.co.uk Date: Sun, 17 Dec 1995 09:31:26 -0800 (PST) Cc: jkh@time.cdrom.com, andreas@knobel.gun.de, current@FreeBSD.org, hackers@FreeBSD.org, cracauer@wavehh.hanse.de, jkh@FreeBSD.org In-Reply-To: <199512171436.OAA13800@server.netcraft.co.uk> from "Paul Richards" at Dec 17, 95 02:36:17 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk > > Absolutely, the vm headers are a good example. Peter was fixing > code for a while after this commit because some parts of the tree > WOULDN'T EVEN COMPILE! Was a make world done before this commit, > I somehow doubt it given the glaring problems that Peter fixed. > Missing the odd bug when changing the filesystem to allow 1Tb files > is one thing and is what -current is for, not doing even a basic > sanity check to make sure the tree still compiles is a totally > different case and one we used to be a lot more stern about when > it happened. > > I think the core team has become a little too soft when dealing > with it's cotributors :-) > A make world was not done, and if someone would donate a reasonable machine to me to let me do so -- it would be very nice. I probably have the least powerful machine of any major contributor (and have only one.) Those with expensive high power machines are welcome to help. (Machines bigger than a 3 yr old 20MB 486/66 :-)). The kernel did work -- and there was some chaff (a bug in sys_process.c) -- oh, by the way did the 1Tb changes break things -- or was it the header file changes/improvements???? All I had to do to get ps working again was to rebuild libkvm/ps.... John dyson@freebsd.org From owner-freebsd-current Sun Dec 17 09:35:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09670 for current-outgoing; Sun, 17 Dec 1995 09:35:27 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09664 Sun, 17 Dec 1995 09:35:24 -0800 (PST) From: John Dyson Message-Id: <199512171735.JAA09664@freefall.freebsd.org> Subject: Re: FreeBSD-current-stable ??? (fwd) To: bugs@freebsd.netcom.com (Mark Hittinger) Date: Sun, 17 Dec 1995 09:35:23 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199512171638.KAA08740@freebsd.netcom.com> from "Mark Hittinger" at Dec 17, 95 10:38:28 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > Now that 2.1 has gone gold, the time is probably right to start a freeze on > the goals for 2.2 functionality and 2.2 performance improvement. ** I didn't > say freeze - I said start-to-freeze-the-goals!! ** heh > I have some improvements to vfs_bio that *really* make some significant performance impact. I am waiting for -current to settle. John dyson@freebsd.org From owner-freebsd-current Sun Dec 17 09:37:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09778 for current-outgoing; Sun, 17 Dec 1995 09:37:13 -0800 (PST) Received: from knobel.gun.de (knobel-ip.gun.de [192.109.159.141]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA09753 Sun, 17 Dec 1995 09:37:01 -0800 (PST) Received: (from andreas@localhost) by knobel.gun.de (8.6.12/8.6.12) id SAA03816; Sun, 17 Dec 1995 18:36:30 +0100 From: Andreas Klemm Message-Id: <199512171736.SAA03816@knobel.gun.de> Subject: Re: FreeBSD-current-stable ??? To: julian@jhome.DIALix.COM (Julian Elischer) Date: Sun, 17 Dec 1995 18:36:30 +0100 (MET) Cc: current@FreeBSD.org, hackers@FreeBSD.org, cracauer@wavehh.hanse.de, jkh@FreeBSD.org In-Reply-To: <199512171542.XAA02873@jhome.DIALix.COM> from "Julian Elischer" at Dec 17, 95 11:42:38 pm X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk Hi Julian and the others ! > I do dissagree. -current is exceptionally stable for what it is... Ok, but other people seem to dislike little surprises Among them Jordan and Paul. But what counts more, people, that would otherwise like to join -current as I described. > Usually this is pilot error. It usually requires the user to > compile more or check their configuration..... Here I disagree. As Jordan already mentioned, it should be normal, to incorporate only those changes into the current tree, that are locally tested. Normally you cam only test something, that does compile. If changes doesn't compile, then it's a sign for either - not tested or - tested in a too small scope > Sometimes it's something due to the symbol space cleanup > going on, but I tyhink this is vastly overstated.. Then it would be interesting to me, to hear from Martin Cracauer, why he is currently not interested in getting current. Perhaps some patches are really done too loosey or whatever. > the -current kernel is in a successfully compilabel state > 90% of the time.. from my commercial experience I'd say this is a > REMARKABLE achievement.. Well the whole FreeBSD project is a very very good one and I'm really happy to have such a wonderful and stable OS running here. But that's not the point. Current should be brought into a state, that more people are motivated to sup and install it. The goal is, to get some more good programmers into the boat. > No the code that is SO green that it cashes the systems should > be tested in people's private trees.. Yes. And in addition to that: changes should be tested. It's not necessary, that other people can't compile the system after supping those changes. > what we have now is working fine... > if you can't cope with the TINY hickups happenning > then you should stay with -stable (2.1) and develope with that.. > and 'merge the new driver to -curent later. On the other hand ... If -current would become more stable, then more people would use it. This would have the advantage, that feedback on new code would come much earlier. This would have a big advantage shortly before a release schedule. The quality of SNAP shots would improve, possibly one wouldn't need as many SNAP's. -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Sun Dec 17 10:13:40 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA11140 for current-outgoing; Sun, 17 Dec 1995 10:13:40 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA11133 for ; Sun, 17 Dec 1995 10:13:24 -0800 (PST) Received: from plentium.clinet.fi (plentium.clinet.fi [194.100.0.7]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id UAA29875; Sun, 17 Dec 1995 20:13:13 +0200 Received: (hsu@localhost) by plentium.clinet.fi (8.6.12/8.6.4) id UAA16727; Sun, 17 Dec 1995 20:17:13 +0200 Date: Sun, 17 Dec 1995 20:17:13 +0200 Message-Id: <199512171817.UAA16727@plentium.clinet.fi> From: Heikki Suonsivu To: Mark Hittinger Cc: current@freebsd.org In-reply-to: Mark Hittinger's message of 17 Dec 1995 18:57:59 +0200 Subject: Re: FreeBSD-current-stable ??? (fwd) Organization: Clinet Ltd, Espoo, Finland Sender: owner-current@freebsd.org Precedence: bulk Perhaps we need a 2.1-stable, 2.2-performance, and a 2.3-boom :-) 2.3-boom could be the new wild west :-) I know there is a disk space issue. The problem is that people are committing broken code into source tree without testing it. There should never be need for more than two threads, one which is being stabilized and one development. Both of them should be workable when checked out. As CVS makes doing separate testing trees easy, there should be no reason for untested code ever be committed? -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi work +358-0-4375209 fax -4555276 home -8031121 From owner-freebsd-current Sun Dec 17 11:16:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA13172 for current-outgoing; Sun, 17 Dec 1995 11:16:53 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA13151 Sun, 17 Dec 1995 11:16:46 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA17231; Mon, 18 Dec 1995 06:11:27 +1100 Date: Mon, 18 Dec 1995 06:11:27 +1100 From: Bruce Evans Message-Id: <199512171911.GAA17231@godzilla.zeta.org.au> To: andreas@knobel.gun.de, julian@jhome.dialix.com Subject: Re: FreeBSD-current-stable ??? Cc: cracauer@wavehh.hanse.de, current@freebsd.org, hackers@freebsd.org, jkh@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk >> Hi FreeBSD core team ! >> >> [ Possibly I'm speaking for many other people here ] >It's possible. Possibly for non-developers :-). >> >> Generally I would be interested to help testing and debugging new >> FreeBSD-current features. But when reading the -current mailing list, >> FreeBSD-current, so to say FreeBSD-2.2 in it's early days, seems to be ^^^^^^^^^^^ >> an instability nightmare. Perhaps this expression is a bit oversized, >> but please understand my point of view. >I do dissagree. -current is exceptionally stable for what it is... I agree with Julian. >I run -currrent (up until last week) on my machine at TFS.com >and I have had NO troubles with it... I have had only one serious problem (2 core dumps apparently caused by some vm change in the last month). Bruce From owner-freebsd-current Sun Dec 17 11:56:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA14843 for current-outgoing; Sun, 17 Dec 1995 11:56:26 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA14809 Sun, 17 Dec 1995 11:56:13 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id UAA14386; Sun, 17 Dec 1995 20:46:43 +0100 Message-Id: <199512171946.UAA14386@ra.dkuug.dk> Subject: Re: FreeBSD-current-stable ??? To: bde@zeta.org.au (Bruce Evans) Date: Sun, 17 Dec 1995 20:46:42 +0100 (MET) Cc: andreas@knobel.gun.de, julian@jhome.dialix.com, cracauer@wavehh.hanse.de, current@FreeBSD.ORG, hackers@FreeBSD.ORG, jkh@FreeBSD.ORG In-Reply-To: <199512171911.GAA17231@godzilla.zeta.org.au> from "Bruce Evans" at Dec 18, 95 06:11:27 am From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk In reply to Bruce Evans who wrote: > > >> Hi FreeBSD core team ! > >> > >> [ Possibly I'm speaking for many other people here ] > >It's possible. > > Possibly for non-developers :-). > > >> > >> Generally I would be interested to help testing and debugging new > >> FreeBSD-current features. But when reading the -current mailing list, > >> FreeBSD-current, so to say FreeBSD-2.2 in it's early days, seems to be > >> an instability nightmare. Perhaps this expression is a bit oversized, > >> but please understand my point of view. > >I do dissagree. -current is exceptionally stable for what it is... > > I agree with Julian. Ahem, I'm not sure I do, I think we should take this critique VERY serious guys. I have been trying to get a -current system up and running for the last week, and its just been possible shortly to even compile a system without tweeking files here and there... (and I'm seeing runtime problems here and there still) I think its is CRUCIAL that -current can be compile & is resonably stable at any given time. I agree that this puts more stress on the people doing "high tech" development for the next release, but they should test their code so that it at least compiles. When it is kernel level stuff it should at least work too. I've been burnt more than once by a kernel that blew up into my face destroing hours of work (I know, I asked for it running current :) Also getting a current up and running this time (for doing dev work) has costed me ~ a week where I could have done some real work on the system.... > >I run -currrent (up until last week) on my machine at TFS.com > >and I have had NO troubles with it... > > I have had only one serious problem (2 core dumps apparently caused by > some vm change in the last month). You must have another current than most of us :) :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Sun Dec 17 12:50:37 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA19618 for current-outgoing; Sun, 17 Dec 1995 12:50:37 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA19613 Sun, 17 Dec 1995 12:50:35 -0800 (PST) X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: current@freebsd.org, hackers@freebsd.org Subject: Re: FreeBSD-current-stable ??? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19610.819233434.1@freefall.freebsd.org> Date: Sun, 17 Dec 1995 12:50:34 -0800 Message-ID: <19611.819233434@freefall.freebsd.org> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > >> Hi FreeBSD core team ! > >> > >> [ Possibly I'm speaking for many other people here ] > >It's possible. > > Possibly for non-developers :-). likely so.. > >> > >> Generally I would be interested to help testing and debugging new > >> FreeBSD-current features. But when reading the -current mailing list, > >> FreeBSD-current, so to say FreeBSD-2.2 in it's early days, seems to be > ^^^^^^^^^^^ > >> an instability nightmare. Perhaps this expression is a bit oversized, > >> but please understand my point of view. > >I do dissagree. -current is exceptionally stable for what it is... > > I agree with Julian. actually even more stable than in a long time :-) > >I run -currrent (up until last week) on my machine at TFS.com > >and I have had NO troubles with it... > > I have had only one serious problem (2 core dumps apparently caused by > some vm change in the last month). I have some bogons, but they are quite likely HW actually. (Don't worry Rod, I just have not got around to flash the boot-patition correctly :-). I would like to release some steam here. If we are to keep abreast with the world, (we're presently running a mere 5 years behind schedule I think), we need to move some things a long way. If changes like devfs, protoizing & staticization are supposed to be commited as flaw-less, then we might as well close shop and run Linux. -current is generally compilable, it's perfectly stable for long stretches of time, but right after any major release, a lot of saved up powder gets ignited with -current as target, and that is simply the way it is. If somebody were to stand forward and say, "I'm willing to maintain a tag on the CVS-tree which runs a little behind HEAD, and which is stable", (firest I would question that persons sanity actually), I would think that we may go for it, but any more administrative work, and the core- team will melt. I as a FreeBSD hacker, and as a -core in particular, try to do my best, and that is it really. I cannot do it any better. Sometimes you break code you didn't know were there. I have found so much dead code during my staticization sweep that I'm positively sure nobody else, (including superhumans like Terry :-) knows all of our source and how it fits together, to a level of detail that would allow us to run a "safe shop" in -current. Maybe when the kernel gets more modular, this will be less of a problem, but now, that's the way it is. If you want to help us, but only have one machine, run -stable (2.1.0 presently), and work in user-space. (If you only have one machine, kernel-hacking is very dangerous anyway.) User-space isn't any more boring than the kernel. If you don't belive me do this: cd /usr/src make CFLAGS=-Wall plenty to do :-( FreeBSD needs a lot more than kernel hackers. Go for it :-) Poul-Henning From owner-freebsd-current Sun Dec 17 12:56:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA19963 for current-outgoing; Sun, 17 Dec 1995 12:56:52 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA19958 for ; Sun, 17 Dec 1995 12:56:49 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA09975; Sun, 17 Dec 1995 13:53:36 -0700 From: Terry Lambert Message-Id: <199512172053.NAA09975@phaeton.artisoft.com> Subject: Re: FreeBSD-current-stable ??? (fwd) To: hsu@clinet.fi (Heikki Suonsivu) Date: Sun, 17 Dec 1995 13:53:36 -0700 (MST) Cc: bugs@freebsd.netcom.com, current@FreeBSD.ORG In-Reply-To: <199512171817.UAA16727@plentium.clinet.fi> from "Heikki Suonsivu" at Dec 17, 95 08:17:13 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-current@FreeBSD.ORG Precedence: bulk > Perhaps we need a 2.1-stable, 2.2-performance, and a 2.3-boom :-) 2.3-boom > could be the new wild west :-) I know there is a disk space issue. > > The problem is that people are committing broken code into source tree > without testing it. There should never be need for more than two threads, > one which is being stabilized and one development. Both of them should be > workable when checked out. As CVS makes doing separate testing trees easy, > there should be no reason for untested code ever be committed? Sorry, but this is inhernet in the CVS mechanism itself. I have suggested before a reader/writer lock mechanism. If the checkout for general availability obeyed a reader/writer lock, it would be impossible to get a checkout during an active checkin. If committers built before rleasing the writer lock, the tree could never be in a state where it could not be built. There are situation where this isn't completely possible because of lack of equipment (I thought this was what thud was for?), but in the general case, it's really nothing more than a tree usage protocol problem. 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-current Sun Dec 17 14:19:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA27118 for current-outgoing; Sun, 17 Dec 1995 14:19:27 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA27112 for ; Sun, 17 Dec 1995 14:19:24 -0800 (PST) Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with ESMTP id NAA22057 for ; Tue, 12 Dec 1995 13:21:41 -0800 (PST) Received: (from mark@localhost) by linus.demon.co.uk (8.7.3/8.7.3) id VAA00447 for current@freebsd.org; Tue, 12 Dec 1995 21:18:40 GMT Message-Id: <199512122118.VAA00447@linus.demon.co.uk> From: mark@linus.demon.co.uk (Mark Valentine) Date: Tue, 12 Dec 1995 21:18:39 +0000 X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: current@FreeBSD.ORG Subject: padded files Sender: owner-current@FreeBSD.ORG Precedence: bulk I've had a couple of header files apparently get padded out to an 8K boundary with NULs during a make world today (small sample: might have been a page boundary). This was on an up-to-date kernel. The modification time on the files was "just a minute ago", when the only feasible operation on them was cpp reading them... (This is a single user machine, not connected to any network at the time.) I've also been getting a few of the previously reported "attempt to write meta-data" messages, but not at the same time as these file corruptions. Could some of the recent innocuous changes possibly be not so innocuous, or uncovering old bugs? System is a 486DX2/66, 16MB RAM, AHA1542C (no bounce buffers). Mark. -- "Tigers will do ANYTHING for a tuna fish sandwich." "We're kind of stupid that way." *munch* *munch* From owner-freebsd-current Sun Dec 17 14:20:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA27286 for current-outgoing; Sun, 17 Dec 1995 14:20:33 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA27278 for ; Sun, 17 Dec 1995 14:20:28 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA21915; Sun, 17 Dec 1995 15:22:15 -0700 Date: Sun, 17 Dec 1995 15:22:15 -0700 From: Nate Williams Message-Id: <199512172222.PAA21915@rocky.sri.MT.net> To: Julian Elischer Cc: current@FreeBSD.org Subject: Re: FreeBSD-current-stable ??? In-Reply-To: <199512171542.XAA02873@jhome.DIALix.COM> References: <199512171542.XAA02873@jhome.DIALix.COM> Sender: owner-current@FreeBSD.org Precedence: bulk > > Generally I would be interested to help testing and debugging new > > FreeBSD-current features. But when reading the -current mailing list, > > FreeBSD-current, so to say FreeBSD-2.2 in it's early days, seems to be > > an instability nightmare. Perhaps this expression is a bit oversized, > > but please understand my point of view. > I do dissagree. -current is exceptionally stable for what it is... I *BEG* to differ. -Current is absolutely useless for me, and I'm running a system that it about as stock as it can get. This box ran 2.0.5 for weeks w/out problems, and I can't run for more than 5 minutes under -current. Now, if you consider that 'exceptionally stable', I guess we have some differences in how we communicate stability. > > I read in -current very often messages like, can't boot, can't compile, > > unreferenced symbols, ... and so on ... > > > Usually this is pilot error. It usually requires the user to compile more > or check their configuration..... I beg your pardon? I've been doing this for a *LONG* time (as long as most folks), and even now wearing the hat of 'release engineer' for SRI's internal BSD release. I *do* know what I'm doing and I can say that -current is completely and absolutely unusable for me. I *want* to run -current so I can help work out the bugs in it. I like the idea of -current for many reasons, two of them being: 1) It's the only fair place for new/radical changes to be integrated in 2) It gives these changes a chance to be tested However, the -current kernel tree has been broken for many people for over 6 weeks now. I remember folks complaining about getblk() hangs in early November, and I although it appears that they are fixed for some folks (and for unknown reasons), we have yet to see a version of -current since November that is has been compilable and usable for a majority of folks. I finally have given up on a -current kernel simply because my machine reboots with no panic messages or dumps if I don't have DDB installed, and hangs with DDB. I am now tracking -current only in those parts of user-land code which don't require 2.2 functionality. There have been few changes in the user-land stuff though. > Sometimes it's something due to the symbol space cleanup > going on, but I tyhink this is vastly overstated.. > the -current kernel is in a successfully compilabel state > 90% of the time.. from my commercial experience I'd say this is a > REMARKABLE achievement.. I don't mind it being a little bit broken, but when we have *serious* instability problems, it shouldn't be the goal of everyone to stuff in 'one more feature' which affects the entire system. There have been 4-5 major wide sweeping changes that affect the entire kernel sources since the tree was opened up, any one which can make the kernel unstable/un-compilable. I know for a fact that the kernel was unstable after the first couple additions, but that didn't stop folks from adding more to the tree, thus making it more difficult to track down the problem. > > Since I only have one PC and one harddisk, as many other people, > > it's not possible for me to switch to -current, because I need > > a certain level of stability. > > you should be able to do all your initial development with 2.1 Then -current has no purpose. I'll bet the number of folks who actually run -current are less than 20. This means that -current serves no purpose which couldn't be served by sending patches to one another, since the audience is extremely small. > You can also have two kernel trees (for example) and compile and run > 2.2 kernels froma 2.1 tree.. ... > you will have to compile 2.2 versions of some utilities (ps etc) > but it's quite doable.. I do it here It doesn't work very well at all. It *sort of* works, but you're not testing anything new, since all the new interesting stuff in the user-land requires a -current kernel. All the non-interesting stuff doesn't need to be tested or was tested well before it was integrated. :) > > When speaking with people like Martin Cracauer, then I get > > the impression, that possibly more people would be interested > > to help in FreeBSD developement. Perhaps developing additional > > features, too. But they only have one machine, which shouldn't > > get into a very unstable state. > > you don't need to totally upgrade.. > you can.. > 1/ do development on 2.1 You can't do kernel development on 2.1 since the kernel has changed radically in -current. > 2/ make a chroot tree, filled with 2.2 binaries Which works for all the non-important user-land stuff. > 3/ use the 2.1 reee with a 2.2 kernel for testing > -current is by definition kinda unstable.. it's a feature, not a problem.. I agree that -current can be uncompilable for short times, and unstable for short times, but 6 weeks is way too long. There are *bugs* in the kernel which were known about 6 weeks ago which still haven't been addressed, but 'progress' has gone out without progress being made. > > If there is a brand new driver with a risk of crashing the systemm > > it should be added and tested there. > No the code that is SO green that it cashes the systems should be tested in > people's private trees.. Obviously this hasn't been done. When reports of crashes come in, the developers attitude has been 'it works for me, I'm going to assume it's pilot error', rather than 'here is how you can work with me to find the problem'. Not to single you out alone, but your 'JREMOD' changes were announced one day, installed into the tree the next day, and then you complained that folks weren't giving you feedback less than 48 hours after they were put in. First of all, the tree was unstable *before* the changes went in, so folks weren't running -current until those were fixed. Then, those folks that were supposed to quickly get the new sources, compile up new kernels, and test them out in less than 48 hours and give you valid feedback? I don't think that's fair to either the developers or the users. Now, this *is* a volunteer project and everyone is free to do what they wish, but that doesn't give folks cause to put in their 'pet project' into the tree no matter what state the tree is in. > > If the new driver doesn't cause crashes or such it shoud move to > > FreeBSD-current, to introduce it to a larger audience that is > > willed to test the bleeding edge. > i.e just like now.. I doubt we have the number of folks running -current that we had for the 1.X releases. I doubt we have the number of folks running -current that we had since the 2.0 release. > I run -current... > I don't have problems.. > if it aint broke don't fix it.. That's the attitude I'm seeing. "If I don't see any problems, there must not be any problems." Is this the same Julian Elischer who complained for months that 'FreeBSD must have a problem since the same hardware runs OSF fine and crashes repeatedly under FreeBSD'? How come it's fine to act this way when it doesn't affect you directly, but it's not when it affects you? > what we have now is working fine... > if you can't cope with the TINY hickups happenning I don't consider these TINY anymore. I can see the tree being broken for weeks, but *IF* it's broken then the free for all that's happened in the tree shouldn't occur. Kernel folks, the kernel is broken w/regard to a large number of folks who try to run it. I think we have a number of folks who are willing to work with you to make it better, but there isn't any co-operation from you. We need your help to make it better, and telling folks "it works for me, it must be something you've done" is only making the problem worse. Nate From owner-freebsd-current Sun Dec 17 14:53:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA00831 for current-outgoing; Sun, 17 Dec 1995 14:53:44 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA00823 for ; Sun, 17 Dec 1995 14:53:36 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA21983; Sun, 17 Dec 1995 15:56:08 -0700 Date: Sun, 17 Dec 1995 15:56:08 -0700 From: Nate Williams Message-Id: <199512172256.PAA21983@rocky.sri.MT.net> To: current@FreeBSD.org Subject: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) In-Reply-To: References: <7748.819191407@time.cdrom.com> Sender: owner-current@FreeBSD.org Precedence: bulk I just posted something, but I read through the all of the email on this subject and I want to summarize what I'm seeing. S'ren and I are seeing lots of problems with -current. Peter is seeing some problems with -current, most related to the AHC driver. Bruce, John, and Julian aren't seeing any (significant) problems on their systems. So, S'ren and I are upset (understandably), and are venting our frustrations on the mailing lists. The users are seeing this and are un-willing to run -current on their boxes, and are asking for a more 'stable -current' so they can try out new features. Some of the developers are defending the unstability of -current as 'the way things are', which is justified, but this attitude has been going on for a very long time. Me, I resent being told that it's 'operator error', as well I'm sure S'ren does (and probably anyone else). We've been doing this long enough to know what we are doing, and the fact of the matter is that for us the system is unusable. However, this response of 'that's -current' has gone on for a while now. I watch the mailing lists, commit lists, and such and I've yet to see fixes which directly apply to bugs that were reported a long time ago. Now, we could be trying to add so many 'good/tested' code to the system that the bugs we're tracking down will become so obvious that it will be easy to find them, but somehow I doubt this is the case. I agree that the changes made to the tree have been good changes, but what I disagree on is the timing. However, in defense of the -core team and the developers, I can see where an unstable -current is less important since the next release is not based on it. There is going to be alot more time to fix the bugs in -current than normal, so more instability is acceptable. But, the ways things have been going I don't see how -current will ever become a release candidate for 'normal' users unless the 'feeping creaturism' slows, which I suspect will happen in time. In the meantime, *how* can folks help the developers debug -current. Obviously, the system works fine for the developers who added the new fetures, but it's not for others. We need a way for the -current developers to give some time to helping out those folks who can't get it working who *can* help them out. I'm willing to get -current more stable if I can get someone to work with me. I'll have more time to work on it over the holidays as I have a week off, and I will be around home for most of it. Nate From owner-freebsd-current Sun Dec 17 15:25:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA04168 for current-outgoing; Sun, 17 Dec 1995 15:25:16 -0800 (PST) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA04123 Sun, 17 Dec 1995 15:25:01 -0800 (PST) Received: by haven.uniserve.com id <30740-2>; Sun, 17 Dec 1995 15:27:23 -0000 Date: Sun, 17 Dec 1995 15:27:17 -0800 (PST) From: Tom Samplonius To: John Dyson cc: paul@netcraft.co.uk, jkh@time.cdrom.com, andreas@knobel.gun.de, current@FreeBSD.ORG, hackers@FreeBSD.ORG, cracauer@wavehh.hanse.de, jkh@FreeBSD.ORG Subject: Re: FreeBSD-current-stable ??? In-Reply-To: <199512171731.JAA09419@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk While this discussion about -current is all very nice, but what I want to know, is anyone still doing bug-hunting through the -stable tree? Tom From owner-freebsd-current Sun Dec 17 16:07:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08378 for current-outgoing; Sun, 17 Dec 1995 16:07:02 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA08357 for ; Sun, 17 Dec 1995 16:06:57 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id BAA13085 ; Mon, 18 Dec 1995 01:06:55 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id BAA14283 ; Mon, 18 Dec 1995 01:06:54 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id BAA00293; Mon, 18 Dec 1995 01:05:23 +0100 (MET) From: Ollivier Robert Message-Id: <199512180005.BAA00293@keltia.freenix.fr> Subject: Re: Mouse not working for two days To: bde@zeta.org.au (Bruce Evans) Date: Mon, 18 Dec 1995 01:05:23 +0100 (MET) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199512162032.HAA09302@godzilla.zeta.org.au> from "Bruce Evans" at Dec 17, 95 07:32:16 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1441 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that Bruce Evans said: > It breaks COM_NOFIFO() for at least 16650's and stops the output fifo > being used at speeds <= 4800. These bugs shouldn't matter for mouses. > Perhaps the second bug interferes with the SMC bugfix (what happens > when the fifos are reset while the fifos are not enabled?). Here is the patch I made to restore most of the 1.126 sio.c code, changing the constants FIFO_TRIGGER_* into the new FIFO_RX_*. The new 16650 detection code is between STARTECH_PROBE (from a patch Peter sent me). I don't know if all of what I inserted back is useful but as it is needed for the last part of the patch which is the *culprit* in my problem ! I found that because it would not work till I inserted the lines back... Index: sio.c =================================================================== RCS file: /spare/FreeBSD-current/src/sys/i386/isa/sio.c,v retrieving revision 1.129 diff -u -2 -r1.129 sio.c --- sio.c 1995/12/10 20:54:38 1.129 +++ sio.c 1995/12/17 23:57:24 @@ -174,4 +174,6 @@ u_char cfcr_image; /* copy of value written to CFCR */ u_char ftl; /* current rx fifo trigger level */ + u_char ftl_init; /* ftl_max for next open */ + u_char ftl_max; /* maximum ftl for current open */ bool_t hasfifo; /* nonzero for 16550 UARTs */ bool_t loses_outints; /* nonzero if device loses output interrupts */ @@ -835,8 +837,12 @@ } else { com->hasfifo = TRUE; + com->ftl_init = FIFO_RX_HIGH; com->tx_fifo_size = 16; kdc_sio[unit].kdc_description = "Serial port: National 16550A or compatible"; } +#ifndef STARTECH_PROBE + printf(" 16550A"); +#else /* * Check for the Startech ST16C650 chip. @@ -861,7 +867,10 @@ "Serial port: Startech 16C650 or similar"; } +#endif if (!com->tx_fifo_size) printf(" fifo disabled"); +#ifdef STARTECH_PROBE } +#endif break; } @@ -1036,4 +1045,5 @@ ? com->it_out : com->it_in; (void)commctl(com, TIOCM_DTR | TIOCM_RTS, DMSET); + com->ftl_max = com->ftl_init; com->poll = com->no_irq; com->poll_output = com->loses_outints; @@ -1062,5 +1072,6 @@ while (TRUE) { outb(iobase + com_fifo, - FIFO_RCV_RST | FIFO_XMT_RST | com->ftl); + FIFO_RCV_RST | FIFO_XMT_RST + | FIFO_ENABLE | com->ftl); DELAY(100); if (!(inb(com->line_status_port) & LSR_RXRDY)) @@ -1898,6 +1909,8 @@ */ com->ftl = t->c_ospeed <= 4800 - ? 0 : FIFO_ENABLE | FIFO_RX_HIGH; - outb(iobase + com_fifo, com->ftl); + ? FIFO_RX_LOW : FIFO_RX_HIGH; + if (com->ftl > com->ftl_max) + com->ftl = com->ftl_max; + outb(iobase + com_fifo, FIFO_ENABLE | com->ftl); } -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #4: Fri Dec 15 19:22:25 MET 1995 From owner-freebsd-current Sun Dec 17 16:21:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA09957 for current-outgoing; Sun, 17 Dec 1995 16:21:45 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA09952 Sun, 17 Dec 1995 16:21:42 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id QAA04798; Sun, 17 Dec 1995 16:21:12 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id QAA01420; Sun, 17 Dec 1995 16:21:50 -0800 Message-Id: <199512180021.QAA01420@corbin.Root.COM> To: sos@freebsd.org cc: current@freebsd.org, hacker@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Sun, 17 Dec 95 20:46:42 +0100." <199512171946.UAA14386@ra.dkuug.dk> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 17 Dec 1995 16:21:50 -0800 Sender: owner-current@freebsd.org Precedence: bulk >> >I run -currrent (up until last week) on my machine at TFS.com >> >and I have had NO troubles with it... >> >> I have had only one serious problem (2 core dumps apparently caused by >> some vm change in the last month). > >You must have another current than most of us :) :) Actually, I haven't had any problems with -current, either. -DG From owner-freebsd-current Sun Dec 17 16:38:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA10965 for current-outgoing; Sun, 17 Dec 1995 16:38:52 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA10960 Sun, 17 Dec 1995 16:38:49 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id QAA04853; Sun, 17 Dec 1995 16:38:48 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id QAA01438; Sun, 17 Dec 1995 16:39:27 -0800 Message-Id: <199512180039.QAA01438@corbin.Root.COM> To: Tom Samplonius cc: current@freebsd.org, hackers@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Sun, 17 Dec 95 15:27:17 PST." From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 17 Dec 1995 16:39:26 -0800 Sender: owner-current@freebsd.org Precedence: bulk > While this discussion about -current is all very nice, but what I want >to know, is anyone still doing bug-hunting through the -stable tree? Yes, fixes are going into -stable *slowly* (just as they should be). -DG From owner-freebsd-current Sun Dec 17 16:43:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA11246 for current-outgoing; Sun, 17 Dec 1995 16:43:18 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA11234 Sun, 17 Dec 1995 16:43:14 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id QAA04868; Sun, 17 Dec 1995 16:43:14 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id QAA01454; Sun, 17 Dec 1995 16:43:53 -0800 Message-Id: <199512180043.QAA01454@corbin.Root.COM> To: sos@freebsd.org cc: current@freebsd.org, hackers@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Sun, 17 Dec 95 20:46:42 +0100." <199512171946.UAA14386@ra.dkuug.dk> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 17 Dec 1995 16:43:52 -0800 Sender: owner-current@freebsd.org Precedence: bulk >> >I run -currrent (up until last week) on my machine at TFS.com >> >and I have had NO troubles with it... >> >> I have had only one serious problem (2 core dumps apparently caused by >> some vm change in the last month). > >You must have another current than most of us :) :) Actually, I haven't had any problems with -current, either. -DG From owner-freebsd-current Sun Dec 17 16:53:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12692 for current-outgoing; Sun, 17 Dec 1995 16:53:27 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA12636 Sun, 17 Dec 1995 16:53:16 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id QAA11101; Sun, 17 Dec 1995 16:53:03 -0800 From: "Rodney W. Grimes" Message-Id: <199512180053.QAA11101@GndRsh.aac.dev.com> Subject: Re: FreeBSD-current-stable ??? To: phk@freefall.freebsd.org (Poul-Henning Kamp) Date: Sun, 17 Dec 1995 16:53:03 -0800 (PST) Cc: current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <19611.819233434@freefall.freebsd.org> from "Poul-Henning Kamp" at Dec 17, 95 12:50:34 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-current@FreeBSD.org Precedence: bulk ... > > I have had only one serious problem (2 core dumps apparently caused by > > some vm change in the last month). > > I have some bogons, but they are quite likely HW actually. (Don't worry > Rod, I just have not got around to flash the boot-patition correctly :-). When you do go to flash it, get the 112 version of the BIOS for the PCI/I-P55TP4XE board as I have qualified that here. Be sure to update both the BIOS and the bios boot-partition (requires you to move the MB jumper to enable write to the bios boot-code) and then clear the ESCD. One thing you might try without going to the newest BIOS is drop the PCI latency timer to 32 clocks, seems ASUS has found that this works best as the 80 clocks was just to long for some boards and causes some problems. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sun Dec 17 16:56:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA13133 for current-outgoing; Sun, 17 Dec 1995 16:56:21 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA13113 for ; Sun, 17 Dec 1995 16:56:12 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id LAA27345; Mon, 18 Dec 1995 11:51:05 +1100 Date: Mon, 18 Dec 1995 11:51:05 +1100 From: Bruce Evans Message-Id: <199512180051.LAA27345@godzilla.zeta.org.au> To: bde@zeta.org.au, roberto@keltia.freenix.fr Subject: Re: Mouse not working for two days Cc: freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >I don't know if all of what I inserted back is useful but as it is needed >for the last part of the patch which is the *culprit* in my problem ! Is it really the last part?: >@@ -1898,6 +1909,8 @@ > */ > com->ftl = t->c_ospeed <= 4800 >- ? 0 : FIFO_ENABLE | FIFO_RX_HIGH; >- outb(iobase + com_fifo, com->ftl); >+ ? FIFO_RX_LOW : FIFO_RX_HIGH; >+ if (com->ftl > com->ftl_max) >+ com->ftl = com->ftl_max; >+ outb(iobase + com_fifo, FIFO_ENABLE | com->ftl); > } > I think this is a no-op at speeds > 4800, and your mouse is at 9600. Perhaps the speed is sometimes set to 0? (This might be part of the mouse initialization for certain mouses). A speed of 0 means is a command to drop DTR and it shouldn't be used for anything to do with the line speed like it is here. Disabling the FIFO should be fairly harmless, but is may fail for the buggy SMC chips. The code to work around the bug wouldn't help because the FIFO_ENABLE bit isn't set in com->ftl either. Try the following change. It keeps the FIFO enabled and fixes a bitrotted name and comment. Bruce *** sio.c~ Mon Dec 11 10:12:30 1995 --- sio.c Mon Dec 11 10:13:00 1995 *************** *** 173,177 **** bool_t active_out; /* nonzero if the callout device is open */ u_char cfcr_image; /* copy of value written to CFCR */ ! u_char ftl; /* current rx fifo trigger level */ bool_t hasfifo; /* nonzero for 16550 UARTs */ bool_t loses_outints; /* nonzero if device loses output interrupts */ --- 173,177 ---- bool_t active_out; /* nonzero if the callout device is open */ u_char cfcr_image; /* copy of value written to CFCR */ ! u_char fifo_image; /* copy of value written to FIFO */ bool_t hasfifo; /* nonzero for 16550 UARTs */ bool_t loses_outints; /* nonzero if device loses output interrupts */ *************** *** 1062,1066 **** while (TRUE) { outb(iobase + com_fifo, ! FIFO_RCV_RST | FIFO_XMT_RST | com->ftl); DELAY(100); if (!(inb(com->line_status_port) & LSR_RXRDY)) --- 1062,1067 ---- while (TRUE) { outb(iobase + com_fifo, ! FIFO_RCV_RST | FIFO_XMT_RST ! | com->fifo_image); DELAY(100); if (!(inb(com->line_status_port) & LSR_RXRDY)) *************** *** 1897,1903 **** * latencies are larger. */ ! com->ftl = t->c_ospeed <= 4800 ! ? 0 : FIFO_ENABLE | FIFO_RX_HIGH; ! outb(iobase + com_fifo, com->ftl); } --- 1898,1904 ---- * latencies are larger. */ ! com->fifo_image = t->c_ospeed <= 4800 ! ? FIFO_ENABLE : FIFO_ENABLE | FIFO_RX_HIGH; ! outb(iobase + com_fifo, com->fifo_image); } From owner-freebsd-current Sun Dec 17 16:56:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA13202 for current-outgoing; Sun, 17 Dec 1995 16:56:41 -0800 (PST) Received: from smart.ruhr.de (smart.ruhr.de [193.100.176.36]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA13170 for ; Sun, 17 Dec 1995 16:56:30 -0800 (PST) Received: (from tom@localhost) by smart.ruhr.de (8.7.3/8.7.3) id BAA06788; Mon, 18 Dec 1995 01:56:09 +0100 (MET) To: Nate Williams CC: current@FreeBSD.ORG Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) References: <7748.819191407@time.cdrom.com> <199512172256.PAA21983@rocky.sri.MT.net> From: tom@smart.ruhr.de (Thomas Neumann) Date: 18 Dec 1995 01:56:08 +0100 In-Reply-To: Nate Williams's message of Sun, 17 Dec 1995 15:56:08 -0700 Message-ID: <877mzv5gwn.fsf@smart.ruhr.de> Organization: Ruhr.DE Lines: 42 Sender: owner-current@FreeBSD.ORG Precedence: bulk Folks, don't you think that this "discussion" is gaining a dangerous amount of emotional momentum - lets try to keep it 'professional' instead of 'personal'. Let me bring up a few words from the point of view of a mere -current user (I'm running -current for a few weeks now, but up to now have been doing so in "read-only" mode, scanning this list and trying to develop some feel for what's going on, but if it's true that <20 people really actually *run* -current, well, then my impressions might not be as unimportant as I thought them to be). Personally, I'm experiencing relatively few problems with -current. Maybe I'm just lucky and my combination of hardware components is by mere coincidence one that uses the more stable drivers or whatever - I really can't tell. I, too, have seen the whole system crash for no apparent reason, but this has happened only twice during the last four or five weeks, so I can live with that. Following the discussion, I get the impression that one half of the camp favours a more radical approach for 'making progress' while the other half is willing to lengthen development time in favour of a more stable code-base. Both points of view have their benefits, as I'm sure you're all aware, but I must admit that the "-current" :-] state of affairs is starting to get me worried from a software-engineering point of view. I'm by no means a god-of-kernel-hacking, but years of experience in large-scale application development have told me the lesson that once you allow a large software system to "drift" and destablize beyond a certain point it becomes *very* hard to get the thing back on track. Once you begin losing the grip on where to start debugging in case of problem reports and instead just feel surrounded by "a little thing not working here, a little thing not working there, and 1753 other little things not working over there..." and you don't really know *why the hell* things blow up, then, IMHO, it's time to concentrate on making things stable again instead of going for even more new features. Speaking of feeping creaturism, what actually *is* the list of new creatures scheduled for 2.2? I've never seen an official list of "this is what we're heading for" points. Having said that, I'd sure like to see a more stable -current than todays. -t From owner-freebsd-current Sun Dec 17 19:57:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA27765 for current-outgoing; Sun, 17 Dec 1995 19:57:56 -0800 (PST) Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA27728 for ; Sun, 17 Dec 1995 19:56:52 -0800 (PST) Received: (from mark@localhost) by linus.demon.co.uk (8.7.3/8.7.3) id DAA03748 for current@freebsd.org; Mon, 18 Dec 1995 03:43:59 GMT Message-Id: <199512180343.DAA03748@linus.demon.co.uk> From: mark@linus.demon.co.uk (Mark Valentine) Date: Mon, 18 Dec 1995 03:43:59 +0000 In-Reply-To: Mark Valentine's message of Dec 12, 9:18pm X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: current@freebsd.org Subject: Re: padded files Sender: owner-current@freebsd.org Precedence: bulk > From: mark@linus.demon.co.uk (Mark Valentine) > Date: Tue 12 Dec, 1995 > Subject: padded files > I've had a couple of header files apparently get padded out to an 8K > boundary with NULs during a make world today... Hmm, looks like the barrnet backlog finally cleared! Please note the date on that message. I haven't seen any more of this behaviour since then. Mark. From owner-freebsd-current Sun Dec 17 19:58:06 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA27796 for current-outgoing; Sun, 17 Dec 1995 19:58:06 -0800 (PST) Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA27763 Sun, 17 Dec 1995 19:57:55 -0800 (PST) Received: (from mark@localhost) by linus.demon.co.uk (8.7.3/8.7.3) id DAA03733; Mon, 18 Dec 1995 03:40:34 GMT Message-Id: <199512180340.DAA03733@linus.demon.co.uk> From: mark@linus.demon.co.uk (Mark Valentine) Date: Mon, 18 Dec 1995 03:40:33 +0000 In-Reply-To: Julian Elischer's message of Dec 17, 11:42pm X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: current@freebsd.org, hackers@freebsd.org Subject: Re: FreeBSD-current-stable ??? Sender: owner-current@freebsd.org Precedence: bulk I think the problem of a less-stable-than-usual -current is basically self-fixing (users yell; contributors think about how they might improve their testing), and requires no fundamental change in philosophy. People should either run releases or snaps, or be prepared to help on the debugging (how about enabling DDB by default in -current GENERIC? ;-) These choices are a wonderful part of this project. I'm speaking as one who lives dangerously with -current on my only home system, backup device at the ready, and very rarely has to boot /kernel.old for a few days. Mark. From owner-freebsd-current Sun Dec 17 21:08:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA02418 for current-outgoing; Sun, 17 Dec 1995 21:08:02 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA02364 Sun, 17 Dec 1995 21:07:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id VAA10399; Sun, 17 Dec 1995 21:03:52 -0800 To: Bruce Evans cc: andreas@knobel.gun.de, julian@jhome.dialix.com, cracauer@wavehh.hanse.de, current@freebsd.org, hackers@freebsd.org, jkh@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Mon, 18 Dec 1995 06:11:27 +1100." <199512171911.GAA17231@godzilla.zeta.org.au> Date: Sun, 17 Dec 1995 21:03:51 -0800 Message-ID: <10396.819263031@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > >> Hi FreeBSD core team ! > >> > >> [ Possibly I'm speaking for many other people here ] > >It's possible. > > Possibly for non-developers :-). I think that's something of a cheap shot. Even developers aren't always blessed with a surfeit of hardware. I mentioned that I myself had been somewhat "scared away" from -current, namely because the only machine I have available for running -current is also my gateway machine, and if it starts crashing I'm off the air. I like being able to run current and see what people are up to, helping out if I can, but I can't afford to be radically destabilised by it, and I think a lot of other folks are saying here that they can't either. JOrdan From owner-freebsd-current Sun Dec 17 21:15:51 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA02768 for current-outgoing; Sun, 17 Dec 1995 21:15:51 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA02759 Sun, 17 Dec 1995 21:15:47 -0800 (PST) From: John Dyson Message-Id: <199512180515.VAA02759@freefall.freebsd.org> Subject: Re: ISP state their FreeBSD concerns To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Sun, 17 Dec 1995 21:15:47 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199511121600.KAA26310@brasil.moneng.mei.com> from "Joe Greco" at Nov 12, 95 10:00:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > > > > 8. File creation (particularly directories) appears to be slow compared > > > to other BSD-like systems. They say the stats for INN and CNEWS > > > for articles processed per second are quite a bit lower than that > > > on some "other" systems. They say that file deletion seems to be > > > a bit slower than BSDI, but not by much. I think they are talking > > > 2.0.5 on this item, although one ISP was experimenting with 1026 SNAP. > > > > I am working on this stuff right now. Give me benchmarks!!!! I'll > > do what I can. > > :-( > > I have a little suite of programs I use for performance testing. The tests > are absolutely slanted towards news server type applications. The one in > particular I will quote is "small-file-write.c", a program that writes 10000 > files in subdirectories, creating the subdirectories if needed (much like a > news server would do). So the "first run" numbers include the time needed > to make dirs: > > Slowaris 5.4 - SS10/30 - 64MB RAM (SCSI II, reasonable drive) > > 10000 files in 332 seconds - first run > 10000 files in 20 !!! seconds - second run > > Slowaris 5.4 - SS10/30 - 64MB RAM (SCSI II, Barracuda drive) > > 10000 files in 249 seconds - first run > 10000 files in 13 !!! seconds - second run > > Slowaris 5.4 - SS10/30 - 64MB RAM - PrestoServe (SCSI II, Barracuda drive) > > 10000 files in 76 seconds - first run > 10000 files in 12 seconds - second run > > FreeBSD 2.0.5R - ASUS SP3G AMD 486DX2/66 + NCR810 - 8MB (SCSI II, reasonable > drive) > > 10000 files in 620 seconds - first run :-( :-( > 10000 files in 310 seconds - second run :-( :-( :-( !! > > FreeBSD 1026-SNAP - ASUS SP3G AMD 486DX4/100 + NCR810 - 48MB (SCSI II, SLOW > drive, fs mounted -o async) > > 10000 files in 569 seconds - first run :-( :-( > 10000 files in 207 seconds - second run :-( :-( :-( !! > > Now, I can't swear that by tweaking newfs options, etc., it isn't able to > improve this - I simply haven't tried because I didn't realize until just > now how abominable this performance was. Does anybody have advice about > what might be tweakable to help this? This is really sad. > > The program itself: > > #include > #include > #include > #include > #include > #include > > char *pathn(int x) > { > static char *buffer[1024]; > int d1, d2, d3; > > d1 = x; > x /= 10; > d1 -= x * 10; > d2 = x; > x /= 10; > d2 -= x * 10; > d3 = x; > x /= 10; > d3 -= x * 10; > sprintf(buffer, "%d/%d/%d/%d", d1, d2, d3, x); > return(buffer); > } > > > > > > int writef(char *name) > { > int fd; > char *ptr; > > if ((fd = open(name, O_CREAT|O_RDWR, 0644)) < 0) { > if (errno == ENOENT) { > ptr = name; > while (ptr = strchr(ptr, '/')) { > *ptr = '\0'; > if (mkdir(name, 0755) < 0) { > if (errno != EEXIST) { > perror(name); > exit(1); > } > } > *ptr++ = '/'; > } > return(writef(name)); > } else { > perror(name); > exit(1); > } > } else { > close(fd); > } > } > > > > > > int main() > { > int i, n; > time_t tm = time(NULL); > n = 10000; > > for (i = 0; i < n; i++) { > writef(pathn(i)); > if (! (i % 100)) { > printf("%d..", i); > fflush(stdout); > } > } > printf("\n%d files in %d seconds\n", n, time(NULL) - tm); > exit(0); > } > From owner-freebsd-current Sun Dec 17 22:15:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06153 for current-outgoing; Sun, 17 Dec 1995 22:15:03 -0800 (PST) Received: from sting.artisoft.com (sting.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA06141 Sun, 17 Dec 1995 22:14:59 -0800 (PST) Received: (from mday@localhost) by sting.artisoft.com (8.6.9/8.6.9) id XAA08133; Sun, 17 Dec 1995 23:14:27 -0700 Date: Sun, 17 Dec 1995 23:14:27 -0700 From: Matt Day Message-Id: <199512180614.XAA08133@sting.artisoft.com> To: dyson@FreeBSD.ORG, terry@lambert.org Subject: Re: Page management in BSD Cc: current@FreeBSD.ORG, kato@eclogite.eps.nagoya-u.ac.jp, peter@jhome.DIALix.COM, winter@jurai.net Sender: owner-current@FreeBSD.ORG Precedence: bulk John Dyson wrote: > > > I have been evaluating the possibility of the VM system properly > > > supporting ill constructed a.out formats (like those with 1K offset) > > > and it would not be too hard. It would break coherency -- but > > > would add maybe 25-50 lines of code (very simple.) Since it is > > > bad (not allowed) to modify a running binary anyway, the cost (in > > > functionality) is low. I definitely plan to add it for 2.2. But > > > if someone has a better (easier) solution -- PLEASE go for it!!! > > > > You should talk to Matt Day (mday@elbereth.org). He has been working > > on VOP_GETPAGE/VOP_PUTPAGE style linear address caching modification > > (ala SunOS/SVR4) if you think this will completely torpedo coherency. > > > > You would have to get the details from him; he was talking about > > rolling the changes back in. > > > I think that the SVR4 approach is not very good -- I hope he isn't > planning on faulting into kernel space either. There are some significant > re-dos happening in FreeBSD right now -- and the relationship of buffers and > I/O is in flux. But -- I definitely do not want to shoot down anything that > might be good .... Ask him to get into contact with me so that we can > coordinate the efforts. (Hopefully he isn't trying to do exactly what SVR4 > does :-)). Terry neglected to explain one very important thing: the work I'm doing is for a Win95 file system project where I'm forced to use Win95's memory management system if I want my disk cache memory pool to dynamically grow and shrink depending on available system memory. Unfortunately, there are only two Win95 memory management facilities that I can use to accomplish this goal: a simple memory allocation mechanism which is too limited and wasteful for my liking, and a mechanism by which I can install my own VM pager and get called by the Win95 VM system on page-in and page-out events. As I explored the possibility of using this paging mechanism to manage my disk cache memory pool, I realized that the SVR4 disk cache mechanism is better suited to this facility than the traditional Unix buffer cache mechanism. So, that's why I'm exploring the SVR4 way. I agree, just the SVR4 way will definitely not be good enough for what we want, and I had planned on tailoring the mechanism to best meet my exact needs anyway (for example, I don't have to worry about supporting complexities like memory-mapped files), so the end result could be quite different from both the SVR4 and the FreeBSD way. Anyway, the thought had occured to me that the VOP_GETPAGE/VOP_PUTPAGE code might be useful to the FreeBSD project, to help simplify the vnode pager (as the comment at the top of vnode_pager.c suggests). If this proves to be true, I'll certainly supply the necessary patches. As for the rest of my work, I suspect it will be too tailored to Win95 to be of any use to FreeBSD. When my project is completed, I think I'll be very interested in discussing and helping to work on the current FreeBSD VM/buffer cache mechanism; for example, I'd be very interested to know about the significant changes you mentioned. Thanks very much, Matt Day From owner-freebsd-current Sun Dec 17 22:26:19 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06456 for current-outgoing; Sun, 17 Dec 1995 22:26:19 -0800 (PST) Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA06449 Sun, 17 Dec 1995 22:26:07 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id IAA04837; Mon, 18 Dec 1995 08:26:02 +0200 Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.6.9) with SMTP id IAA26327; Mon, 18 Dec 1995 08:26:01 +0200 (SAT) Message-Id: <199512180626.IAA26327@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: davidg@Root.COM cc: sos@freebsd.org, current@freebsd.org, hacker@freebsd.org Subject: Re: FreeBSD-current-stable ??? Date: Mon, 18 Dec 1995 08:25:59 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk David Greenman wrote: > >> >I run -currrent (up until last week) on my machine at TFS.com > >> >and I have had NO troubles with it... > >> > >> I have had only one serious problem (2 core dumps apparently caused by > >> some vm change in the last month). > > > >You must have another current than most of us :) :) > > Actually, I haven't had any problems with -current, either. Just another data point for this graph; I had about 2 weeks of hassles while a make world would not complete without a bit of help, and then 2 days of a messed kernel (some was fixed as soon as I reported it (KERNFS)). It has been more stable, but for me it has not been as bad as it seems for some folks. OTOH, when I see lots of problem repots that are out of my league, I back off and wait for the appropriate commits :-> :-> M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Mon Dec 18 00:01:10 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09568 for current-outgoing; Mon, 18 Dec 1995 00:01:10 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09561 for ; Mon, 18 Dec 1995 00:01:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id AAA10726; Mon, 18 Dec 1995 00:00:39 -0800 To: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Sun, 17 Dec 1995 12:50:34 PST." <19611.819233434@freefall.freebsd.org> Date: Mon, 18 Dec 1995 00:00:38 -0800 Message-ID: <10724.819273638@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk [ cc: -= -hackers ] > > I think we're in violent agreement as to goals here, Poul, it's just the desired methods where we have some divergence. I don't think that our wishes are necessarily mutually exclusive, either. I think that -current can be good enough for *everyone* with just a little more effort being exerted. I do not speak as one who's hands are free of blood, either. I've certainly spammed -current few enough times, but I've also seen -current a lot less scary than it is right now. Maybe we could try to stagger these changes in a somewhat more coordinated fashion? Maybe we could even just go around the table once in -core and post a "what I'm up to and expect to be committing over the next 3 months" sort of thing? :-) Jordan From owner-freebsd-current Mon Dec 18 00:37:01 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA11258 for current-outgoing; Mon, 18 Dec 1995 00:37:01 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA10998 Mon, 18 Dec 1995 00:31:35 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (134.100.239.2) with smtp id ; Mon, 18 Dec 95 09:28 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for hackers@FreeBSD.org id ; Mon, 18 Dec 95 09:28 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA01417; Mon, 18 Dec 95 09:17:38 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9512180817.AA01417@wavehh.hanse.de> Subject: Re: FreeBSD-current-stable ??? To: Andreas@wavehh.hanse.de, Klemm@wavehh.hanse.de, Date: Mon, 18 Dec 1995 09:17:37 +0100 (MET) Cc: current@FreeBSD.org, hackers@FreeBSD.org, jkh@FreeBSD.org Reply-To: cracauer@wavehh.hanse.de X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk As I am the one who is named here, let me just clarify what my position is. I couldn't decide whether running NetBSD or FreeBSD is the better system for my work. I wrote down some of the experiences and made them available by WWW. In this document, I explained that one reason I feel more comfortable with NetBSD for now is that I can have one machine running -current for production use. Every problem I encounter can be fixed on that machine and the fix can be brought back into -current (actually, the NetBSD community is quite active in those system parts I encounter problems in and most problems are fixed before I get my diffs ready). Or in other words, NetBSD makes it easier to engage in a useful way without investing too much time, while engaging in FreeBSD would require more work (but possibly pay back more). I think the way FreeBSD organizes things by now is just right for their (your, our) needs. Having only one source tree as NetBSD does (ok, sort of) is not an option because much more modifications are done and one experimental vehicle is needed. I don't see how having a third source tree could help, since I can't imagine a mechanism to keep the "middle" one (that one that could qualify for production use) to the stability that is needed. The NetBSD way of organizing development just doesn't fit what I think FreeBSD is. The URL of the comparison is http://www.leo.org/pub/comp/os/bsd/cracauer/ The document is available in German language only. I consider the German version a "beta test", with the options of either translating it after some people looked over it or to remove it if I have to take too much heat. BTW, I'm just snarfing FreeBSD-current to get an own impression of how stable it is. I'm pretty sure, though, that it is usable, but not as usable for a production system as NetBSD-current is. Happy Hacking Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer - Fax +49 40 522 85 36 BSD User Group Hamburg, Germany - No NeXTMail anymore, please. Copyright 1995. Redistribution via Microsoft Network is prohibited From owner-freebsd-current Mon Dec 18 00:55:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA11729 for current-outgoing; Mon, 18 Dec 1995 00:55:16 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA11724 for ; Mon, 18 Dec 1995 00:55:13 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id JAA21259; Mon, 18 Dec 1995 09:54:05 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Mon, 18 Dec 1995 00:00:38 PST." <10724.819273638@time.cdrom.com> Date: Mon, 18 Dec 1995 09:54:04 +0100 Message-ID: <21257.819276844@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > our wishes are necessarily mutually exclusive, either. I think that > -current can be good enough for *everyone* with just a little more > effort being exerted. Jordan, I think that all the people involved are as cautious as they can be, I don't think you will ever see a more stable -current. If people want to be on a child-proof bleeding edge, they got bigger problems than -current. > I do not speak as one who's hands are free of > blood, either. I've certainly spammed -current few enough times, but > I've also seen -current a lot less scary than it is right now. Jordan, I don't think that -current has been as stable as it is now at any period I can ever remember, unless somebody had swung the titanium release-sword low over the heads of committeres for a long period of time. > Maybe > we could try to stagger these changes in a somewhat more coordinated > fashion? Maybe we could even just go around the table once in -core > and post a "what I'm up to and expect to be committing over the next 3 > months" sort of thing? :-) I think -core isn't enough for that. But anyway, here goes: I intend to continue to isolate the scope of variables as far as I can get it. This may from time to time make a custom kernel uncompilable, as my test-set is GENERIC and LINT. I would also like to point out that we need a lot of user-space hackers too, so if people can't run -current on their box, there is still plenty of challenging tasks to jump on. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Dec 18 01:34:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA13905 for current-outgoing; Mon, 18 Dec 1995 01:34:30 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA13897 for ; Mon, 18 Dec 1995 01:34:24 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id KAA21503; Mon, 18 Dec 1995 10:30:05 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Bruce Evans cc: roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG Subject: Re: Mouse not working for two days In-reply-to: Your message of "Mon, 18 Dec 1995 11:51:05 +1100." <199512180051.LAA27345@godzilla.zeta.org.au> Date: Mon, 18 Dec 1995 10:30:05 +0100 Message-ID: <21501.819279005@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG Precedence: bulk Sorry about this mess, I didn't mean to commit the Startech changes, but they slipped in by mistake. Nuke them if it helps. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Dec 18 01:38:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA14372 for current-outgoing; Mon, 18 Dec 1995 01:38:20 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA14343 Mon, 18 Dec 1995 01:38:12 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id KAA21485; Mon, 18 Dec 1995 10:27:05 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: "Rodney W. Grimes" cc: phk@freefall.freebsd.org (Poul-Henning Kamp), current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Sun, 17 Dec 1995 16:53:03 PST." <199512180053.QAA11101@GndRsh.aac.dev.com> Date: Mon, 18 Dec 1995 10:27:04 +0100 Message-ID: <21483.819278824@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org Precedence: bulk > ... > > > I have had only one serious problem (2 core dumps apparently caused by > > > some vm change in the last month). > > > > I have some bogons, but they are quite likely HW actually. (Don't worry > > Rod, I just have not got around to flash the boot-patition correctly :-). > > When you do go to flash it, get the 112 version of the BIOS for the > PCI/I-P55TP4XE board as I have qualified that here. Be sure to update > both the BIOS and the bios boot-partition (requires you to move the MB > jumper to enable write to the bios boot-code) and then clear the ESCD. I know, that why I havn't done it yet, I need to move all the X-mas presents away to get to the server... > One thing you might try without going to the newest BIOS is drop the > PCI latency timer to 32 clocks, seems ASUS has found that this works > best as the 80 clocks was just to long for some boards and causes some > problems. will try. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Dec 18 04:14:10 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA23171 for current-outgoing; Mon, 18 Dec 1995 04:14:10 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA23166 for ; Mon, 18 Dec 1995 04:14:06 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id EAA00783; Mon, 18 Dec 1995 04:14:01 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id EAA00230; Mon, 18 Dec 1995 04:14:04 -0800 Message-Id: <199512181214.EAA00230@corbin.Root.COM> To: Poul-Henning Kamp cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Mon, 18 Dec 95 09:54:04 +0100." <21257.819276844@critter.tfs.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 18 Dec 1995 04:14:03 -0800 Sender: owner-current@freebsd.org Precedence: bulk >But anyway, here goes: I intend to continue to isolate the scope of >variables as far as I can get it. This may from time to time make >a custom kernel uncompilable, as my test-set is GENERIC and LINT. Please don't lose sight of the fact that changes like this can very easily introduce new bugs. Our linker doesn't complain about multiple declarations of a common symbol...so if these exist, making variables that are supposed to be common into private/static will introduce "interesting" new bugs. -DG From owner-freebsd-current Mon Dec 18 04:29:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA23524 for current-outgoing; Mon, 18 Dec 1995 04:29:26 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA23518 for ; Mon, 18 Dec 1995 04:29:23 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id NAA21859; Mon, 18 Dec 1995 13:27:11 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: davidg@Root.COM cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Mon, 18 Dec 1995 04:14:03 PST." <199512181214.EAA00230@corbin.Root.COM> Date: Mon, 18 Dec 1995 13:27:10 +0100 Message-ID: <21857.819289630@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > >But anyway, here goes: I intend to continue to isolate the scope of > >variables as far as I can get it. This may from time to time make > >a custom kernel uncompilable, as my test-set is GENERIC and LINT. > > Please don't lose sight of the fact that changes like this can very easily > introduce new bugs. Our linker doesn't complain about multiple declarations > of a common symbol...so if these exist, making variables that are supposed to > be common into private/static will introduce "interesting" new bugs. I am very careful. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Dec 18 05:15:07 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA25506 for current-outgoing; Mon, 18 Dec 1995 05:15:07 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA25463 Mon, 18 Dec 1995 05:14:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id FAA11611; Mon, 18 Dec 1995 05:13:01 -0800 To: Tom Samplonius cc: John Dyson , paul@netcraft.co.uk, andreas@knobel.gun.de, current@FreeBSD.ORG, hackers@FreeBSD.ORG, cracauer@wavehh.hanse.de, jkh@FreeBSD.ORG Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Sun, 17 Dec 1995 15:27:17 PST." Date: Mon, 18 Dec 1995 05:13:01 -0800 Message-ID: <11609.819292381@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG Precedence: bulk We usually do this in "sweeps", where you try to merge in as many "obvious bug fixes" as you can without getting too out of control. I don't think anyone's quite worked up the bottle to do it again for 2.1.1 just yet. :-) Jordan > While this discussion about -current is all very nice, but what I want > to know, is anyone still doing bug-hunting through the -stable tree? > > Tom From owner-freebsd-current Mon Dec 18 07:34:06 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA01805 for current-outgoing; Mon, 18 Dec 1995 07:34:06 -0800 (PST) Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA01779 for ; Mon, 18 Dec 1995 07:33:41 -0800 (PST) Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id PAA18935 for FreeBSD-current@FreeBSD.org; Mon, 18 Dec 1995 15:33:20 GMT From: Paul Richards Message-Id: <199512181533.PAA18935@server.netcraft.co.uk> Subject: Re: FreeBSD-current-stable ??? To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Mon, 18 Dec 1995 15:33:19 +0000 (GMT) In-Reply-To: <199512171731.JAA09419@freefall.freebsd.org> from "John Dyson" at Dec 17, 95 09:31:26 am Reply-to: paul@netcraft.co.uk X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk Trimmed an out of controll CC line to just be -current. In reply to John Dyson who said > > A make world was not done, and if someone would donate a reasonable > machine to me to let me do so -- it would be very nice. I probably > have the least powerful machine of any major contributor (and have > only one.) Those with expensive high power machines are welcome to > help. (Machines bigger than a 3 yr old 20MB 486/66 :-)). > It's not *that* small. Geeze, remember when we started, I had a 4Mb 25Mhz 486 when we did 1.0, things have changed a lot in the last few years :-) > The kernel did work -- and there was some chaff (a bug in sys_process.c) > -- oh, by the way did the 1Tb changes break things -- or was it the header file > changes/improvements???? All I had to do to get ps working again was to > rebuild libkvm/ps.... The vm header file changes, I didn't think you were responsible for that, I was using the 1Tb changes as an example of something where I would expect the odd bug to slip through since simply checking it compiles and even running it for a while is not going to flush out every possible situation. This is exactly what -current IS for. Testing out totally new code to flush out those unexpected bugs. You do run current at a risk to your system since a filesystem or vm bug could be very nasty, that's the sacrifice you make. What I don't like to see though is a situation where the tree simply wouldn't compile. It wasn't even a simple oversight, it was damn clear no attempt had been made to compile the tree because a whole load of utils just plain simple wouldn't build because the vm header files had changed. There's just no excuse for that. If you don't have a machine that you're willing to run a make world on then don't play in areas that require a make world to validate them. I also disagree with Poul's suggestion that people go hack user-land code in 2.1 for 2 reasons. 1) You'd have to be pretty selective in what you did for it to seamlessly drop into -current since all sorts of fundamental things can change in -current, like header files, mk files, malloc, sysctl :-) etc. It's not really a good idea to tell people to go and work in 2.1 and really is just a cop out from addressing the real problem which is that -current is being hacked without any clear focus as to where it's headed. 2) It's *IMPORTANT* to have people actually running -current even if they're not actively developing. If only a tiny number of active developers are hacking -current then we'll never have enough of an user base for that branch to find all the bugs that crop up from diverse use. I've advocated having an actual plan of what features to bring in for a particular release in the past but -core always felt this was a restriction of volunteers freedom to give what they can when they can. I still think that for a single release there should be one or two main developments and that others should wait until the next release. Releases would happen more often that way so people wouldn't have to wait that long before it was their turn to bring in their idea. While they're waiting for their turn they could get it that much more polished and perhaps it would come into -current mostly working :-) -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Mon Dec 18 08:02:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA03288 for current-outgoing; Mon, 18 Dec 1995 08:02:05 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA03281 for ; Mon, 18 Dec 1995 08:02:01 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id RAA22181; Mon, 18 Dec 1995 17:00:48 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: paul@netcraft.co.uk cc: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Mon, 18 Dec 1995 15:33:19 GMT." <199512181533.PAA18935@server.netcraft.co.uk> Date: Mon, 18 Dec 1995 17:00:48 +0100 Message-ID: <22179.819302448@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org Precedence: bulk > I also disagree with Poul's suggestion that people go hack user-land > code in 2.1 for 2 reasons. > > 1) You'd have to be pretty selective in what you did for it to > seamlessly drop into -current since all sorts of fundamental things > can change in -current, like header files, mk files, malloc, sysctl > :-) etc. It's not really a good idea to tell people to go and work > in 2.1 and really is just a cop out from addressing the real problem > which is that -current is being hacked without any clear focus as to > where it's headed. >I< don't know of any interface changes yet between 2.1 and 2.2 There is no change in sysctl(3) there is no change to malloc. I would argue that you missed your shot, unless you can show me a piece of code that needs an ifdef for "post-2.1" > 2) It's *IMPORTANT* to have people actually running -current even if they're > not actively developing. If only a tiny number of active developers are > hacking -current then we'll never have enough of an user base for that > branch to find all the bugs that crop up from diverse use. Now this is true, but it doesn't mean that people should hack around in their kernels, does it ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Dec 18 08:28:25 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA04877 for current-outgoing; Mon, 18 Dec 1995 08:28:25 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA04869 for ; Mon, 18 Dec 1995 08:28:15 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id QAA00761; Mon, 18 Dec 1995 16:26:17 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 18 Dec 1995 16:25:59 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id QAA05747; Mon, 18 Dec 1995 16:25:54 GMT From: Paul Richards Message-Id: <199512181625.QAA05747@cadair.elsevier.co.uk> Subject: Re: FreeBSD-current-stable ??? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Mon, 18 Dec 1995 16:25:54 +0000 (GMT) Cc: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) In-Reply-To: <22179.819302448@critter.tfs.com> from "Poul-Henning Kamp" at Dec 18, 95 05:00:48 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Poul-Henning Kamp who said > > >I< don't know of any interface changes yet between 2.1 and 2.2 There > is no change in sysctl(3) there is no change to malloc. I would > argue that you missed your shot, unless you can show me a piece of > code that needs an ifdef for "post-2.1" That's really not the issue. I'm not expecting such clear incompatibilties that an #ifdef 2.1 would be required (although the vm header changes would in fact require that so there you are, I have an example). It's the runtime environment as much as anything that's an issue. So many bugs have been found because of the new malloc, which is a good thing but that wouldn't happen if all the folks who want to do user-land development stick to 2.1. The yp code in -current is evolving, the yp code in 2.1 might not even exist in -current. There are loads more examples I could think up if I didn't have better things to do. It should be clear to everyone that it's a dumb idea to go and tell people to work on user-land code under a different version of the OS. > > > 2) It's *IMPORTANT* to have people actually running -current even if they're > > not actively developing. If only a tiny number of active developers are > > hacking -current then we'll never have enough of an user base for that > > branch to find all the bugs that crop up from diverse use. > > Now this is true, but it doesn't mean that people should hack around > in their kernels, does it ? No, I wasn't disagreeing that there's lots of user-land things to do. I was arguing against telling them to work in a 2.1 environment. I think it might be instructive if you grabbed something from 2.1 and tried to compile it under -current. I think point 2 is much more important than point 1 anyway. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Mon Dec 18 08:37:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA05528 for current-outgoing; Mon, 18 Dec 1995 08:37:54 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA05519 for ; Mon, 18 Dec 1995 08:37:44 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA23704; Mon, 18 Dec 1995 09:39:24 -0700 Date: Mon, 18 Dec 1995 09:39:24 -0700 From: Nate Williams Message-Id: <199512181639.JAA23704@rocky.sri.MT.net> To: paul@netcraft.co.uk Cc: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Subject: Re: FreeBSD-current-stable ??? In-Reply-To: <199512181533.PAA18935@server.netcraft.co.uk> References: <199512171731.JAA09419@freefall.freebsd.org> <199512181533.PAA18935@server.netcraft.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk > > A make world was not done, and if someone would donate a reasonable > > machine to me to let me do so -- it would be very nice. I probably > > have the least powerful machine of any major contributor (and have > > only one.) Those with expensive high power machines are welcome to > > help. (Machines bigger than a 3 yr old 20MB 486/66 :-)). > > > > It's not *that* small. Geeze, remember when we started, I had a 4Mb 25Mhz > 486 when we did 1.0, things have changed a lot in the last few years :-) Ahh, the good 'ol days, when you could build a kernel in less than 10 minutes on a 486/33 cause we were using gcc 1.4. The amount of resources required to do development has changed *ALOT* since 1.X. My 486/66 is slower than my 486/33 was in doing a 'make world' in 1.1.5 and 2.X than it was in 1.0. Having said that, I think that it would be nice if the project could help John out with a faster box, but given how difficult that is I'm not sure how. Nate From owner-freebsd-current Mon Dec 18 09:03:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA06892 for current-outgoing; Mon, 18 Dec 1995 09:03:45 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06885 for ; Mon, 18 Dec 1995 09:03:38 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id QAA00890 for ; Mon, 18 Dec 1995 16:58:31 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 18 Dec 1995 16:59:04 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id QAA06312 for FreeBSD-current@FreeBSD.org; Mon, 18 Dec 1995 16:58:56 GMT From: Paul Richards Message-Id: <199512181658.QAA06312@cadair.elsevier.co.uk> Subject: ppp To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Mon, 18 Dec 1995 16:58:56 +0000 (GMT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk I'm having problems with PPP as is someone else I know, on a 2.1 system. Basically, if the line drops then it drops the default route from the routing table and when you next try and use the net instead of it re-dialing you get no route to host errors. I can't find any way to get auto-dialing to work properly. I have to kill ppp and re-start if manually (user-land ppp that is). Killing ppp also has the side-effect of killing the X server. This makes it a real pain to use. On a totally unrelated issue, ftp'ing into freefall drops me in / rather than my home directory using ncftp 2.2.2. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Mon Dec 18 09:59:15 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09622 for current-outgoing; Mon, 18 Dec 1995 09:59:15 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA09617 for ; Mon, 18 Dec 1995 09:59:12 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA23978; Mon, 18 Dec 1995 11:00:17 -0700 Date: Mon, 18 Dec 1995 11:00:17 -0700 From: Nate Williams Message-Id: <199512181800.LAA23978@rocky.sri.MT.net> To: Paul Richards Cc: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Subject: Re: ppp In-Reply-To: <199512181658.QAA06312@cadair.elsevier.co.uk> References: <199512181658.QAA06312@cadair.elsevier.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk > I'm having problems with PPP as is someone else I know, on a 2.1 system. > > Basically, if the line drops then it drops the default route from the > routing table and when you next try and use the net instead of it > re-dialing you get no route to host errors. Umm, if the line drops to your net connection, you have no route to host. This sounds like the correct response. > I can't find any way to get auto-dialing to work properly. I have to > kill ppp and re-start if manually (user-land ppp that is). Hmm, I didn't have any problems with it working when I tested it, although I wasn't happy with it locking up at times and dropping the connection. Since I needed something that worked 'all' the time, I am now using kernel ppp, and I've not had any problems. Someone (Mike Smith?) sent me some example scripts which helped me setup auto-login with kernel mode stuff, and I haven't had any problems since. > Killing ppp also has the side-effect of killing the X server. This makes > it a real pain to use. That's strange. I've not seen either of these problems. If you want I can try and help you debug it if you send me (privately) your ppp configuration files. Also, are you using internal/external modems? Nate From owner-freebsd-current Mon Dec 18 10:17:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA10344 for current-outgoing; Mon, 18 Dec 1995 10:17:26 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA10339 for ; Mon, 18 Dec 1995 10:17:19 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id SAA01147; Mon, 18 Dec 1995 18:15:36 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 18 Dec 1995 18:16:36 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id SAA06921; Mon, 18 Dec 1995 18:16:31 GMT From: Paul Richards Message-Id: <199512181816.SAA06921@cadair.elsevier.co.uk> Subject: Re: ppp To: nate@rocky.sri.MT.net (Nate Williams) Date: Mon, 18 Dec 1995 18:16:31 +0000 (GMT) Cc: FreeBSD-current@FreeBSD.org In-Reply-To: <199512181800.LAA23978@rocky.sri.MT.net> from "Nate Williams" at Dec 18, 95 11:00:17 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Nate Williams who said > > > I'm having problems with PPP as is someone else I know, on a 2.1 system. > > > > Basically, if the line drops then it drops the default route from the > > routing table and when you next try and use the net instead of it > > re-dialing you get no route to host errors. > > Umm, if the line drops to your net connection, you have no route to > host. This sounds like the correct response. Hmm, possibly. Maybe dropping the route isn't the reason it's failing to redial although I don't see how ppp would even get a chance to see the packet if the kernel doesn't know to send the packet out through tun0. Whatever the cause, dial-on-demand is broken and there's at least two of us seeing the problem. Is anyone else having any problems, the common factor between me and this other person is we both use Demon as our ISP. > Hmm, I didn't have any problems with it working when I tested it, > although I wasn't happy with it locking up at times and dropping the > connection. Since I needed something that worked 'all' the time, I am > now using kernel ppp, and I've not had any problems. Someone (Mike Well, I switched from kernel ppp to user-land ppp for similar reasons :-) That was back in 2.0 days though so I guess kernel ppp is a lot better now. Does it do dial-on-demand? > > Killing ppp also has the side-effect of killing the X server. This makes > > it a real pain to use. > > That's strange. I've not seen either of these problems. If you want I > can try and help you debug it if you send me (privately) your ppp > configuration files. Can't do anything until the w/e since I work away from home and it's my home box. I'll send them to you when I get a chance. > > Also, are you using internal/external modems? External. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Mon Dec 18 10:26:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA10828 for current-outgoing; Mon, 18 Dec 1995 10:26:05 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA10823 for ; Mon, 18 Dec 1995 10:25:56 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA24031; Mon, 18 Dec 1995 11:26:56 -0700 Date: Mon, 18 Dec 1995 11:26:56 -0700 From: Nate Williams Message-Id: <199512181826.LAA24031@rocky.sri.MT.net> To: Paul Richards Cc: nate@rocky.sri.MT.net (Nate Williams), FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: <199512181816.SAA06921@cadair.elsevier.co.uk> References: <199512181800.LAA23978@rocky.sri.MT.net> <199512181816.SAA06921@cadair.elsevier.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk [ user-land ppp dropping the routes ] > .... it's failing to > redial although I don't see how ppp would even get a chance to see the > packet if the kernel doesn't know to send the packet out through tun0. > > Whatever the cause, dial-on-demand is broken and there's at least two > of us seeing the problem. Again, if you want to send me your configuration files I'll try and help out. > Is anyone else having any problems, the common factor between me and this > other person is we both use Demon as our ISP. It shouldn't make any difference since the dial-on-demand is all done at the client side. > > Hmm, I didn't have any problems with it working when I tested it, > > although I wasn't happy with it locking up at times and dropping the > > connection. Since I needed something that worked 'all' the time, I am > > now using kernel ppp, and I've not had any problems. Someone (Mike > > Well, I switched from kernel ppp to user-land ppp for similar reasons :-) > That was back in 2.0 days though so I guess kernel ppp is a lot better now. > Does it do dial-on-demand? It does is you put it into a tight loop. :) /etc/ppp/ppp0/Start -------------------- #!/bin/sh # # PPP Auto-Dialer script # # Note: # Yyou *MUST* use -detach mode or else the pppd process will fork # into the background and you will get hundreds of pppd processes trying # to connect to the remote site. The current behavior causes the line to # re-dial when pppd fails, so it acts like a auto-dialer. # PHONE=1234567 USER=Puser PASSWORD=secret DEVICE=cuaa0 while `true`; do /usr/sbin/pppd sri.MT.net:micgate -detach \ connect 'chat -v -f /etc/ppp/ppp0/chat' $DEVICE 115200 # If we fail, wait a little while for the line to settle down sleep 15 done -------------------- /etc/start_if.ppp0 ------------------ # Starting up ppp link echo "STARTING PPP connection to the World" /etc/ppp/ppp0/Start & ------------------ This works quite well for us, although it does require that we uncomment modem lines in /etc/rc.serial to setup line 0, and also modify the speed to 115200. Nate From owner-freebsd-current Mon Dec 18 10:33:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA11353 for current-outgoing; Mon, 18 Dec 1995 10:33:35 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA11348 for ; Mon, 18 Dec 1995 10:33:29 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id SAA01171; Mon, 18 Dec 1995 18:31:05 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 18 Dec 1995 18:31:39 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id SAA07024; Mon, 18 Dec 1995 18:31:34 GMT From: Paul Richards Message-Id: <199512181831.SAA07024@cadair.elsevier.co.uk> Subject: Re: ppp To: nate@rocky.sri.MT.net (Nate Williams) Date: Mon, 18 Dec 1995 18:31:34 +0000 (GMT) Cc: nate@rocky.sri.MT.net, FreeBSD-current@FreeBSD.org In-Reply-To: <199512181826.LAA24031@rocky.sri.MT.net> from "Nate Williams" at Dec 18, 95 11:26:56 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Nate Williams who said > > It does is you put it into a tight loop. :) > > while `true`; do > /usr/sbin/pppd sri.MT.net:micgate -detach \ > connect 'chat -v -f /etc/ppp/ppp0/chat' $DEVICE 115200 > # If we fail, wait a little while for the line to settle down > sleep 15 > done Umm, that's going to re-dial as soon as the line drops isn't it? That's not dial on demand. Dial-on-demand saves my phone bill by only keeping the line up while I'm actually using it. Remember we pay by the minute in Europe, letting the line drop when it's idle is kinda important. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Mon Dec 18 10:36:38 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA11676 for current-outgoing; Mon, 18 Dec 1995 10:36:38 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA11666 for ; Mon, 18 Dec 1995 10:36:32 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA24072; Mon, 18 Dec 1995 11:37:36 -0700 Date: Mon, 18 Dec 1995 11:37:36 -0700 From: Nate Williams Message-Id: <199512181837.LAA24072@rocky.sri.MT.net> To: Paul Richards Cc: nate@rocky.sri.MT.net (Nate Williams), FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: <199512181831.SAA07024@cadair.elsevier.co.uk> References: <199512181826.LAA24031@rocky.sri.MT.net> <199512181831.SAA07024@cadair.elsevier.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk > > It does is you put it into a tight loop. :) > > > > while `true`; do > > /usr/sbin/pppd sri.MT.net:micgate -detach \ > > connect 'chat -v -f /etc/ppp/ppp0/chat' $DEVICE 115200 > > # If we fail, wait a little while for the line to settle down > > sleep 15 > > done > > Umm, that's going to re-dial as soon as the line drops isn't it? That's not > dial on demand. Dial-on-demand saves my phone bill by only keeping the > line up while I'm actually using it. Remember we pay by the minute in > Europe, letting the line drop when it's idle is kinda important. Ahh, right. I keep forgetting that I demand that my connection be up all the time. ;) Nate From owner-freebsd-current Mon Dec 18 10:47:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA12108 for current-outgoing; Mon, 18 Dec 1995 10:47:36 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA12103 for ; Mon, 18 Dec 1995 10:47:32 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id SAA01185; Mon, 18 Dec 1995 18:45:48 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 18 Dec 1995 18:46:22 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id SAA07107; Mon, 18 Dec 1995 18:46:19 GMT From: Paul Richards Message-Id: <199512181846.SAA07107@cadair.elsevier.co.uk> Subject: Re: ppp To: nate@rocky.sri.MT.net (Nate Williams) Date: Mon, 18 Dec 1995 18:46:19 +0000 (GMT) Cc: nate@rocky.sri.MT.net, FreeBSD-current@FreeBSD.org In-Reply-To: <199512181837.LAA24072@rocky.sri.MT.net> from "Nate Williams" at Dec 18, 95 11:37:36 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Nate Williams who said > > > Umm, that's going to re-dial as soon as the line drops isn't it? That's not > > dial on demand. Dial-on-demand saves my phone bill by only keeping the > > line up while I'm actually using it. Remember we pay by the minute in > > Europe, letting the line drop when it's idle is kinda important. > > Ahh, right. I keep forgetting that I demand that my connection be up > all the time. ;) Which has got me wondering, the US folks probably never see this problem since the ISP won't drop the line for them since they don't pay by the minute (at least not many of them). Our ISP drops the line after 2 mins idle time (configurable), if I wanted to keep the line up permanently I could quite easily (and do if I really need to get work done) but that's not how it should work. So, is there anyone out there who has dial-on-demand working i.e. the ISP drops the line when the connection is idle and the modem re-dials automatically next time you send a packet. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Mon Dec 18 10:53:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA12405 for current-outgoing; Mon, 18 Dec 1995 10:53:36 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA12400 for ; Mon, 18 Dec 1995 10:53:28 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA24120; Mon, 18 Dec 1995 11:54:29 -0700 Date: Mon, 18 Dec 1995 11:54:29 -0700 From: Nate Williams Message-Id: <199512181854.LAA24120@rocky.sri.MT.net> To: Paul Richards Cc: nate@rocky.sri.MT.net (Nate Williams), FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: <199512181846.SAA07107@cadair.elsevier.co.uk> References: <199512181837.LAA24072@rocky.sri.MT.net> <199512181846.SAA07107@cadair.elsevier.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk > So, is there anyone out there who has dial-on-demand working i.e. the > ISP drops the line when the connection is idle and the modem re-dials > automatically next time you send a packet. I *had* that working a while back (did you see the patches I posted to make ijppp do auto-redial *always*), but it wasn't robust enough for me since it didn't redial on demand 100% of the time. Sometimes it couldn't get a connection (busy phone line, etc..) and after 20 or so attempts it would blow off and die. It was pretty easy to get working. Is your modem setup to drop DTR when the lines goes down so ppp knows the link went down? Nate From owner-freebsd-current Mon Dec 18 11:03:22 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA12886 for current-outgoing; Mon, 18 Dec 1995 11:03:22 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12880 for ; Mon, 18 Dec 1995 11:03:13 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id TAA01202; Mon, 18 Dec 1995 19:01:32 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 18 Dec 1995 19:02:05 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id TAA07238; Mon, 18 Dec 1995 19:02:01 GMT From: Paul Richards Message-Id: <199512181902.TAA07238@cadair.elsevier.co.uk> Subject: Re: ppp To: nate@rocky.sri.MT.net (Nate Williams) Date: Mon, 18 Dec 1995 19:02:00 +0000 (GMT) Cc: nate@rocky.sri.MT.net, FreeBSD-current@FreeBSD.org In-Reply-To: <199512181854.LAA24120@rocky.sri.MT.net> from "Nate Williams" at Dec 18, 95 11:54:29 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Nate Williams who said > > It was pretty easy to get working. Is your modem setup to drop DTR when > the lines goes down so ppp knows the link went down? Yeah, I used to have this working at a box in work so I know it was OK at some point(same modem, I borrowed it). It probably is a configuration problem but I'm still puzzled about the routing table. If the default route gets dropped then I just can't see how ppp is ever going to get in on the act. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Mon Dec 18 11:06:39 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA13057 for current-outgoing; Mon, 18 Dec 1995 11:06:39 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA13052 for ; Mon, 18 Dec 1995 11:06:33 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA24210; Mon, 18 Dec 1995 12:07:37 -0700 Date: Mon, 18 Dec 1995 12:07:37 -0700 From: Nate Williams Message-Id: <199512181907.MAA24210@rocky.sri.MT.net> To: Paul Richards Cc: nate@rocky.sri.MT.net (Nate Williams), FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: <199512181902.TAA07238@cadair.elsevier.co.uk> References: <199512181854.LAA24120@rocky.sri.MT.net> <199512181902.TAA07238@cadair.elsevier.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk [ PPP on-demand ] > Yeah, I used to have this working at a box in work so I know it was OK > at some point(same modem, I borrowed it). It probably is a > configuration problem but I'm still puzzled about the routing table. If > the default route gets dropped then I just can't see how ppp is ever > going to get in on the act. I think the missing default route is a symptom of the original problem. If ppp isn't setup correctly to auto-dial, it's going to drop the default route just before it exits. If not, it will keep the route (the code is there to do that). Nate From owner-freebsd-current Mon Dec 18 12:01:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA16094 for current-outgoing; Mon, 18 Dec 1995 12:01:05 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA16080 for ; Mon, 18 Dec 1995 12:00:54 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id VAA03888 ; Mon, 18 Dec 1995 21:00:46 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id VAA17515 ; Mon, 18 Dec 1995 21:00:45 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id UAA03157; Mon, 18 Dec 1995 20:28:16 +0100 (MET) From: Ollivier Robert Message-Id: <199512181928.UAA03157@keltia.freenix.fr> Subject: Re: Mouse not working for two days To: bde@zeta.org.au (Bruce Evans) Date: Mon, 18 Dec 1995 20:28:15 +0100 (MET) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.org In-Reply-To: <199512180051.LAA27345@godzilla.zeta.org.au> from "Bruce Evans" at Dec 18, 95 11:51:05 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1449 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that Bruce Evans said: > > Is it really the last part?: When I inserted it back, my mouse started working again so... > Try the following change. It keeps the FIFO enabled and fixes a > bitrotted name and comment. I'll try it on a fresh 1.129 sio.c and keep you informed. Thanks. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Dec 18 00:50:47 MET 1995 From owner-freebsd-current Mon Dec 18 12:57:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA19245 for current-outgoing; Mon, 18 Dec 1995 12:57:29 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA19238 for ; Mon, 18 Dec 1995 12:57:24 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA12329; Mon, 18 Dec 1995 13:52:58 -0700 From: Terry Lambert Message-Id: <199512182052.NAA12329@phaeton.artisoft.com> Subject: Re: ISP state their FreeBSD concerns To: dyson@freefall.freebsd.org (John Dyson) Date: Mon, 18 Dec 1995 13:52:58 -0700 (MST) Cc: jgreco@brasil.moneng.mei.com, current@FreeBSD.org In-Reply-To: <199512180515.VAA02759@freefall.freebsd.org> from "John Dyson" at Dec 17, 95 09:15:47 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-current@FreeBSD.org Precedence: bulk > > I have a little suite of programs I use for performance testing. The tests > > are absolutely slanted towards news server type applications. The one in > > particular I will quote is "small-file-write.c", a program that writes 10000 > > files in subdirectories, creating the subdirectories if needed (much like a > > news server would do). So the "first run" numbers include the time needed > > to make dirs: This is, I think, atypical of most common usage (72% of common usage according to Novell is "Read", 20% is "Write", and 8% is "everything else", including lookups, creates, deletes, etc.). > > Slowaris 5.4 - SS10/30 - 64MB RAM (SCSI II, reasonable drive) > > > > 10000 files in 332 seconds - first run > > 10000 files in 20 !!! seconds - second run [ ... ] > > FreeBSD 2.0.5R - ASUS SP3G AMD 486DX2/66 + NCR810 - 8MB (SCSI II, reasonable > > drive) > > > > 10000 files in 620 seconds - first run :-( :-( > > 10000 files in 310 seconds - second run :-( :-( :-( !! > > > > FreeBSD 1026-SNAP - ASUS SP3G AMD 486DX4/100 + NCR810 - 48MB (SCSI II, SLOW > > drive, fs mounted -o async) > > > > 10000 files in 569 seconds - first run :-( :-( > > 10000 files in 207 seconds - second run :-( :-( :-( !! The "second run" numbers are to be expected. As I recently pointed out, the cache_enter() call is not made on the CREATE nameiop if the file did not already exist. So you are getting 0 cache hits on terminal components. 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-current Mon Dec 18 13:12:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20112 for current-outgoing; Mon, 18 Dec 1995 13:12:45 -0800 (PST) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA20107 for ; Mon, 18 Dec 1995 13:12:34 -0800 (PST) Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id NAA24463; Mon, 18 Dec 1995 13:53:27 GMT Date: Mon, 18 Dec 1995 13:53:27 +0000 (GMT) From: Doug Rabson To: gpalmer@westhill.cdrom.com cc: Terry Lambert , Chuck Robey , winter@jurai.net, peter@jhome.DIALix.COM, kato@eclogite.eps.nagoya-u.ac.jp, current@FreeBSD.ORG Subject: Re: Is the Linux emulator not working for you? In-Reply-To: <5933.819160685@westhill.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Sat, 16 Dec 1995 gpalmer@westhill.cdrom.com wrote: > Terry Lambert wrote in message ID > <199512170007.RAA08528@phaeton.artisoft.com>: > > > Kinda strikes me as funny. FreeBSD emulating Linux emulating Mac. I > > > know it's useful, but it's _still_ funny. > > > Now the burning questions in everyone's minds: > > > 1) Will executor run the Mac version of Insignia systems > > "SoftPC" product? > > Yes > > > 2) Will Insignia systems "SoftPC" product run NetBSD? > > No The new one might.. They have just finished their 486DX emulator. I don't know if it will ship for 68k systems though. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Mon Dec 18 13:16:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20187 for current-outgoing; Mon, 18 Dec 1995 13:16:21 -0800 (PST) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA20178 for ; Mon, 18 Dec 1995 13:16:03 -0800 (PST) Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id NAA24452; Mon, 18 Dec 1995 13:46:54 GMT Date: Mon, 18 Dec 1995 13:46:53 +0000 (GMT) From: Doug Rabson To: Terry Lambert cc: terry@lambert.org, current@FreeBSD.ORG Subject: Re: VOP_READIR revisited In-Reply-To: <199512152002.NAA04666@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Fri, 15 Dec 1995, Terry Lambert wrote: > > > I know that. The search restart isn't an issue except in the NFS case. > > > > > > ...well, and the telldir/seekdir/readdir case, which is currently broken > > > according to existing practice, but technically correct according to > > > the documentation. It's broken *because* it doesn't use cookies or > > > some other restart mechanism. > > > > I think it is technically broken according to the documentation but the > > documentation implies behaviour which is wrong IMHO. In any case the > > abnormal usage which WINE made of this has been changed to something more > > conservative (assuming they integrate Julian's patch that is). > > I agree with this. I'd like that case to operate as it does on SunOS, > since that's as close to a "traditional" behaviour as we'll be able to > find. > > I think that by making the telldir token a 32 bit value instead of a > token will fix the problem instantly. No malloc so no need to maintain > nor free a token list. That would be nice. The current code is disgusting. > > Actually, there's no reason the current implementation can't be fixed > like this using the bit vector translation mechanism I suggested before. > Unfortunately, telldir is documented as returning a 'long', not an off_t, > so that places a 26 (+1) bit limit on the magnitued of the index, and > thus the directory size. Ugh. How embarrasing! A limitation of 134 million entries per directory :-) > > For a token conforming to the documentation, where an intervening > directory compaction could screw up the usability of the token because > of directory compaction (this limit arises because the directory block > buffer in core is a snapshot, taken atomically, of the buffer on disk), > a simple linear 32 bit offset can be used, using the off_t from the > actual fd open on the dir before the getdirentries() call, plus the > offset in the block snapshot of the in core block relative to its > start address. Then using the find-block-scan-forward-to-offset-and- > backof-on-miss approach (which would work right now in place of the > cookies, if you were willing to accept the occasional duplicate entry > in the compaction case), the token can be used to restart the search > after the dir has been reopened. > > The biggest danger here is handling the directory truncation which > 4.4BSD added to the directory compaction. > > > > Don't be too sure you will win by shaving a couple of arguments off the > > function call. All the memory involved is in the cache and writing NULL > > to a cached memory location is virtually free. > > I'm considering the additional overhead of the push of the call arguments > as well as the stack structure element assigns in the VOP_READDIR proper > (which I assume is what you are talking about?). There is also the cycles > burned on the compare/jump in the non-cookie case, and the fact that the > code generation is complicated by having another couple of values that > it will have to invalidate registers on to generate the code (there is > no way of hinting to the compiler that the cookie variables are referenced > in the least common case). The structure element assigns are stores of const values to stack memory which, I claim, is virtually free. The compare jump is 'less free' but the processor's branch prediction might help. The compiler's register usage should not be affected since that is the last basic block in the function. Not that gcc does a particularly good job in register allocation for the x86 anyway :-(. > > > I don't agree that replacing a function which reads and parses a > > directory block in one operation with two functions, one which reads a > > block and one which parses it is code simplification. > > Logical or algorithmic simplification? The two are not tightly bound. > > Basically, this is intended only to delay the disk-directory-contents > to user-snapshot-of-disk-directory-contents-in-user-format. Nothing > more. OK, I think. > > > > > So let's concentrate on the benefits: > > > > > > The primary benefit is a search restart without use of cookies. > > > > > > The secondary benefit is an elimination of the malloc in the "on disk > > > directory entry larger than the 'cannonical' directory entry" case. > > > > How is the malloc eliminated? Surely the caller will have to first > > malloc space for reading the fs-specific directory block and then parse > > that into getdirentries format. It seems to me that in the most common > > case (UFS), the caller will do *more* work, not less. > > Good question. > > It's eliminated because the buffer pointer in the directory vnode is > what is passed around to use in the translation to the user buffer. > > If I VOP_READDIR a directory block from a CDROM, for instance, the > directory block is put in core in a buffer referenced off the vnode. > > I can later use this buffer directly fro my source when translating the > entries to user space. > > This is actually one case where prevalidation of the target of a > copyout is a good idea: it avoids multiple validations in the copyout > case. So a local stack "struct dirent *" is all that's used. > > > > How do we eliminate restart overhead (cookies)? > > [ ... my stuff elided ... ] > > > [code deleted] > > > > How do you propose avoiding the extra copy for UFS where the directory > > does not need converting? > > A copy from the kernel space buffer to the user space buffer must always > take place, unless you start being tricky about process space mapping. > > The sneaky bit is that the VOP_READDIR doesn't ever do a copy, it only > faults in the directory block in question (if it's not in core) or moves > it to the top of the LRU (if it is). The VOP_DIRCVT is the one that > takes the uio: the purpose of a uio in the directory case is to describe > a movement of data from kernel to user space. So your second comment > is correct. I understand now. I actually quite like this idea now. It does make the interface cleaner. > > > The side benefit of handling a directory block that contains more entries > than can be returned in a user directory block falls out from the fact > that we have changed the restart mechanism: now it is possible to take > a single disk directory block and parse it into multiple user dirent > entries in the user supplied buffer. The restart mechanism means that > we can do this "safely". > > > The next question I'd have, if I were reading this for the first time, > is "why not just make the VOP_READDIR act this way itself, throwing out > the old VOP_READDIR and the new VOP_DIRCVT. My thoughts exactly. > > The answer to this is non-obvious: by decoupling the operations, you > allow the copy operation to be "delayed". This is an issue of FS > layering, more than anything else. If I stack several file system > layers on top of each other, the underlying vnode containing the > directory is the one I am interested in having translated. So the > VOP_READDIR *also* takes a (struct vnode **) to be filled out by the > underlying FS that answers the VOP_READDIR request. The VOP_DIRCVT > acts on this vnode. For the majority of cases, this is the same > vnode as the call-down interface for the top level directory being > read, since most FS's are single layer (or integrated layer, like > those which use ufs and have statically placed ufs_* calls in their > VOP tables). But in the nullfs, lofs, or hypothetical compression > or encryption layers, etc., the vp is that of the underlying layer > and thus the VOP_DIRCVT associated with the vp is the correct one > for the data being retrieved. Makes sense, I think. My head hurts. > > > Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com > > PS: Hey! You guys got bought it looks like! 'Fraid so. I haven't had the mind control device implanted yet. At least, I don't think I have. Would I know? Help? -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Mon Dec 18 13:22:37 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20434 for current-outgoing; Mon, 18 Dec 1995 13:22:37 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA20429 for ; Mon, 18 Dec 1995 13:22:30 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA08614; Mon, 18 Dec 1995 16:22:12 -0500 Date: Mon, 18 Dec 1995 16:22:12 -0500 From: "Garrett A. Wollman" Message-Id: <9512182122.AA08614@halloran-eldar.lcs.mit.edu> To: davidg@root.com Cc: current@FreeBSD.ORG Subject: Re: FreeBSD-current-stable ??? In-Reply-To: <199512180021.QAA01420@corbin.Root.COM> References: <199512171946.UAA14386@ra.dkuug.dk> <199512180021.QAA01420@corbin.Root.COM> Sender: owner-current@FreeBSD.ORG Precedence: bulk [CCs trimmed.] < said: >> You must have another current than most of us :) :) > Actually, I haven't had any problems with -current, either. Nor have I, and I just recently upgraded. I /did/ have a number of problems bootstrapping, but once I got a completely clean system installed, everything has been working just fine. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Dec 18 15:48:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA28920 for current-outgoing; Mon, 18 Dec 1995 15:48:34 -0800 (PST) Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA28914 for ; Mon, 18 Dec 1995 15:48:31 -0800 (PST) Received: (from jc@localhost) by irbs.irbs.com (8.6.12/8.6.6) id SAA00407; Mon, 18 Dec 1995 18:44:56 -0500 From: John Capo Message-Id: <199512182344.SAA00407@irbs.irbs.com> Subject: Re: ppp To: p.richards@elsevier.co.uk (Paul Richards) Date: Mon, 18 Dec 1995 18:44:56 -0500 (EST) Cc: nate@rocky.sri.MT.net, FreeBSD-current@FreeBSD.org In-Reply-To: <199512181846.SAA07107@cadair.elsevier.co.uk> from "Paul Richards" at Dec 18, 95 06:46:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk Paul Richards writes: > > So, is there anyone out there who has dial-on-demand working i.e. the > ISP drops the line when the connection is idle and the modem re-dials > automatically next time you send a packet. > I set up bi-directional demand dialing in preperation for an ISDN circuit that never hapened. I used ppp on both ends. Is routed or gated dropping your default route by chance? John Capo From owner-freebsd-current Mon Dec 18 17:42:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06118 for current-outgoing; Mon, 18 Dec 1995 17:42:26 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (Aspen.Woc.Atinc.COM [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA06110 for ; Mon, 18 Dec 1995 17:42:19 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id UAA09195; Mon, 18 Dec 1995 20:40:29 -0500 Date: Mon, 18 Dec 1995 20:40:28 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Paul Richards cc: FreeBSD current mailing list Subject: Re: ppp In-Reply-To: <199512181658.QAA06312@cadair.elsevier.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Mon, 18 Dec 1995, Paul Richards wrote: > Killing ppp also has the side-effect of killing the X server. This makes > it a real pain to use. OUCH! watch out for the "delete ALL" in /etc/ppp/ppp.conf. it works for me using the following: Aspen:[7] tail /etc/rc.local # /usr/sbin/ppp -auto atinc /sbin/ping -c 10 198.138.38.21 # X11 server if [ -x /usr/X11/bin/xdm ]; then echo -n ' xdm'; (sleep 5 ; /usr/X11/bin/xdm) & fi the ping gets ppp to dial and set up the routes BEFORE xdm gets started, else my /etc/ppp/ppp.{conf,linkup} took X down when it reconfiged the routes Aspen:[8] cat /etc/ppp/ppp.conf # # BEWARE: a blank line is a separator! # it ENDS a configuration # and begins an unlabeled configuration # # # settings listed as default are always used. # they may be overridden by settings for a particular site # default: set debug phase lcp chat lqm # set debug phase set device /dev/cua01 set speed 57600 set timeout 18000 disable lqr deny lqr set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" # # assume that we will be talking to rimmer # setup the interface and route to match # correct later in ppp.linkup as needed # accept any address assigned to us # atinc: set phone 0001112222 set login "TIMEOUT 10 mmer>-\\r-mmer>-\\r-mmer> set\\sppp" # set ifaddr 0 198.138.38.21/24 # add 0 0 198.138.38.21 set ifaddr 198.138.38.205 198.138.38.21 add 0 255.255.255.0 198.138.38.21 Aspen:[9] cat /etc/ppp/ppp.linkup # 1) At first, IP address assigned into our side is serched and execute # associated command. # # 2) If it didn't found, then label name specified at startup time is # searched. # # 3) If given label name is not found, then label MYADDR is serched. # # if connecting to A&T delete existing routing entries # add peer as default gateway # atinc: # delete _ALL NEVER use delete ALL with X or xdm running # server will disconnect from keyboard # # DID NOT MATTER still locked up after ppp link was established! # add 0 0 HISADDR MYADDR: add 0 0 HISADDR Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-current Mon Dec 18 17:46:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06437 for current-outgoing; Mon, 18 Dec 1995 17:46:41 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (Aspen.Woc.Atinc.COM [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA06431 for ; Mon, 18 Dec 1995 17:46:37 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id UAA09202; Mon, 18 Dec 1995 20:45:00 -0500 Date: Mon, 18 Dec 1995 20:44:58 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Paul Richards cc: Nate Williams , FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: <199512181816.SAA06921@cadair.elsevier.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Mon, 18 Dec 1995, Paul Richards wrote: > Whatever the cause, dial-on-demand is broken and there's at least two > of us seeing the problem. dial-on-demand, user land ppp, is solid for me. i am running 2.1R with a sportster 14.4 and asus sp3g on-board uarts. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-current Mon Dec 18 21:03:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA22127 for current-outgoing; Mon, 18 Dec 1995 21:03:56 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA22113 for ; Mon, 18 Dec 1995 21:03:52 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA25662; Mon, 18 Dec 1995 22:06:19 -0700 Date: Mon, 18 Dec 1995 22:06:19 -0700 From: Nate Williams Message-Id: <199512190506.WAA25662@rocky.sri.MT.net> To: current@FreeBSD.org Subject: Mis-feature in -current Sender: owner-current@FreeBSD.org Precedence: bulk This one was a strange one, but I finally figured it out. I'm trying to build kernels which contain all of the necessary 'debug' symbols in them, so I'm not compiling the code with '-O'. However, I've noticed that if you don't compile the code with '-O', gcc no longer optimizes out the calls to strlen. What this means is that the kernel will no longer link if you compile any modules which uses strlen(). I'd like to add back the strlen() routine to libkern. Basically, the linker won't pull it in if the kernel is compiled with optimization since it won't be needed, but it's available if any routines aren't optimized. The reason I think this should be brought in is that the current behavior of in-lining strlen() is extremely non-intuitive and very GCC specific. At least if we add back the strlen() code we aren't depending on gcc optimizing away the calls. Any disagreements before I add back strlen to libkern? Nate From owner-freebsd-current Mon Dec 18 21:56:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA24766 for current-outgoing; Mon, 18 Dec 1995 21:56:04 -0800 (PST) Received: from localhost (vet.vet.purdue.edu [128.210.79.50]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA24729 for ; Mon, 18 Dec 1995 21:55:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by localhost (8.6.12/8.6.12) with SMTP id AAA04015 for ; Tue, 19 Dec 1995 00:55:57 -0500 Message-Id: <199512190555.AAA04015@localhost> X-Authentication-Warning: localhost.vet.purdue.edu: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 To: FreeBSD-current@freebsd.org Subject: Re: ppp From: Benjamin Lewis Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Dec 1995 00:55:54 -0500 Sender: owner-current@freebsd.org Precedence: bulk > On Mon, 18 Dec 1995, Paul Richards wrote: > > > Whatever the cause, dial-on-demand is broken and there's at least two > > of us seeing the problem. > > dial-on-demand, user land ppp, is solid for me. i am running > 2.1R with a sportster 14.4 and asus sp3g on-board uarts. > Just to add another weirdness to the pile, iijppp doesn't do demand dialing for me either, but in a different way than I've seen other people mention. I can use it to do a regular dialin with no problem... well, I did have to do a bit of hacking on the source to get it to work 100%. My login script is extremely long (I have to log in to an annex, log into a computer, bounce back to the annex to set it to do 8 bits properly, bounce back to the computer and start up SLiRP), and it wasn't sending the last few characters, and thus failed to actually start up the PPP process. I hacked the length of the array that contains the script (was a long time ago, don't remember details), recompiled, and all was peachy keen for vanilla usage. I could type "ppp vet" and it would happily start the ppp process and everything was great. However, if I tried "ppp -demand vet" and sent a packet, it would dial up, log in, start the remote ppp, and core dump. At that point I gave up hacking on it, and went with pppd. I figured (still do) that either I broke something when I hacked the array length, or that some other weirdness peculiar to my system is responsible, especially as I didn't see hordes of complaints on the newsgroups and mailing lists. Now, I think that maybe my problem might just be an exaggerated version of other people's difficulties. Perhaps the extra long script is just tickling a bug a little harder or something. Since my C coding skills were just about exhuasted by changing [512] to [1024] or whatever it was, I can't be of any more help than sending copies of my config files to interested parties. Oh, the original ppp binary I had was from the last 2.1-SNAP, as is the rest of my userland stuff, but I went and snagged the 2.1.0-RELEASE iijppp source code for my hacking. -Ben "waiting for a kernel written in TCL so *I* can hack on it :)" Lewis -- Benjamin Lewis (blewis@vet.vet.purdue.edu) From owner-freebsd-current Mon Dec 18 23:49:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA28391 for current-outgoing; Mon, 18 Dec 1995 23:49:53 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA28386 for ; Mon, 18 Dec 1995 23:49:51 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with SMTP id NAA21863 for ; Tue, 12 Dec 1995 13:14:46 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA01741; Tue, 12 Dec 1995 14:10:05 -0700 From: Terry Lambert Message-Id: <199512122110.OAA01741@phaeton.artisoft.com> Subject: Re: What is this thing in locore.s? To: bde@zeta.org.au (Bruce Evans) Date: Tue, 12 Dec 1995 14:10:05 -0700 (MST) Cc: current@freebsd.org, terry@lambert.org In-Reply-To: <199512120940.UAA25385@godzilla.zeta.org.au> from "Bruce Evans" at Dec 12, 95 08:40: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-current@freebsd.org Precedence: bulk > >What is the purpose of: > >============================================================================= > > movl %esi,%ebx /* calculate pte offset to ptd */ > > shrl $PGSHIFT-2,%ebx > > addl %esi,%ebx /* address of page directory */ > > addl $((1+UPAGES+1)*NBPG),%ebx /* offset to kernel page tables */ > >============================================================================= > > This initializes %ebx :-). > > >The kernel boots and runs fine without it -- it doesn't seem to do > >anything really useful?!? > > There are some ifdefs before it. Apparently %ebx is left with the > correct value for the case that you use. I think it is left with the > correct value for all cases, but this is only true now that the kernel > is loaded above 1MB. Previously, in the BDE_DEBUGGER case, %ebx was > left pointing to the pte for physical address 0xa0000, while the page > dir was either somewhat lower (at KERNend - KERNBASE) or perhaps at 1MB. > This depends on the page dir going at (KERNend - KERNBASE). I think that %ebx is definitely preserved. Looking at the code from Oct 1994, it was preserved there as well. I don't think the 4.4BSD code was ever loading kernels below 1M, was it? BTW: since you *are* "BDE"... 8-). I am apparently having a problem with either PTD initialization or something else on a second processor. I presume that the envirnment for the second processor should be identical to the environment for the first. Any chance of you looking at my hacked up locore.s and telling me what you think is different between the processor settings after the code has executed? 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-current Tue Dec 19 00:12:57 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA29919 for current-outgoing; Tue, 19 Dec 1995 00:12:57 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA29906 for ; Tue, 19 Dec 1995 00:12:53 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id RAA22411; Mon, 18 Dec 1995 17:34:37 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Paul Richards cc: FreeBSD-current@freebsd.org (FreeBSD current mailing list) Subject: Re: FreeBSD-current-stable ??? In-reply-to: Your message of "Mon, 18 Dec 1995 16:25:54 GMT." <199512181625.QAA05747@cadair.elsevier.co.uk> Date: Mon, 18 Dec 1995 17:34:36 +0100 Message-ID: <22409.819304476@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > In reply to Poul-Henning Kamp who said > > > > >I< don't know of any interface changes yet between 2.1 and 2.2 There > > is no change in sysctl(3) there is no change to malloc. I would > > argue that you missed your shot, unless you can show me a piece of > > code that needs an ifdef for "post-2.1" > > That's really not the issue. I'm not expecting such clear incompatibilties > that an #ifdef 2.1 would be required (although the vm header changes would > in fact require that so there you are, I have an example). You can apply the same fix in 2.1, it's the 2.1 src that is bogus. > It should be clear to everyone that it's a dumb idea to go and tell > people to work on user-land code under a different version of the OS. If people don't have the resources to do kernel work, then it would be stupid to tell them to go away, rather than to point them at user-land. > > Now this is true, but it doesn't mean that people should hack around > > in their kernels, does it ? > > No, I wasn't disagreeing that there's lots of user-land things to do. > I was arguing against telling them to work in a 2.1 environment. I > think it might be instructive if you grabbed something from 2.1 and > tried to compile it under -current. Well, I hope we have a snap of -current in Jan for exactly this reason. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Dec 19 01:53:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA04180 for current-outgoing; Tue, 19 Dec 1995 01:53:27 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA04171 Tue, 19 Dec 1995 01:53:13 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id JAA02209; Tue, 19 Dec 1995 09:51:32 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Tue, 19 Dec 1995 09:52:10 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id JAA01648; Tue, 19 Dec 1995 09:52:08 GMT From: Paul Richards Message-Id: <199512190952.JAA01648@cadair.elsevier.co.uk> Subject: Re: ppp To: jmb@FreeBSD.org (Jonathan M. Bresler) Date: Tue, 19 Dec 1995 09:52:08 +0000 (GMT) Cc: FreeBSD-current@FreeBSD.org In-Reply-To: from "Jonathan M. Bresler" at Dec 18, 95 08:40:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Jonathan M. Bresler who said > > On Mon, 18 Dec 1995, Paul Richards wrote: > > > Killing ppp also has the side-effect of killing the X server. This makes > > it a real pain to use. > > OUCH! > watch out for the "delete ALL" in /etc/ppp/ppp.conf. it works for me using > the following: I will, that'd probably be the problem if it is there. > Aspen:[7] tail /etc/rc.local > # > /usr/sbin/ppp -auto atinc > /sbin/ping -c 10 198.138.38.21 > > > # X11 server > if [ -x /usr/X11/bin/xdm ]; then > echo -n ' xdm'; (sleep 5 ; /usr/X11/bin/xdm) & > fi > > the ping gets ppp to dial and set up the routes BEFORE xdm gets started, > else my /etc/ppp/ppp.{conf,linkup} took X down when it reconfiged the routes Good idea, sounds like this is exactly what's happening. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Tue Dec 19 02:02:55 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA04717 for current-outgoing; Tue, 19 Dec 1995 02:02:55 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA04698 for ; Tue, 19 Dec 1995 02:02:45 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id KAA02272; Tue, 19 Dec 1995 10:01:00 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Tue, 19 Dec 1995 10:01:50 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id KAA01747; Tue, 19 Dec 1995 10:01:44 GMT From: Paul Richards Message-Id: <199512191001.KAA01747@cadair.elsevier.co.uk> Subject: Re: FreeBSD-current-stable ??? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 19 Dec 1995 10:01:44 +0000 (GMT) Cc: FreeBSD-current@freebsd.org In-Reply-To: <22409.819304476@critter.tfs.com> from "Poul-Henning Kamp" at Dec 18, 95 05:34:36 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk In reply to Poul-Henning Kamp who said > > > That's really not the issue. I'm not expecting such clear incompatibilties > > that an #ifdef 2.1 would be required (although the vm header changes would > > in fact require that so there you are, I have an example). > You can apply the same fix in 2.1, it's the 2.1 src that is bogus. How are you going to even find out the bug exists if you're not running -current? If you're seriously suggesting that people should consider doing development work on user land code in 2.1 if they're having problems with -current's stability then things really have got out of control. This has never been a problem before and it shouldn't be now, we want to get more people back to using -current not "recommend" that they use 2.1 instead. We're talking about potential developers here, who are wiling to put up with the odd problem, not end users who need stability. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Tue Dec 19 02:45:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA06975 for current-outgoing; Tue, 19 Dec 1995 02:45:44 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA06965 for ; Tue, 19 Dec 1995 02:45:38 -0800 (PST) Received: from hub.org (hub.org [199.166.238.138]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with ESMTP id IAA07567 for ; Tue, 12 Dec 1995 08:41:28 -0800 (PST) Received: (from scrappy@localhost) by hub.org (8.7.3/8.7.3) id LAA00632; Tue, 12 Dec 1995 11:37:00 -0500 (EST) Date: Tue, 12 Dec 1995 11:36:47 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org Subject: panic: m_copydata Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk HI... Figured I'd send this here too... To: FreeBSD-gnats-submit@freebsd.org Subject: From: scrappy Reply-To: scrappy X-send-pr-version: 3.2 >Submitter-Id: current-users >Originator: Marc G. Fournier >Organization: <> >Confidential: no >Synopsis: panic: m_copydata >Severity: critical >Priority: high >Category: kern >Release: FreeBSD 2.2-CURRENT i386 >Class: sw-bug >Environment: dmesg of system: FreeBSD 2.2-CURRENT #4: Tue Dec 12 05:39:49 EST 1995 scrappy@hub.org:/usr/src/sys/compile/hubdebug CPU: i386DX (386-class CPU) real memory = 8650752 (8448K bytes) avail memory = 6971392 (6808K bytes) DEVFS: ready for devices Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: tvga 9000, 80/132 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16450 lpt0 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 329MB (675450 sectors), 790 cyls, 15 heads, 57 S/T, 512 B/S aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 327MB (670506 512 byte sectors) (aha0:2:0): "CONNER CFA540S 13B0" type 0 fixed SCSI 2 sd1(aha0:2:0): Direct-Access 515MB (1056708 512 byte sectors) (aha0:6:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 sd2(aha0:6:0): Direct-Access 234MB (479350 512 byte sectors) npx0 on motherboard npx0: 387 emulator devfs ready to run WARNING: / was not properly dismounted. config of system: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # GENERIC,v 1.45.2.3 1995/06/05 21:50:41 jkh Exp # machine "i386" cpu "I386_CPU" ident hubdebug maxusers 10 options DEVFS options DODUMP options DDB options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MSDOSFS #MSDOS Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console config kernel root on wd0 options SYSVSHM options SYSVSEM options SYSVMSG controller isa0 #controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 #controller ncr0 controller ahc0 controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console #device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.1 options PCVT_SCREENSAVER options PCVT_PRETTYSCRNS #options "PCVT_NSCREENS=7" #options XSERVER # include code for XFree86 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 >Description: On a reasonably regular basis, I get a 'panic: m_copydata' error and reboot of the system. Having enabled DDB and DODUMP, I'm not getting a 'savecore', but it does put me into the kernel debugger instead of rebooting. Error: panic: m_copydata stopped at _Debugger+0x2b: movb $0,_in_Debugger.98 Trace: _Debugger(f0111fe0,f011d5e4,efbffe94,14) at _Debugger+0x2b _panic(f011d5e3,14,ffffffff,f05f3880,efbfff20) at _panic+0x3b _m_copydata(0,ffffffff,1,f05f38e8,0) at _m_copydata+0x21 _tcp_output(f05a4f00,f061169c,f0611b80,14,efbfff30) at _tcp_output+0x635 _tcp_input(f0611680,14) at _tcp_input+0x13da _ipintr(f0172117,0,efbf0027,27,3c) at _ipintr+0x429 Bad User Frame pointer: 0xefbf9120 I have a /var/crash directory created, but not core dump... In transcribing the Trace to paper, do I need *all* the lines, or is there only one or two that are significant? >How-To-Repeat: >Fix: Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-current Tue Dec 19 02:46:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA07023 for current-outgoing; Tue, 19 Dec 1995 02:46:14 -0800 (PST) Received: from wiley.muc.ditec.de (wiley.muc.ditec.de [194.120.126.9]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA07012 Tue, 19 Dec 1995 02:46:04 -0800 (PST) Received: from vector.enet (slip139-92-42-155.emea.ibm.net [139.92.42.155]) by wiley.muc.ditec.de (8.6.12/8.6.9) with ESMTP id LAA06133; Tue, 19 Dec 1995 11:43:27 +0100 Received: from localhost (localhost [127.0.0.1]) by vector.enet (8.6.12/8.6.9) with SMTP id QAA14441; Mon, 18 Dec 1995 16:56:32 +0100 Message-Id: <199512181556.QAA14441@vector.enet> X-Authentication-Warning: vector.enet: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: sos@freebsd.org, current@freebsd.org Subject: Re: FreeBSD-current-stable ??? Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. (Internet Unix & C Consultants) Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (pending reconfig) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH version 1.6.4 10/10/95 In-reply-to: Your message of "Sun, 17 Dec 1995 16:43:52 PST." <199512180043.QAA01454@corbin.Root.COM> Date: Mon, 18 Dec 1995 16:56:30 +0100 From: "Julian H. Stacey" Sender: owner-current@freebsd.org Precedence: bulk Hi David, Reference: > From: David Greenman > Reply-to: davidg@Root.COM > Subject: Re: FreeBSD-current-stable ??? > Date: Sun, 17 Dec 1995 16:43:52 -0800 > Message-id: <199512180043.QAA01454@corbin.Root.COM> > Cc: current@freebsd.org, hackers@freebsd.org > > Actually, I haven't had any problems with -current, either. I believe cross posting to hackers & current is discouraged ? ( Reason I mention it is that I am using: ~/.procmailrc: :0 * ^Sender:.owner-hackers@FreeBSD.ORG | /usr/local/lib/mh/rcvstore +freebsd/hackers :0 * ^Sender:.owner-current@freebsd.org | /usr/local/lib/mh/rcvstore +freebsd/current So I at least get 2 copies in different places, & end up reading the same thing twice. ) Best Regards, Julian. -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Tue Dec 19 02:47:37 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA07098 for current-outgoing; Tue, 19 Dec 1995 02:47:37 -0800 (PST) Received: from wiley.muc.ditec.de (wiley.muc.ditec.de [194.120.126.9]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA07073 for ; Tue, 19 Dec 1995 02:47:23 -0800 (PST) Received: from vector.enet (slip139-92-42-155.emea.ibm.net [139.92.42.155]) by wiley.muc.ditec.de (8.6.12/8.6.9) with ESMTP id LAA06148; Tue, 19 Dec 1995 11:45:44 +0100 Received: from localhost (localhost [127.0.0.1]) by vector.enet (8.6.12/8.6.9) with SMTP id OAA11252; Mon, 18 Dec 1995 14:24:57 +0100 Message-Id: <199512181324.OAA11252@vector.enet> X-Authentication-Warning: vector.enet: Host localhost didn't use HELO protocol To: Andreas Klemm cc: current@freebsd.org Subject: Re: FreeBSD-current-stable ??? Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. (Internet Unix & C Consultants) Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (pending reconfig) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH version 1.6.4 10/10/95 In-reply-to: Your message of "Sun, 17 Dec 1995 18:36:30 +0100." <199512171736.SAA03816@knobel.gun.de> Date: Mon, 18 Dec 1995 14:24:56 +0100 From: "Julian H. Stacey" Sender: owner-current@freebsd.org Precedence: bulk Hi, Reference: > From: Andreas Klemm > Subject: Re: FreeBSD-current-stable ??? > Date: Sun, 17 Dec 1995 18:36:30 +0100 (MET) > Message-id: <199512171736.SAA03816@knobel.gun.de> .... > If changes doesn't compile, then it's a sign for either > - not tested or > - tested in a too small scope IMHO Then it's time for the commiter to rectify an inappropriate commit ... fast, & then get some sleep :-) > Current should be brought into a state, that more people are > motivated to sup and install it. The goal is, to get some more > good programmers into the boat. Nice idea, just one reservation: I recommend CTM :-) It puts less additional strain on freefall, & needs less local resources too :-) ( A big increase in sup'ers just now would be a problem until we increase sup server sites (in progress)) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Tue Dec 19 04:40:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA13565 for current-outgoing; Tue, 19 Dec 1995 04:40:45 -0800 (PST) Received: (from jkh@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA13559 for current; Tue, 19 Dec 1995 04:40:44 -0800 (PST) Date: Tue, 19 Dec 1995 04:40:44 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199512191240.EAA13559@freefall.freebsd.org> To: current Subject: Yikes! No man page for ypset? Sender: owner-current@FreeBSD.ORG Precedence: bulk I can't help but notice: /c/NetBSD/NetBSD-current/src/usr.sbin/ypset/ypset.8 What's our own problem? :-) Jordan From owner-freebsd-current Tue Dec 19 04:46:39 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA13733 for current-outgoing; Tue, 19 Dec 1995 04:46:39 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA13726 for ; Tue, 19 Dec 1995 04:46:36 -0800 (PST) Received: (from jkh@localhost) by time.cdrom.com (8.6.12/8.6.9) id EAA17333 for current@freefall; Tue, 19 Dec 1995 04:46:00 -0800 Date: Tue, 19 Dec 1995 04:46:00 -0800 From: "Jordan K. Hubbard" Message-Id: <199512191246.EAA17333@time.cdrom.com> To: current@freefall.FreeBSD.org Subject: pcnfsd.. Sender: owner-current@FreeBSD.ORG Precedence: bulk Is freely redistributable software, right? At least that's what the man page says, anyway.. I'm wondering if this isn't something that *should* move out of ports and into the main tree? It currently represents something of an imperfect match, at best, as simply reading the man page or doing the two-step configuration process for it will readily attest. Jordan From owner-freebsd-current Tue Dec 19 05:02:32 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA14559 for current-outgoing; Tue, 19 Dec 1995 05:02:32 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA14554 Tue, 19 Dec 1995 05:02:30 -0800 (PST) Received: from wiley.muc.ditec.de (wiley.muc.ditec.de [194.120.126.9]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with SMTP id NAA22328; Tue, 12 Dec 1995 13:28:12 -0800 (PST) Received: from vector.enet ([139.92.18.129]) by wiley.muc.ditec.de (8.6.12/8.6.9) with ESMTP id WAA02591; Tue, 12 Dec 1995 22:25:07 +0100 Received: (from jhs@localhost) by vector.enet (8.6.12/8.6.9) id WAA00404; Tue, 12 Dec 1995 22:00:48 +0100 Date: Tue, 12 Dec 1995 22:00:48 +0100 From: "Julian Stacey jhs@freebsd.org" Message-Id: <199512122100.WAA00404@vector.enet> To: current@freebsd.org, ports@freebsd.org, gea@vector.enet, bsd-munich@vector.enet Subject: Julian Stacey has lost all mail between Sunday and Tue Dec 12 21:42 Reply-To: "Julian H. Stacey" Sender: owner-current@freebsd.org Precedence: bulk -------- All mail sent to Julian Stacey between Sunday and Tue Dec 12 21:42:50 MEZ 1995 ... has been lost. Anyone waiting for a reply, or anyone who knows someone who sent me something important ..., please let me know, Thanks. Please do not reply direct to this, without pruning the large Cc: line ! Thanks :-) Julian S From owner-freebsd-current Tue Dec 19 06:16:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA29685 for current-outgoing; Tue, 19 Dec 1995 06:16:28 -0800 (PST) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA29653 Tue, 19 Dec 1995 06:16:24 -0800 (PST) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id JAA27171; Tue, 19 Dec 1995 09:14:24 -0500 for Date: Tue, 19 Dec 1995 09:14:24 -0500 From: "Frank E. Terhaar-Yonkers" Message-Id: <199512191414.JAA27171@robin.mcnc.org.mcnc.org> To: jmb@FreeBSD.org, p.richards@elsevier.co.uk Subject: Re: ppp Cc: FreeBSD-current@FreeBSD.org X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@FreeBSD.org Precedence: bulk This is bogus. The phone lines to my house are so crappy that I regularly have to kill ijppp and restart it. I don't want to have to kill all the X stuff as well, before I restart PPP. Running ijppp and X has been a crap shoot. About 1/4 the time, killing ppp locks up the system. What's the problem and why can't we fix it? - Frank >In reply to Jonathan M. Bresler who said >> >> On Mon, 18 Dec 1995, Paul Richards wrote: >> >> > Killing ppp also has the side-effect of killing the X server. This makes >> > it a real pain to use. >> >> OUCH! >> watch out for the "delete ALL" in /etc/ppp/ppp.conf. it works for me using >> the following: > >I will, that'd probably be the problem if it is there. > >> Aspen:[7] tail /etc/rc.local >> # >> /usr/sbin/ppp -auto atinc >> /sbin/ping -c 10 198.138.38.21 >> >> >> # X11 server >> if [ -x /usr/X11/bin/xdm ]; then >> echo -n ' xdm'; (sleep 5 ; /usr/X11/bin/xdm) & >> fi >> >> the ping gets ppp to dial and set up the routes BEFORE xdm gets started, >> else my /etc/ppp/ppp.{conf,linkup} took X down when it reconfiged the routes > >Good idea, sounds like this is exactly what's happening. > >-- > Paul Richards. Originative Solutions Ltd. > Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk > Phone: 0370 462071 (Mobile), +44 1225 447500 (work) > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Tue Dec 19 06:54:01 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA09882 for current-outgoing; Tue, 19 Dec 1995 06:54:01 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA09875 Tue, 19 Dec 1995 06:53:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id GAA18131; Tue, 19 Dec 1995 06:53:13 -0800 To: "Frank E. Terhaar-Yonkers" cc: jmb@FreeBSD.org, p.richards@elsevier.co.uk, FreeBSD-current@FreeBSD.org Subject: Re: ppp In-reply-to: Your message of "Tue, 19 Dec 1995 09:14:24 EST." <199512191414.JAA27171@robin.mcnc.org.mcnc.org> Date: Tue, 19 Dec 1995 06:53:13 -0800 Message-ID: <18129.819384793@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk Maybe what has to happen first is you need to figure out a way of causing ppp to kill your system *without* running X, e.g. so that we can get into ddb and see what's panicing! Jordan > This is bogus. The phone lines to my house are so crappy that I regularly > have to kill ijppp and restart it. I don't want to have to kill all the X > stuff as well, before I restart PPP. Running ijppp and X has been a > crap shoot. About 1/4 the time, killing ppp locks up the system. > > What's the problem and why can't we fix it? > > - Frank > > > >In reply to Jonathan M. Bresler who said > >> > >> On Mon, 18 Dec 1995, Paul Richards wrote: > >> > >> > Killing ppp also has the side-effect of killing the X server. This make s > >> > it a real pain to use. > >> > >> OUCH! > >> watch out for the "delete ALL" in /etc/ppp/ppp.conf. it works for me usi ng > >> the following: > > > >I will, that'd probably be the problem if it is there. > > > >> Aspen:[7] tail /etc/rc.local > >> # > >> /usr/sbin/ppp -auto atinc > >> /sbin/ping -c 10 198.138.38.21 > >> > >> > >> # X11 server > >> if [ -x /usr/X11/bin/xdm ]; then > >> echo -n ' xdm'; (sleep 5 ; /usr/X11/bin/xdm) & > >> fi > >> > >> the ping gets ppp to dial and set up the routes BEFORE xdm gets started, > >> else my /etc/ppp/ppp.{conf,linkup} took X down when it reconfiged the rou tes > > > >Good idea, sounds like this is exactly what's happening. > > > >-- > > Paul Richards. Originative Solutions Ltd. > > Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk > > Phone: 0370 462071 (Mobile), +44 1225 447500 (work) > > > > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\ \ > Frank Terhaar-Yonkers > High Performance Computing and Communications Research > MCNC > PO Box 12889 3021 Cornwallis Road > Research Triangle Park, North Carolina 27709-2889 > fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 > > http://www.mcnc.org/hpcc.html From owner-freebsd-current Tue Dec 19 07:08:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA12557 for current-outgoing; Tue, 19 Dec 1995 07:08:44 -0800 (PST) Received: from dworshak.cs.uidaho.edu (root@dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA12543 for ; Tue, 19 Dec 1995 07:08:39 -0800 (PST) Received: from hoodoo.cs.uidaho.edu (hoodoo.cs.uidaho.edu [129.101.100.34]) by dworshak.cs.uidaho.edu (8.6.12/1.1) with ESMTP id HAA21042; Tue, 19 Dec 1995 07:08:38 -0800 Received: from localhost (localhost [127.0.0.1]) by hoodoo.cs.uidaho.edu (8.6.10/1.0) with SMTP id HAA08739; Tue, 19 Dec 1995 07:05:03 -0800 Message-Id: <199512191505.HAA08739@hoodoo.cs.uidaho.edu> X-Authentication-Warning: hoodoo.cs.uidaho.edu: Host localhost didn't use HELO protocol To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: panic: m_copydata In-reply-to: Your message of "Tue, 12 Dec 1995 11:36:47 PST." Date: Tue, 19 Dec 1995 07:05:02 PST From: faried nawaz Sender: owner-current@freebsd.org Precedence: bulk "Marc G. Fournier" wrote... Trace: _Debugger(f0111fe0,f011d5e4,efbffe94,14) at _Debugger+0x2b _panic(f011d5e3,14,ffffffff,f05f3880,efbfff20) at _panic+0x3b _m_copydata(0,ffffffff,1,f05f38e8,0) at _m_copydata+0x21 _tcp_output(f05a4f00,f061169c,f0611b80,14,efbfff30) at _tcp_output+0x635 _tcp_input(f0611680,14) at _tcp_input+0x13da _ipintr(f0172117,0,efbf0027,27,3c) at _ipintr+0x429 Bad User Frame pointer: 0xefbf9120 i have this same problem. i don't have a crash dump (i crashed yesterday, got mad at /var filling up and deleted them all), but i posted a gdb -k walk-through of a core-dump two weeks ago. i last got a crash due to this yesterday (dec 18). i used to get them once a day (sometimes more frequently). faried. From owner-freebsd-current Tue Dec 19 07:37:10 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA16993 for current-outgoing; Tue, 19 Dec 1995 07:37:10 -0800 (PST) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA16977 Tue, 19 Dec 1995 07:37:06 -0800 (PST) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id KAA02797; Tue, 19 Dec 1995 10:35:26 -0500 for Date: Tue, 19 Dec 1995 10:35:26 -0500 From: "Frank E. Terhaar-Yonkers" Message-Id: <199512191535.KAA02797@robin.mcnc.org.mcnc.org> To: jkh@time.cdrom.com Subject: Re: ppp Cc: FreeBSD-current@FreeBSD.org, jmb@FreeBSD.org, p.richards@elsevier.co.uk X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@FreeBSD.org Precedence: bulk It isn't panicing. It just gets wedged. I did get into DDB 'cause I happened to be at a non-X virtual console. I'm sorry that I don't have enuf experience with ddb (and the kernel wasn't config'd with -g) to get much info. I did force a panic and saved the dump. If you think it's worth looking at. I can set up an account on my box or ftp the dump somewhere. - Frank >Maybe what has to happen first is you need to figure out a way of >causing ppp to kill your system *without* running X, e.g. so that >we can get into ddb and see what's panicing! > > Jordan > >> This is bogus. The phone lines to my house are so crappy that I regularly >> have to kill ijppp and restart it. I don't want to have to kill all the X >> stuff as well, before I restart PPP. Running ijppp and X has been a >> crap shoot. About 1/4 the time, killing ppp locks up the system. >> >> What's the problem and why can't we fix it? >> >> - Frank >> >> >> >In reply to Jonathan M. Bresler who said >> >> >> >> On Mon, 18 Dec 1995, Paul Richards wrote: >> >> >> >> > Killing ppp also has the side-effect of killing the X server. This make >s >> >> > it a real pain to use. >> >> >> >> OUCH! >> >> watch out for the "delete ALL" in /etc/ppp/ppp.conf. it works for me usi >ng >> >> the following: >> > >> >I will, that'd probably be the problem if it is there. >> > >> >> Aspen:[7] tail /etc/rc.local >> >> # >> >> /usr/sbin/ppp -auto atinc >> >> /sbin/ping -c 10 198.138.38.21 >> >> >> >> >> >> # X11 server >> >> if [ -x /usr/X11/bin/xdm ]; then >> >> echo -n ' xdm'; (sleep 5 ; /usr/X11/bin/xdm) & >> >> fi >> >> >> >> the ping gets ppp to dial and set up the routes BEFORE xdm gets started, >> >> else my /etc/ppp/ppp.{conf,linkup} took X down when it reconfiged the rou >tes >> > >> >Good idea, sounds like this is exactly what's happening. >> > >> >-- >> > Paul Richards. Originative Solutions Ltd. >> > Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk >> > Phone: 0370 462071 (Mobile), +44 1225 447500 (work) >> > >> >> \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\ >\ >> Frank Terhaar-Yonkers >> High Performance Computing and Communications Research >> MCNC >> PO Box 12889 3021 Cornwallis Road >> Research Triangle Park, North Carolina 27709-2889 >> fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 >> >> http://www.mcnc.org/hpcc.html > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Tue Dec 19 07:46:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17371 for current-outgoing; Tue, 19 Dec 1995 07:46:03 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA17361 for ; Tue, 19 Dec 1995 07:45:56 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA26516; Tue, 19 Dec 1995 08:48:22 -0700 Date: Tue, 19 Dec 1995 08:48:22 -0700 From: Nate Williams Message-Id: <199512191548.IAA26516@rocky.sri.MT.net> To: "Jordan K. Hubbard" Cc: current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512191246.EAA17333@time.cdrom.com> References: <199512191246.EAA17333@time.cdrom.com> Sender: owner-current@FreeBSD.ORG Precedence: bulk > Is freely redistributable software, right? At least that's what the > man page says, anyway.. I'm wondering if this isn't something that > *should* move out of ports and into the main tree? How useful is it for the general user of FreeBSD? (I'd say a *very* small percentage of users actually have use for it) Nate From owner-freebsd-current Tue Dec 19 07:58:43 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA18101 for current-outgoing; Tue, 19 Dec 1995 07:58:43 -0800 (PST) Received: from ncd.com (firewall-user@welch.ncd.com [192.43.160.250]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA18095 for ; Tue, 19 Dec 1995 07:58:40 -0800 (PST) Received: by ncd.com; id IAA01760; Tue, 19 Dec 1995 08:17:16 -0800 Received: from z-code.z-code.com(192.82.56.21) by welch.ncd.com via smap (g3.0.1) id xma001648; Tue, 19 Dec 95 08:17:02 -0800 Received: from zolaris.z-code.com (zolaris.z-code.com [192.82.56.41]) by z-code.z-code.com (8.6.9/8.6.9) with SMTP id HAA12227; Tue, 19 Dec 1995 07:56:44 -0800 Received: by zolaris.z-code.com (5.x/SMI-SVR4) id AA13629; Tue, 19 Dec 1995 07:54:28 -0800 From: "Ulf Zimmermann" Message-Id: <9512190754.ZM13627@zolaris.z-code.com> Date: Tue, 19 Dec 1995 07:54:27 -0800 In-Reply-To: "Jordan K. Hubbard" "pcnfsd.." (Dec 19, 4:46) References: <199512191246.EAA17333@time.cdrom.com> X-Mailer: Z-Mail (3.2.0 06sep94) To: "Jordan K. Hubbard" , current@freefall.freebsd.org Subject: Re: pcnfsd.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-current@FreeBSD.ORG Precedence: bulk On Dec 19, 4:46, Jordan K. Hubbard wrote: > Subject: pcnfsd.. > Is freely redistributable software, right? At least that's what the > man page says, anyway.. I'm wondering if this isn't something that > *should* move out of ports and into the main tree? It currently represents > something of an imperfect match, at best, as simply reading the man page > or doing the two-step configuration process for it will readily attest. > > Jordan >-- End of excerpt from Jordan K. Hubbard I would say, yes it should be in the main tree, as every "Up-to-date" unix now delivers it. Or least together with their NFS package ;-) Ulf. -- Ulf Zimmermann, NCD Software, 101 Rowland Way, Suite 300, Novato, CA 94945 phone: 415-899-7941, email: ulf@z-code.ncd.com, phone-home: 510-865-0204 ====================================== FreeBSD 2.1.0 is available now! -------------------------------------- FreeBSD: Turning PCs into Workstations ====================================== From owner-freebsd-current Tue Dec 19 08:21:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA19552 for current-outgoing; Tue, 19 Dec 1995 08:21:18 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA19350 for ; Tue, 19 Dec 1995 08:19:37 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id RAA19445 for freebsd-current@freefall.cdrom.com; Tue, 19 Dec 1995 17:21:15 +0100 Date: Tue, 19 Dec 1995 17:21:15 +0100 From: "Christoph P. Kukulies" Message-Id: <199512191621.RAA19445@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: make init fails Sender: owner-current@FreeBSD.ORG Precedence: bulk from an attempt to make world today: cc -O -DDEBUGSHELL -DSECURE -static -o init init.o -L -lutil -ldescrypt init.o: Undefined symbol `_logout' referenced from text segment init.o: Undefined symbol `_logwtmp' referenced from text segment init.o: Undefined symbol `_login_tty' referenced from text segment init.o: Undefined symbol `_logwtmp' referenced from text segment init.o: Undefined symbol `_logwtmp' referenced from text segment *** Error code 1 Stop. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Dec 19 08:30:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA20624 for current-outgoing; Tue, 19 Dec 1995 08:30:48 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA20619 for ; Tue, 19 Dec 1995 08:30:38 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA26625; Tue, 19 Dec 1995 09:32:05 -0700 Date: Tue, 19 Dec 1995 09:32:05 -0700 From: Nate Williams Message-Id: <199512191632.JAA26625@rocky.sri.MT.net> To: "Ulf Zimmermann" Cc: "Jordan K. Hubbard" , current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <9512190754.ZM13627@zolaris.z-code.com> References: <199512191246.EAA17333@time.cdrom.com> <9512190754.ZM13627@zolaris.z-code.com> Sender: owner-current@FreeBSD.ORG Precedence: bulk [ PCNFSD in main FreeBSD source tree ] > I would say, yes it should be in the main tree, as every "Up-to-date" > unix now delivers it. Or least together with their NFS package ;-) Hmm, although Solaris 2.5 is almost out so I can't check it, both Solaris 2.4 and SunOS 4.1 don't ship with pcnfsd. As a matter of fact, I don't know of any commercial OS which delivers it. Nate From owner-freebsd-current Tue Dec 19 08:47:00 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA21685 for current-outgoing; Tue, 19 Dec 1995 08:47:00 -0800 (PST) Received: from ncd.com (firewall-user@welch.ncd.com [192.43.160.250]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA21679 for ; Tue, 19 Dec 1995 08:46:53 -0800 (PST) Received: by ncd.com; id JAA29018; Tue, 19 Dec 1995 09:05:31 -0800 Received: from z-code.z-code.com(192.82.56.21) by welch.ncd.com via smap (g3.0.1) id xma028824; Tue, 19 Dec 95 09:05:10 -0800 Received: from zolaris.z-code.com (zolaris.z-code.com [192.82.56.41]) by z-code.z-code.com (8.6.9/8.6.9) with SMTP id IAA12767; Tue, 19 Dec 1995 08:44:50 -0800 Received: by zolaris.z-code.com (5.x/SMI-SVR4) id AA13687; Tue, 19 Dec 1995 08:42:35 -0800 From: "Ulf Zimmermann" Message-Id: <9512190842.ZM13685@zolaris.z-code.com> Date: Tue, 19 Dec 1995 08:42:33 -0800 In-Reply-To: Nate Williams "Re: pcnfsd.." (Dec 19, 9:32) References: <199512191246.EAA17333@time.cdrom.com> <9512190754.ZM13627@zolaris.z-code.com> <199512191632.JAA26625@rocky.sri.MT.net> X-Mailer: Z-Mail (3.2.0 06sep94) To: Nate Williams , "Ulf Zimmermann" Subject: Re: pcnfsd.. Cc: "Jordan K. Hubbard" , current@freefall.freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-current@FreeBSD.ORG Precedence: bulk On Dec 19, 9:32, Nate Williams wrote: > Subject: Re: pcnfsd.. > [ PCNFSD in main FreeBSD source tree ] > > > I would say, yes it should be in the main tree, as every "Up-to-date" > > unix now delivers it. Or least together with their NFS package ;-) > > Hmm, although Solaris 2.5 is almost out so I can't check it, both > Solaris 2.4 and SunOS 4.1 don't ship with pcnfsd. As a matter of fact, > I don't know of any commercial OS which delivers it. > > > Nate >-- End of excerpt from Nate Williams BSDI, SGI Irix 5.3 for example. Ulf. -- Ulf Zimmermann, NCD Software, 101 Rowland Way, Suite 300, Novato, CA 94945 phone: 415-899-7941, email: ulf@z-code.ncd.com, phone-home: 510-865-0204 ====================================== FreeBSD 2.1.0 is available now! -------------------------------------- FreeBSD: Turning PCs into Workstations ====================================== From owner-freebsd-current Tue Dec 19 09:47:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24690 for current-outgoing; Tue, 19 Dec 1995 09:47:13 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA24597 for ; Tue, 19 Dec 1995 09:45:28 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id SAA19778; Tue, 19 Dec 1995 18:43:06 +0100 Message-Id: <199512191743.SAA19778@gilberto.physik.rwth-aachen.de> Subject: Re: pcnfsd.. To: nate@rocky.sri.mt.net (Nate Williams) Date: Tue, 19 Dec 1995 18:43:06 +0100 (MET) Cc: jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199512191548.IAA26516@rocky.sri.MT.net> from "Nate Williams" at Dec 19, 95 08:48:22 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk > > > Is freely redistributable software, right? At least that's what the > > man page says, anyway.. I'm wondering if this isn't something that > > *should* move out of ports and into the main tree? > > How useful is it for the general user of FreeBSD? > > (I'd say a *very* small percentage of users actually have use for it) If you have Macs using NFS for file sharing or if you are using XFS32 or other Windoze NFC client software.(PC/TCP - ftp software, Inc.). > > > Nate > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Dec 19 09:49:22 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24883 for current-outgoing; Tue, 19 Dec 1995 09:49:22 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA24876 for ; Tue, 19 Dec 1995 09:49:18 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA26843; Tue, 19 Dec 1995 10:45:49 -0700 Date: Tue, 19 Dec 1995 10:45:49 -0700 From: Nate Williams Message-Id: <199512191745.KAA26843@rocky.sri.MT.net> To: Christoph Kukulies Cc: current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512191743.SAA19778@gilberto.physik.rwth-aachen.de> References: <199512191548.IAA26516@rocky.sri.MT.net> <199512191743.SAA19778@gilberto.physik.rwth-aachen.de> Sender: owner-current@FreeBSD.ORG Precedence: bulk Christoph Kukulies writes: [ PCNFSD ] > > How useful is it for the general user of FreeBSD? > > > > (I'd say a *very* small percentage of users actually have use for it) > > If you have Macs using NFS for file sharing or if you are using > XFS32 or other Windoze NFC client software.(PC/TCP - ftp software, Inc.). I didn't say it was useless. I said it wasn't useful for the generic user. And, with it so easy to get as a port I don't see why it should become part of the system. I suspect 'fvwm' is more useful to the generic user, but it's not part of the base sources. :) Nate From owner-freebsd-current Tue Dec 19 09:57:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA25301 for current-outgoing; Tue, 19 Dec 1995 09:57:05 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA25296 for ; Tue, 19 Dec 1995 09:57:01 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id RAA03912; Tue, 19 Dec 1995 17:55:04 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Tue, 19 Dec 1995 17:55:37 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id RAA09280; Tue, 19 Dec 1995 17:55:30 GMT From: Paul Richards Message-Id: <199512191755.RAA09280@cadair.elsevier.co.uk> Subject: Re: pcnfsd.. To: nate@rocky.sri.MT.net (Nate Williams) Date: Tue, 19 Dec 1995 17:55:29 +0000 (GMT) Cc: kuku@gilberto.physik.rwth-aachen.de, current@freefall.freebsd.org In-Reply-To: <199512191745.KAA26843@rocky.sri.MT.net> from "Nate Williams" at Dec 19, 95 10:45:49 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk In reply to Nate Williams who said > > I didn't say it was useless. I said it wasn't useful for the generic > user. And, with it so easy to get as a port I don't see why it should > become part of the system. I suspect 'fvwm' is more useful to the > generic user, but it's not part of the base sources. :) Or Samba :-) -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Tue Dec 19 10:25:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA26786 for current-outgoing; Tue, 19 Dec 1995 10:25:29 -0800 (PST) Received: from bacchus.eng.umd.edu (bacchus.eng.umd.edu [129.2.94.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA26781 for ; Tue, 19 Dec 1995 10:25:24 -0800 (PST) Received: from latte.eng.umd.edu (latte.eng.umd.edu [129.2.98.15]) by bacchus.eng.umd.edu (8.7.3/8.7) with ESMTP id NAA29391; Tue, 19 Dec 1995 13:25:08 -0500 (EST) Received: (chuckr@localhost) by latte.eng.umd.edu (8.7.3/8.6.4) id NAA08863; Tue, 19 Dec 1995 13:25:07 -0500 (EST) Date: Tue, 19 Dec 1995 13:25:07 -0500 (EST) From: Chuck Robey X-Sender: chuckr@latte.eng.umd.edu To: Ulf Zimmermann cc: Nate Williams , Ulf Zimmermann , "Jordan K. Hubbard" , current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <9512190842.ZM13685@zolaris.z-code.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Tue, 19 Dec 1995, Ulf Zimmermann wrote: > On Dec 19, 9:32, Nate Williams wrote: > > Subject: Re: pcnfsd.. > > [ PCNFSD in main FreeBSD source tree ] > > > > > I would say, yes it should be in the main tree, as every "Up-to-date" > > > unix now delivers it. Or least together with their NFS package ;-) > > > > Hmm, although Solaris 2.5 is almost out so I can't check it, both > > Solaris 2.4 and SunOS 4.1 don't ship with pcnfsd. As a matter of fact, > > I don't know of any commercial OS which delivers it. > > > > > > Nate > >-- End of excerpt from Nate Williams > > BSDI, SGI Irix 5.3 for example. And SVR4. > > Ulf. > > > -- > Ulf Zimmermann, NCD Software, 101 Rowland Way, Suite 300, Novato, CA 94945 > phone: 415-899-7941, email: ulf@z-code.ncd.com, phone-home: 510-865-0204 > ====================================== > FreeBSD 2.1.0 is available now! > -------------------------------------- > FreeBSD: Turning PCs into Workstations > ====================================== > > ============================================================================ Chuck Robey chuckr@eng.umd.edu -- I run FreeBSD on n3lxx and Journey2 --------------------------------------------------------------------------- The Dilbert Zone is Dilbert's new WWW home! The area features never-before-seen original sketches of Dilbert, a photo tour of Scott Adams' studio, Dilbert Trivia and memorabilia, high school photos and much more!: From owner-freebsd-current Tue Dec 19 10:25:37 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA26804 for current-outgoing; Tue, 19 Dec 1995 10:25:37 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA26799 for ; Tue, 19 Dec 1995 10:25:34 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA15358; Tue, 19 Dec 1995 13:25:21 -0500 Date: Tue, 19 Dec 1995 13:25:21 -0500 From: "Garrett A. Wollman" Message-Id: <9512191825.AA15358@halloran-eldar.lcs.mit.edu> To: Nate Williams Cc: current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512191745.KAA26843@rocky.sri.MT.net> References: <199512191548.IAA26516@rocky.sri.MT.net> <199512191743.SAA19778@gilberto.physik.rwth-aachen.de> <199512191745.KAA26843@rocky.sri.MT.net> Sender: owner-current@FreeBSD.ORG Precedence: bulk < said: > I didn't say it was useless. I said it wasn't useful for the generic > user. And, with it so easy to get as a port I don't see why it should > become part of the system. I suspect 'fvwm' is more useful to the > generic user, but it's not part of the base sources. :) `fvwm' and `pcnfsd' are equally useless to me, and probably to anybody who runs FreeBSD in a `service-providing' mode as opposed to a `workstation' mode. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Dec 19 10:31:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27037 for current-outgoing; Tue, 19 Dec 1995 10:31:41 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27030 for ; Tue, 19 Dec 1995 10:31:39 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA14949; Tue, 19 Dec 1995 11:28:28 -0700 From: Terry Lambert Message-Id: <199512191828.LAA14949@phaeton.artisoft.com> Subject: Re: Mis-feature in -current To: nate@rocky.sri.MT.net (Nate Williams) Date: Tue, 19 Dec 1995 11:28:28 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199512190506.WAA25662@rocky.sri.MT.net> from "Nate Williams" at Dec 18, 95 10:06:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > This one was a strange one, but I finally figured it out. I'm trying to > build kernels which contain all of the necessary 'debug' symbols in > them, so I'm not compiling the code with '-O'. > > However, I've noticed that if you don't compile the code with '-O', gcc > no longer optimizes out the calls to strlen. What this means is that > the kernel will no longer link if you compile any modules which uses > strlen(). Can you manually add back in the inlining/intrinsicing? This would be the easiest option. > I'd like to add back the strlen() routine to libkern. Basically, the > linker won't pull it in if the kernel is compiled with optimization > since it won't be needed, but it's available if any routines aren't > optimized. > > The reason I think this should be brought in is that the current > behavior of in-lining strlen() is extremely non-intuitive and very GCC > specific. At least if we add back the strlen() code we aren't depending > on gcc optimizing away the calls. > > Any disagreements before I add back strlen to libkern? Actually (not that it would seem to matter), I'm anti-string-manipulation in kernel code. The only places this is violated currently is in the path parsing code and the NFS argument code. How many times is strlen used, and could it maybe be recoded instead? 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-current Tue Dec 19 10:34:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27198 for current-outgoing; Tue, 19 Dec 1995 10:34:20 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27178 for ; Tue, 19 Dec 1995 10:34:10 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA27072; Tue, 19 Dec 1995 11:36:28 -0700 Date: Tue, 19 Dec 1995 11:36:28 -0700 From: Nate Williams Message-Id: <199512191836.LAA27072@rocky.sri.MT.net> To: Terry Lambert Cc: nate@rocky.sri.MT.net (Nate Williams), current@FreeBSD.org Subject: Re: Mis-feature in -current In-Reply-To: <199512191828.LAA14949@phaeton.artisoft.com> References: <199512190506.WAA25662@rocky.sri.MT.net> <199512191828.LAA14949@phaeton.artisoft.com> Sender: owner-current@FreeBSD.org Precedence: bulk Terry Lambert writes: > > This one was a strange one, but I finally figured it out. I'm trying to > > build kernels which contain all of the necessary 'debug' symbols in > > them, so I'm not compiling the code with '-O'. > > > > However, I've noticed that if you don't compile the code with '-O', gcc > > no longer optimizes out the calls to strlen. What this means is that > > the kernel will no longer link if you compile any modules which uses > > strlen(). > > Can you manually add back in the inlining/intrinsicing? This would be > the easiest option. Not w/out hacking the gcc sources, making our tree even more dependant on the compiler. > > Any disagreements before I add back strlen to libkern? > > Actually (not that it would seem to matter), I'm anti-string-manipulation > in kernel code. The only places this is violated currently is in the > path parsing code and the NFS argument code. We all know about that, but I'm talking about the code that exists in -current today, not in FreeBSD 10.1. > How many times is strlen used, and could it maybe be recoded instead? Why would it need to be recoded? As it stands currently (and this will not change for some time), the code in libkern/strlen.c is completely adequate to do the job. Nate From owner-freebsd-current Tue Dec 19 10:40:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27479 for current-outgoing; Tue, 19 Dec 1995 10:40:04 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27452 for ; Tue, 19 Dec 1995 10:40:01 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15039; Tue, 19 Dec 1995 11:36:44 -0700 From: Terry Lambert Message-Id: <199512191836.LAA15039@phaeton.artisoft.com> Subject: Re: Mis-feature in -current To: nate@rocky.sri.MT.net (Nate Williams) Date: Tue, 19 Dec 1995 11:36:44 -0700 (MST) Cc: terry@lambert.org, nate@rocky.sri.MT.net, current@FreeBSD.org In-Reply-To: <199512191836.LAA27072@rocky.sri.MT.net> from "Nate Williams" at Dec 19, 95 11:36:28 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-current@FreeBSD.org Precedence: bulk > > Actually (not that it would seem to matter), I'm anti-string-manipulation > > in kernel code. The only places this is violated currently is in the > > path parsing code and the NFS argument code. > > We all know about that, but I'm talking about the code that exists in > -current today, not in FreeBSD 10.1. > > > How many times is strlen used, and could it maybe be recoded instead? > > Why would it need to be recoded? As it stands currently (and this will > not change for some time), the code in libkern/strlen.c is completely > adequate to do the job. I meant recoded to not use strlen. wchar_t springs to mind as a likely reason. 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-current Tue Dec 19 10:42:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27627 for current-outgoing; Tue, 19 Dec 1995 10:42:48 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27622 for ; Tue, 19 Dec 1995 10:42:45 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA27145; Tue, 19 Dec 1995 11:45:01 -0700 Date: Tue, 19 Dec 1995 11:45:01 -0700 From: Nate Williams Message-Id: <199512191845.LAA27145@rocky.sri.MT.net> To: Terry Lambert Cc: nate@rocky.sri.MT.net (Nate Williams), current@FreeBSD.org Subject: Re: Mis-feature in -current In-Reply-To: <199512191836.LAA15039@phaeton.artisoft.com> References: <199512191836.LAA27072@rocky.sri.MT.net> <199512191836.LAA15039@phaeton.artisoft.com> Sender: owner-current@FreeBSD.org Precedence: bulk [ strlen used in -current ] > > > How many times is strlen used, and could it maybe be recoded instead? > > > > Why would it need to be recoded? As it stands currently (and this will > > not change for some time), the code in libkern/strlen.c is completely > > adequate to do the job. > > I meant recoded to not use strlen. > > wchar_t springs to mind as a likely reason. I'm just trying to fix -current, not re-code the kernel. If it ain't broke, don't fix it. If it is broke, fix the broken-ness and not introduce new brokeness because it sounds like a good idea. Nate From owner-freebsd-current Tue Dec 19 10:51:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27950 for current-outgoing; Tue, 19 Dec 1995 10:51:36 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27941 for ; Tue, 19 Dec 1995 10:51:22 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15110; Tue, 19 Dec 1995 11:47:47 -0700 From: Terry Lambert Message-Id: <199512191847.LAA15110@phaeton.artisoft.com> Subject: Re: Mis-feature in -current To: nate@rocky.sri.MT.net (Nate Williams) Date: Tue, 19 Dec 1995 11:47:47 -0700 (MST) Cc: terry@lambert.org, nate@rocky.sri.MT.net, current@FreeBSD.org In-Reply-To: <199512191845.LAA27145@rocky.sri.MT.net> from "Nate Williams" at Dec 19, 95 11:45:01 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-current@FreeBSD.org Precedence: bulk > > > > How many times is strlen used, and could it maybe be recoded instead? > > > > > > Why would it need to be recoded? As it stands currently (and this will > > > not change for some time), the code in libkern/strlen.c is completely > > > adequate to do the job. > > > > I meant recoded to not use strlen. > > > > wchar_t springs to mind as a likely reason. > > I'm just trying to fix -current, not re-code the kernel. If it ain't > broke, don't fix it. If it is broke, fix the broken-ness and not > introduce new brokeness because it sounds like a good idea. I just meant that if it was only one or two places. I went grepping: It's more than 60 places. So never mind. I agree with adding it back into the lib for now. 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-current Tue Dec 19 10:52:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA28115 for current-outgoing; Tue, 19 Dec 1995 10:52:24 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA28109 for ; Tue, 19 Dec 1995 10:52:21 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA27205; Tue, 19 Dec 1995 11:54:38 -0700 Date: Tue, 19 Dec 1995 11:54:38 -0700 From: Nate Williams Message-Id: <199512191854.LAA27205@rocky.sri.MT.net> To: Terry Lambert Cc: nate@rocky.sri.MT.net (Nate Williams), current@FreeBSD.org Subject: Re: Mis-feature in -current In-Reply-To: <199512191847.LAA15110@phaeton.artisoft.com> References: <199512191845.LAA27145@rocky.sri.MT.net> <199512191847.LAA15110@phaeton.artisoft.com> Sender: owner-current@FreeBSD.org Precedence: bulk Terry > How many times is strlen used, and could it maybe be recoded instead? Nate > I'm just trying to fix -current, not re-code the kernel. If it ain't Nate > broke, don't fix it. If it is broke, fix the broken-ness and not Nate > introduce new brokeness because it sounds like a good idea. > I just meant that if it was only one or two places. > > I went grepping: It's more than 60 places. So never mind. I agree with > adding it back into the lib for now. Not to mention all of the other string routines such as strcpy and the like. Nate From owner-freebsd-current Tue Dec 19 11:14:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA28803 for current-outgoing; Tue, 19 Dec 1995 11:14:53 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA28794 for ; Tue, 19 Dec 1995 11:14:25 -0800 (PST) Received: by sequent.kiae.su id AA20315 (5.65.kiae-2 ); Tue, 19 Dec 1995 22:00:52 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 19 Dec 95 22:00:51 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id VAA01363; Tue, 19 Dec 1995 21:37:28 +0300 (MSK) To: faried nawaz , "Marc G. Fournier" Cc: current@freebsd.org References: <199512191505.HAA08739@hoodoo.cs.uidaho.edu> In-Reply-To: <199512191505.HAA08739@hoodoo.cs.uidaho.edu>; from faried nawaz at Tue, 19 Dec 1995 07:05:02 PST Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 19 Dec 1995 21:37:28 +0300 (MSK) X-Mailer: Mail/@ [v2.41 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: panic: m_copydata Lines: 23 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message <199512191505.HAA08739@hoodoo.cs.uidaho.edu> faried nawaz writes: >"Marc G. Fournier" wrote... > Trace: > _Debugger(f0111fe0,f011d5e4,efbffe94,14) at _Debugger+0x2b > _panic(f011d5e3,14,ffffffff,f05f3880,efbfff20) at _panic+0x3b > _m_copydata(0,ffffffff,1,f05f38e8,0) at _m_copydata+0x21 > _tcp_output(f05a4f00,f061169c,f0611b80,14,efbfff30) at > _tcp_output+0x635 > _tcp_input(f0611680,14) at _tcp_input+0x13da > _ipintr(f0172117,0,efbf0027,27,3c) at _ipintr+0x429 > Bad User Frame pointer: 0xefbf9120 I saw (and report) the same picture too... :-( -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Tue Dec 19 11:20:10 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA29063 for current-outgoing; Tue, 19 Dec 1995 11:20:10 -0800 (PST) Received: from trane.uninett.no (trane.uninett.no [129.241.1.16]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA29058 for ; Tue, 19 Dec 1995 11:20:08 -0800 (PST) Received: (from sthaug@localhost) by trane.uninett.no id SAA16348 (8.6.12/IDA-1.6); Tue, 19 Dec 1995 18:51:57 +0100 Date: Tue, 19 Dec 1995 18:51:57 +0100 (MET) From: Steinar Haug To: Nate Williams cc: Ulf Zimmermann , "Jordan K. Hubbard" , current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512191632.JAA26625@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk > > I would say, yes it should be in the main tree, as every "Up-to-date" > > unix now delivers it. Or least together with their NFS package ;-) > > Hmm, although Solaris 2.5 is almost out so I can't check it, both > Solaris 2.4 and SunOS 4.1 don't ship with pcnfsd. As a matter of fact, > I don't know of any commercial OS which delivers it. Have you checked lately? As far as I know both HP-UX and Digital Unix ship with rpc.pcnfsd. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Tue Dec 19 11:36:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA29809 for current-outgoing; Tue, 19 Dec 1995 11:36:24 -0800 (PST) Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA29802 for ; Tue, 19 Dec 1995 11:36:16 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.7.3/8.6.9) with ESMTP id VAA01528 for ; Tue, 19 Dec 1995 21:36:03 +0200 (SAT) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.6.9) with SMTP id VAA12859 for ; Tue, 19 Dec 1995 21:36:02 +0200 (SAT) Message-Id: <199512191936.VAA12859@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: Museum pieces... Date: Tue, 19 Dec 1995 21:35:59 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk Hi All.. There are some museum pieces in src/etc/etc.i386: total 348 drwxr-xr-x 3 root wheel 512 Dec 4 08:38 . drwxr-xr-x 9 root wheel 1024 Dec 18 20:02 .. -rw-r--r-- 1 root wheel 28010 Dec 4 08:38 MAKEDEV -rw-r--r-- 1 root wheel 6474 Jun 28 1994 README.1ST -rw-r--r-- 1 root wheel 36633 Jun 28 1994 README.INSTALL -rw-r--r-- 1 root wheel 28838 Sep 15 1994 cdinst1.install -rw-r--r-- 1 root wheel 2199 Apr 18 1994 cdinst1.profile -rw-r--r-- 1 root wheel 374 Feb 21 1994 cpio.install -rw-r--r-- 1 root wheel 9142 Jun 29 1994 cpio.magic -rw-r--r-- 1 root wheel 3118 Sep 15 1994 cpio.rc -rw-r--r-- 1 root wheel 5645 Oct 2 23:31 disktab -rw-r--r-- 1 root wheel 80 Jun 20 1993 fstab.wd -rw-r--r-- 1 root wheel 30179 Oct 17 1994 inst1.install -rw-r--r-- 1 root wheel 166 Feb 21 1994 inst1.profile -rw-r--r-- 1 root wheel 10687 Sep 15 1994 inst2.rc -rw-r--r-- 1 root wheel 1751 Sep 15 1994 kc.profile -rw-r--r-- 1 root wheel 2351 Dec 2 17:22 rc.i386 Both README's, the cd*'s, the cpio.*'s, the inst*'s and the kc* are only of relevance to 1.1.5.1 and earlier. Can't we nuke 'em? Heck, I don't reckon they'll even work anymore. Also, this was discussed, bit I do not remember the outcome - There are some X games in the source tree that some of us figured should go to ports/ (gnuchess also). Can I go ahead? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Tue Dec 19 12:14:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA02294 for current-outgoing; Tue, 19 Dec 1995 12:14:02 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA02288 for ; Tue, 19 Dec 1995 12:13:58 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA27474; Tue, 19 Dec 1995 13:16:13 -0700 Date: Tue, 19 Dec 1995 13:16:13 -0700 From: Nate Williams Message-Id: <199512192016.NAA27474@rocky.sri.MT.net> To: Mark Murray Cc: current@freebsd.org Subject: Re: Museum pieces... In-Reply-To: <199512191936.VAA12859@grumble.grondar.za> References: <199512191936.VAA12859@grumble.grondar.za> Sender: owner-current@freebsd.org Precedence: bulk > There are some museum pieces in src/etc/etc.i386: ... > -rw-r--r-- 1 root wheel 28010 Dec 4 08:38 MAKEDEV > -rw-r--r-- 1 root wheel 5645 Oct 2 23:31 disktab > -rw-r--r-- 1 root wheel 2351 Dec 2 17:22 rc.i386 You *really* don't want to delete these three files. > Can't we nuke 'em? Heck, I don't reckon they'll even work anymore. I don't see why not. > Also, this was discussed, bit I do not remember the outcome - There are > some X games in the source tree that some of us figured should go to ports/ > (gnuchess also). Can I go ahead? Make sure the ports exists before they get nuked. Nate From owner-freebsd-current Tue Dec 19 12:18:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA02673 for current-outgoing; Tue, 19 Dec 1995 12:18:33 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA02667 for ; Tue, 19 Dec 1995 12:18:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id MAA02161; Tue, 19 Dec 1995 12:17:53 -0800 To: Mark Murray cc: current@freebsd.org Subject: Re: Museum pieces... In-reply-to: Your message of "Tue, 19 Dec 1995 21:35:59 +0200." <199512191936.VAA12859@grumble.grondar.za> Date: Tue, 19 Dec 1995 12:17:53 -0800 Message-ID: <2152.819404273@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk These ancient fossils definitely should go. Removal of xroach and xneko to ports? Fine by me! Jordan > Hi All.. > > There are some museum pieces in src/etc/etc.i386: > > total 348 > drwxr-xr-x 3 root wheel 512 Dec 4 08:38 . > drwxr-xr-x 9 root wheel 1024 Dec 18 20:02 .. > -rw-r--r-- 1 root wheel 28010 Dec 4 08:38 MAKEDEV > -rw-r--r-- 1 root wheel 6474 Jun 28 1994 README.1ST > -rw-r--r-- 1 root wheel 36633 Jun 28 1994 README.INSTALL > -rw-r--r-- 1 root wheel 28838 Sep 15 1994 cdinst1.install > -rw-r--r-- 1 root wheel 2199 Apr 18 1994 cdinst1.profile > -rw-r--r-- 1 root wheel 374 Feb 21 1994 cpio.install > -rw-r--r-- 1 root wheel 9142 Jun 29 1994 cpio.magic > -rw-r--r-- 1 root wheel 3118 Sep 15 1994 cpio.rc > -rw-r--r-- 1 root wheel 5645 Oct 2 23:31 disktab > -rw-r--r-- 1 root wheel 80 Jun 20 1993 fstab.wd > -rw-r--r-- 1 root wheel 30179 Oct 17 1994 inst1.install > -rw-r--r-- 1 root wheel 166 Feb 21 1994 inst1.profile > -rw-r--r-- 1 root wheel 10687 Sep 15 1994 inst2.rc > -rw-r--r-- 1 root wheel 1751 Sep 15 1994 kc.profile > -rw-r--r-- 1 root wheel 2351 Dec 2 17:22 rc.i386 > > Both README's, the cd*'s, the cpio.*'s, the inst*'s and the kc* are only of > relevance to 1.1.5.1 and earlier. Can't we nuke 'em? Heck, I don't reckon > they'll even work anymore. > > Also, this was discussed, bit I do not remember the outcome - There are > some X games in the source tree that some of us figured should go to ports/ > (gnuchess also). Can I go ahead? > > M > > -- > Mark Murray > 46 Harvey Rd, Claremont, Cape Town 7700, South Africa > +27 21 61-3768 GMT+0200 > Finger mark@grondar.za for PGP key From owner-freebsd-current Tue Dec 19 12:19:47 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA02721 for current-outgoing; Tue, 19 Dec 1995 12:19:47 -0800 (PST) Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA02715 for ; Tue, 19 Dec 1995 12:19:40 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.7.3/8.6.9) with ESMTP id WAA01570; Tue, 19 Dec 1995 22:19:29 +0200 (SAT) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.6.9) with SMTP id WAA14570; Tue, 19 Dec 1995 22:19:28 +0200 (SAT) Message-Id: <199512192019.WAA14570@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: Nate Williams cc: current@freebsd.org Subject: Re: Museum pieces... Date: Tue, 19 Dec 1995 22:19:22 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk Nate Williams wrote: > > There are some museum pieces in src/etc/etc.i386: > > ... > > -rw-r--r-- 1 root wheel 28010 Dec 4 08:38 MAKEDEV > > -rw-r--r-- 1 root wheel 5645 Oct 2 23:31 disktab > > -rw-r--r-- 1 root wheel 2351 Dec 2 17:22 rc.i386 > > You *really* don't want to delete these three files. Of course not! I just forgot to say so :) > > Can't we nuke 'em? Heck, I don't reckon they'll even work anymore. > > I don't see why not. Cool! > > Also, this was discussed, bit I do not remember the outcome - There are > > some X games in the source tree that some of us figured should go to ports/ > > (gnuchess also). Can I go ahead? > > Make sure the ports exists before they get nuked. Sure. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Tue Dec 19 12:43:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA04922 for current-outgoing; Tue, 19 Dec 1995 12:43:05 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA04867 for ; Tue, 19 Dec 1995 12:41:44 -0800 (PST) Received: from mordillo (oberon.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id VAA18864; Tue, 19 Dec 1995 21:39:45 +0100 (MET) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id SAA02380; Tue, 19 Dec 1995 18:11:19 +0100 From: Thomas Graichen Message-Id: <199512191711.SAA02380@mordillo> Subject: Re: pcnfsd.. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 19 Dec 1995 18:11:18 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <199512191246.EAA17333@time.cdrom.com> from "Jordan K. Hubbard" at Dec 19, 95 04:46:00 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > > Is freely redistributable software, right? At least that's what the > man page says, anyway.. I'm wondering if this isn't something that > *should* move out of ports and into the main tree? It currently represents > something of an imperfect match, at best, as simply reading the man page > or doing the two-step configuration process for it will readily attest. > > Jordan ... did you set up a NetBSD machine ? :-) (first the ypset man-page from NetBSD and now pcnfsd which is also part of NetBSD ...) t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-current Tue Dec 19 13:00:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA06172 for current-outgoing; Tue, 19 Dec 1995 13:00:20 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA06072 for ; Tue, 19 Dec 1995 13:00:07 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id VAA20567 for freebsd-current@freefall.cdrom.com; Tue, 19 Dec 1995 21:56:42 +0100 Date: Tue, 19 Dec 1995 21:56:42 +0100 From: "Christoph P. Kukulies" Message-Id: <199512192056.VAA20567@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: more on 'lost console' Sender: owner-current@FreeBSD.ORG Precedence: bulk I reported that sort of lost console under PCVT. Fact is, I can't use PCVT-vt-switching at all under that version of a three weeks old -current. It appears though that some ALT-F (9 or 10) give me a HP TERM but still with the same process. So it's just the terminal characteristics that changes, not the process. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Dec 19 13:19:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA07072 for current-outgoing; Tue, 19 Dec 1995 13:19:45 -0800 (PST) Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA07065 for ; Tue, 19 Dec 1995 13:19:40 -0800 (PST) Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.6.12/8.6.9) with ESMTP id NAA00272 for ; Tue, 19 Dec 1995 13:19:39 -0800 Message-Id: <199512192119.NAA00272@pain.csrv.uidaho.edu> To: current@freebsd.org Subject: the crashes. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <264.819407972.1@pain.csrv.uidaho.edu> Date: Tue, 19 Dec 1995 13:19:32 -0800 From: Faried Nawaz Sender: owner-current@freebsd.org Precedence: bulk hi, i've had _5_ crashes today. what fun. i'm running a kernel built from yesterday's (dec 18th) sources. i can put the kernel.debug and vmcore/kernel files up for ftp. is there _anything_ at all that i can do to help fix this problem? it's at the stage where i'm ready to give up and go to 2.1. i'm machine "i386" cpu "I486_CPU" ident pain maxusers 12 options GPL_MATH_EMULATE #Math coprocessor emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options "COMPAT_43" #Compatible with BSD 4.3 options KTRACE #kernel tracing options IPACCT #ip accounting options IPFIREWALL options IPFIREWALL_VERBOSE #talkative firewall options "PCVT_FREEBSD=210" #pcvt for os=-current options FAT_CURSOR #fat cursor. options PCVT_PRETTYSCRNS #pretty screensaver options PCVT_META_ESC #alt = meta options PCVT_INHIBIT_NUMLOCK #i hate numlock options JREMOD config kernel root on wd0 controller isa0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 # uncomment one of the following. #device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed1 at isa? port 0x300 net irq 15 iomem 0xd8000 vector edintr device pca0 at isa? port "IO_TIMER1" tty pseudo-device loop pseudo-device ether pseudo-device log pseudo-device pty 16 pseudo-device bpfilter 2 pseudo-device tun 1 pseudo-device speaker pseudo-device vn 2 and FreeBSD 2.2-CURRENT #1: Tue Dec 19 12:05:25 PST 1995 fn@pain.csrv.uidaho.edu:/disk1/src/sys/compile/pain CPU: i486DX (486-class CPU) real memory = 16777216 (16384K bytes) avail memory = 15192064 (14836K bytes) Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: tvga 8900c, 80/132 col, color, 8 scr, mf2-kbd, [R3.20-b24] ed1 at 0x300-0x31f irq 15 on isa ed1: address 00:40:33:2d:78:48, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16450 lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface pca0 on motherboard pca0: PC speaker audio driver wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 431MB (883624 sectors), 1018 cyls, 14 heads, 62 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 520MB (1065456 sectors), 1057 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: 387 emulator WARNING: / was not properly dismounted. in_rtqtimo: adjusted rtq_reallyold to 2400 here's some output of two of the crashes: Script started on Tue Dec 19 13:08:00 1995 ; gdb -q -k (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.15 (kgdb) core-file /var/crash/vmcore.15 IdlePTD 1a2000 current pcb at 1937fc panic: m_copydata #0 boot (howto=260) at ../../i386/i386/machdep.c:913 913 dumppcb.pcb_ptd = rcr3(); (kgdb) where #0 boot (howto=260) at ../../i386/i386/machdep.c:913 #1 0xf010fbc3 in panic (fmt=0xf015f3ec "page fault") at ../../kern/subr_prf.c:124 #2 0xf015ff0a in trap_fatal (frame=0xf0187cb0) at ../../i386/i386/trap.c:753 #3 0xf015fa7c in trap_pfault (frame=0xf0187cb0, usermode=0) at ../../i386/i386/trap.c:675 #4 0xf015f71b in trap (frame={tf_es = 16, tf_ds = -261357552, tf_edi = -1073610752, tf_esi = 17, tf_ebp = -266830596, tf_isp = -267340107, tf_ebx = 0, tf_edx = 983440, tf_ecx = 0, tf_eax = 17, tf_trapno = 12, tf_err = -266797056, tf_eip = -267340107, tf_cs = -261357560, tf_eflags = 66118, tf_esp = -247749636, tf_ss = -261302144}) at ../../i386/i386/trap.c:316 #5 0xf0158b3d in calltrap () #6 0xf010b6b5 in tsleep (ident=0xf13ba3fc, priority=17, wmesg=0xf011f13f "getblk", timo=0) at ../../kern/kern_synch.c:298 #7 0xf011f1cd in getblk (vp=0xf06cd880, blkno=983440, size=8192, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:901 #8 0xf011e0f5 in bread (vp=0xf06cd880, blkno=983440, size=8192, cred=0xffffffff, bpp=0xf0187d98) at ../../kern/vfs_bio.c:187 #9 0xf0141145 in ffs_update (ap=0xf0187dc4) at ../../ufs/ffs/ffs_inode.c:135 #10 0xf0144674 in ffs_fsync (ap=0xf0187e08) at ./vnode_if.h:1031 #11 0xf01432c4 in ffs_sync (mp=0xf06d4800, waitfor=2, cred=0xf0501b80, p=0xf019fb94) at ./vnode_if.h:407 ---Type to continue, or q to quit--- #12 0xf012498a in sync (p=0xf019fb94, uap=0x0, retval=0x0) at ../../kern/vfs_syscalls.c:347 #13 0xf015b175 in boot (howto=256) at ../../i386/i386/machdep.c:862 #14 0xf010fbc3 in panic (fmt=0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 #15 0xf0118751 in m_copydata (m=0x0, off=-1, len=1, cp=0xf0858a68 "") at ../../kern/uipc_mbuf.c:371 #16 0xf013b9b5 in tcp_output (tp=0xf06cb000) at ../../netinet/tcp_output.c:476 #17 0xf013ac4a in tcp_input (m=0xf085ad00, iphlen=20) at ../../netinet/tcp_input.c:1629 #18 0xf0135b69 in ipintr () at ../../netinet/ip_input.c:464 #19 0xf0159ffd in swi_net_next () #20 0xf015f0d8 in cpu_switch () (kgdb) up #1 0xf010fbc3 in panic (fmt=0xf015f3ec "page fault") at ../../kern/subr_prf.c:124 124 boot(bootopt); (kgdb) up #2 0xf015ff0a in trap_fatal (frame=0xf0187cb0) at ../../i386/i386/trap.c:753 753 panic(trap_msg[type]); (kgdb) up #3 0xf015fa7c in trap_pfault (frame=0xf0187cb0, usermode=0) at ../../i386/i386/trap.c:675 675 trap_fatal(frame); (kgdb) up #4 0xf015f71b in trap (frame={tf_es = 16, tf_ds = -261357552, tf_edi = -1073610752, tf_esi = 17, tf_ebp = -266830596, tf_isp = -267340107, tf_ebx = 0, tf_edx = 983440, tf_ecx = 0, tf_eax = 17, tf_trapno = 12, tf_err = -266797056, tf_eip = -267340107, tf_cs = -261357560, tf_eflags = 66118, tf_esp = -247749636, tf_ss = -261302144}) at ../../i386/i386/trap.c:316 316 (void) trap_pfault(&frame, FALSE); (kgdb) up #5 0xf0158b3d in calltrap () (kgdb) up #6 0xf010b6b5 in tsleep (ident=0xf13ba3fc, priority=17, wmesg=0xf011f13f "getblk", timo=0) at ../../kern/kern_synch.c:298 298 int sig, catch = priority & PCATCH; (kgdb) up #7 0xf011f1cd in getblk (vp=0xf06cd880, blkno=983440, size=8192, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:901 901 if (!tsleep(bp, (kgdb) up #8 0xf011e0f5 in bread (vp=0xf06cd880, blkno=983440, size=8192, cred=0xffffffff, bpp=0xf0187d98) at ../../kern/vfs_bio.c:187 187 bp = getblk(vp, blkno, size, 0, 0); (kgdb) up #9 0xf0141145 in ffs_update (ap=0xf0187dc4) at ../../ufs/ffs/ffs_inode.c:135 135 error = bread(ip->i_devvp, fsbtodb(fs, ino_to_fsba(fs, ip->i_number)), (kgdb) up #10 0xf0144674 in ffs_fsync (ap=0xf0187e08) at ./vnode_if.h:1031 Source file is more recent than executable. 1031 return (VCALL(vp, VOFFSET(vop_update), &a)); (kgdb) up #11 0xf01432c4 in ffs_sync (mp=0xf06d4800, waitfor=2, cred=0xf0501b80, p=0xf019fb94) at ./vnode_if.h:407 Source file is more recent than executable. 407 return (VCALL(vp, VOFFSET(vop_fsync), &a)); (kgdb) up #12 0xf012498a in sync (p=0xf019fb94, uap=0x0, retval=0x0) at ../../kern/vfs_syscalls.c:347 347 VFS_SYNC(mp, MNT_NOWAIT, p != NULL ? p->p_ucred : NOCRED, p); (kgdb) up #13 0xf015b175 in boot (howto=256) at ../../i386/i386/machdep.c:862 862 sync(&proc0, NULL, NULL); (kgdb) up #14 0xf010fbc3 in panic (fmt=0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 124 boot(bootopt); (kgdb) up #15 0xf0118751 in m_copydata (m=0x0, off=-1, len=1, cp=0xf0858a68 "") at ../../kern/uipc_mbuf.c:371 371 panic("m_copydata"); (kgdb) up #16 0xf013b9b5 in tcp_output (tp=0xf06cb000) at ../../netinet/tcp_output.c:476 476 m_copydata(so->so_snd.sb_mb, off, (int) len, (kgdb) up #17 0xf013ac4a in tcp_input (m=0xf085ad00, iphlen=20) at ../../netinet/tcp_input.c:1629 1629 (void) tcp_output(tp); (kgdb) up #18 0xf0135b69 in ipintr () at ../../netinet/ip_input.c:464 464 (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); (kgdb) up #19 0xf0159ffd in swi_net_next () (kgdb) quit ; gdb -q -k (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.19 (kgdb) core-file /var/crash/vmcore.19 IdlePTD 1a2000 current pcb at 1937fc panic: m_copydata #0 boot (howto=256) at ../../i386/i386/machdep.c:913 913 dumppcb.pcb_ptd = rcr3(); (kgdb) where #0 boot (howto=256) at ../../i386/i386/machdep.c:913 #1 0xf010fbc3 in panic (fmt=0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 #2 0xf0118751 in m_copydata (m=0x0, off=-1, len=1, cp=0xf0790868 "") at ../../kern/uipc_mbuf.c:371 #3 0xf013b9b5 in tcp_output (tp=0xf07c3f00) at ../../netinet/tcp_output.c:476 #4 0xf013ac4a in tcp_input (m=0xf079d600, iphlen=20) at ../../netinet/tcp_input.c:1629 #5 0xf0135b69 in ipintr () at ../../netinet/ip_input.c:464 #6 0xf0159ffd in swi_net_next () #7 0xf015f0d8 in cpu_switch () (kgdb) up #1 0xf010fbc3 in panic (fmt=0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 124 boot(bootopt); (kgdb) up #2 0xf0118751 in m_copydata (m=0x0, off=-1, len=1, cp=0xf0790868 "") at ../../kern/uipc_mbuf.c:371 371 panic("m_copydata"); (kgdb) up #3 0xf013b9b5 in tcp_output (tp=0xf07c3f00) at ../../netinet/tcp_output.c:476 476 m_copydata(so->so_snd.sb_mb, off, (int) len, (kgdb) up #4 0xf013ac4a in tcp_input (m=0xf079d600, iphlen=20) at ../../netinet/tcp_input.c:1629 1629 (void) tcp_output(tp); (kgdb) print tp $1 = (struct tcpcb *) 0xf07c3f00 (kgdb) up #5 0xf0135b69 in ipintr () at ../../netinet/ip_input.c:464 464 (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); (kgdb) up #6 0xf0159ffd in swi_net_next () (kgdb) quit ; exit Script done on Tue Dec 19 13:11:04 1995 faried, going out to a late lunch. From owner-freebsd-current Tue Dec 19 13:26:39 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA07493 for current-outgoing; Tue, 19 Dec 1995 13:26:39 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA07485 for ; Tue, 19 Dec 1995 13:26:32 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA17015; Tue, 19 Dec 1995 16:26:29 -0500 Date: Tue, 19 Dec 1995 16:26:29 -0500 From: "Garrett A. Wollman" Message-Id: <9512192126.AA17015@halloran-eldar.lcs.mit.edu> To: FreeBSD-Current Mailing List Subject: Does anybody use DIRECTED_BROADCAST? Sender: owner-current@FreeBSD.ORG Precedence: bulk I am strongly inclined to dike out DIRECTED_BROADCAST, since it is completely bogus in nature. If there is anybody who (intentionally) uses it, please let me know within 24 hours. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Dec 19 13:29:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA07648 for current-outgoing; Tue, 19 Dec 1995 13:29:11 -0800 (PST) Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA07630 for ; Tue, 19 Dec 1995 13:29:01 -0800 (PST) Received: (from scrappy@localhost) by hub.org (8.7.3/8.7.3) id QAA02445; Tue, 19 Dec 1995 16:27:32 -0500 (EST) Date: Tue, 19 Dec 1995 16:27:23 -0500 (EST) From: "Marc G. Fournier" To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= cc: faried nawaz , current@freebsd.org Subject: Re: panic: m_copydata In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Tue, 19 Dec 1995, =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > In message <199512191505.HAA08739@hoodoo.cs.uidaho.edu> faried nawaz > writes: > > >"Marc G. Fournier" wrote... > > > Trace: > > > _Debugger(f0111fe0,f011d5e4,efbffe94,14) at _Debugger+0x2b > > _panic(f011d5e3,14,ffffffff,f05f3880,efbfff20) at _panic+0x3b > > _m_copydata(0,ffffffff,1,f05f38e8,0) at _m_copydata+0x21 > > _tcp_output(f05a4f00,f061169c,f0611b80,14,efbfff30) at > > _tcp_output+0x635 > > _tcp_input(f0611680,14) at _tcp_input+0x13da > > _ipintr(f0172117,0,efbf0027,27,3c) at _ipintr+0x429 > > Bad User Frame pointer: 0xefbf9120 > > I saw (and report) the same picture too... :-( > Okay...I got a response to this for more information, and what was asked for was: " Could you type `panic' in DDB next time you get this error to create a dump, and then print the contents of the `*tp' structure in the tcp_output() routine, and the contents of `*ti' in one frame up, in tcp_input(). " Now, to get my above trace, you have to have DDB enabled in the kernel, which will drop you to a "debug prompt" instead of rebooting the machine (neat feature if you happen to be around...just don't go away for the weekend *grin*) Just type 'tra' when it gets to that prompt, and it will give you exactly as above. To get the dump, you have to enable 'options DODUMP' in the kernel, and use 'config -g '. I'm assuming that to enable DDB, DODUMP has to be enabled first off, as I think they depend on each other. Then, in /etc/sysconfig, enable the following: # Set to the name of the device for kernel crashdumps, or `off' to # disable any statically configured dumpdev, or NO for no change. # The device should normally be one of the swap devices specified # in /etc/fstab. dumpdev=/dev/sd0b # Set to YES if you want kernel crashdumps to be saved for debugging savecore=YES And then, at the DDB prompt, type panic. Urm...make sure you have both a /var/crash directory, *and* there is enough disk space to write the core file to it (~= RAM size) Now...what to do with that core file? Check out Chapter 15 of the Handbook (found in /usr/share/doc/handbook...or, if you don't have it, I have it up at http://hub.org, as a link from the main page) That should be about all the information that I just received on how to help debug this problem...my *-current machine is down right now, and won't be up for a couple of days, so hopefully this helps track down the problem sooner... :) Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-current Tue Dec 19 14:50:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12290 for current-outgoing; Tue, 19 Dec 1995 14:50:28 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA12284 for ; Tue, 19 Dec 1995 14:50:15 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id JAA10809; Wed, 20 Dec 1995 09:22:00 +1030 From: Michael Smith Message-Id: <199512192252.JAA10809@genesis.atrad.adelaide.edu.au> Subject: Re: pcnfsd.. To: nate@rocky.sri.MT.net (Nate Williams) Date: Wed, 20 Dec 1995 09:21:59 +1030 (CST) Cc: jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199512191548.IAA26516@rocky.sri.MT.net> from "Nate Williams" at Dec 19, 95 08:48:22 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk Nate Williams stands accused of saying: > > > Is freely redistributable software, right? At least that's what the > > man page says, anyway.. I'm wondering if this isn't something that > > *should* move out of ports and into the main tree? > > How useful is it for the general user of FreeBSD? > > (I'd say a *very* small percentage of users actually have use for it) If it moves, so does samba and that DHCP daemon that I keep hearing about 8) I'd say that they get an awful lot more use than pcnfsd. (Or would if people knew about them 8) > Nate -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 041-122-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[ From owner-freebsd-current Tue Dec 19 16:36:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA18990 for current-outgoing; Tue, 19 Dec 1995 16:36:53 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (Aspen.Woc.Atinc.COM [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA18985 for ; Tue, 19 Dec 1995 16:36:46 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id TAA11990; Tue, 19 Dec 1995 19:36:07 -0500 Date: Tue, 19 Dec 1995 19:36:05 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: "Frank E. Terhaar-Yonkers" cc: p.richards@elsevier.co.uk, FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: <199512191414.JAA27171@robin.mcnc.org.mcnc.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Tue, 19 Dec 1995, Frank E. Terhaar-Yonkers wrote: > This is bogus. The phone lines to my house are so crappy that I regularly > have to kill ijppp and restart it. I don't want to have to kill all the X > stuff as well, before I restart PPP. Running ijppp and X has been a > crap shoot. About 1/4 the time, killing ppp locks up the system. > > What's the problem and why can't we fix it? do you have "delete ALL" in your /etc/ppp/ppp.{linkup,conf} this seems to be an X killer. every night i start ppp with "ppp -auto foobar". before sleep i kill ppp with kill -9. X and my machine have been up for 10 days. X never gets hammered. the man page stinks to high heaven. someone needs to read the code and write a new manpage detailing all the gotchas. a blank line in /etc/ppp/ppp.conf serves as a null label jmb > Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-current Tue Dec 19 16:44:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA19267 for current-outgoing; Tue, 19 Dec 1995 16:44:56 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (Aspen.Woc.Atinc.COM [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA19258 for ; Tue, 19 Dec 1995 16:44:52 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id TAA12005; Tue, 19 Dec 1995 19:44:33 -0500 Date: Tue, 19 Dec 1995 19:44:31 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: "Jordan K. Hubbard" cc: "Frank E. Terhaar-Yonkers" , p.richards@elsevier.co.uk, FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: <18129.819384793@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Tue, 19 Dec 1995, Jordan K. Hubbard wrote: > Maybe what has to happen first is you need to figure out a way of > causing ppp to kill your system *without* running X, e.g. so that > we can get into ddb and see what's panicing! > it aint ppp. it may well be the configuration that the user has spec'ed to ppp, but it aint ppp. excuse me for being so bloody insistent. it took a while to get ppp set up correctly. being the kook that i am, i keep hammering on it till i got the setup right (for me at least). now everyone at my previous employer uses my config files for ppp, works like a charm. BUT you gotta beware of "delete ALL" and setup up your routes first, during boot, as in: ifconfig tun0 inet 198.138.38.205 198.138.38.21 netmask 255.255.255.0 route add default 198.138.38.205 then in /etc/rc.local get ppp going and active /usr/sbin/ppp -auto atinc /sbin/ping -c 10 198.138.38.21 ONLY THEN do you start X. i use xdm ;) Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-current Tue Dec 19 16:45:08 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA19304 for current-outgoing; Tue, 19 Dec 1995 16:45:08 -0800 (PST) Received: from dworshak.cs.uidaho.edu (root@dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA19297 for ; Tue, 19 Dec 1995 16:45:05 -0800 (PST) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.6.12/1.1) with ESMTP id QAA25387; Tue, 19 Dec 1995 16:45:03 -0800 Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.6.10/1.0) with SMTP id QAA28519; Tue, 19 Dec 1995 16:45:44 -0800 Message-Id: <199512200045.QAA28519@waldrog.cs.uidaho.edu> X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost didn't use HELO protocol To: "Marc G. Fournier" cc: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= , current@freebsd.org Subject: Re: panic: m_copydata In-reply-to: Your message of "Tue, 19 Dec 1995 16:27:23 PST." Date: Tue, 19 Dec 1995 16:45:43 PST From: faried nawaz Sender: owner-current@freebsd.org Precedence: bulk "Marc G. Fournier" wrote... Okay...I got a response to this for more information, and what was asked for was: " Could you type `panic' in DDB next time you get this error to create a dump, and then print the contents of the `*tp' structure in the tcp_output () routine, and the contents of `*ti' in one frame up, in tcp_input(). " from the last core dump i had, ; gdb -k -q (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.19 (kgdb) core-file /var/crash/vmcore.19 IdlePTD 1a2000 current pcb at 1937fc panic: m_copydata ##0 boot (howto=256) at ../../i386/i386/machdep.c:913 913 dumppcb.pcb_ptd = rcr3(); (kgdb) where ##0 boot (howto=256) at ../../i386/i386/machdep.c:913 ##1 0xf010fbc3 in panic (fmt=0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 ##2 0xf0118751 in m_copydata (m=0x0, off=-1, len=1, cp=0xf0790868 "") at ../../kern/uipc_mbuf.c:371 ##3 0xf013b9b5 in tcp_output (tp=0xf07c3f00) at ../../netinet/tcp_output.c:476 ##4 0xf013ac4a in tcp_input (m=0xf079d600, iphlen=20) at ../../netinet/tcp_input.c:1629 ##5 0xf0135b69 in ipintr () at ../../netinet/ip_input.c:464 ##6 0xf0159ffd in swi_net_next () ##7 0xf015f0d8 in cpu_switch () (kgdb) up ##1 0xf010fbc3 in panic (fmt=0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 u124 boot(bootopt); (kgdb) up ##2 0xf0118751 in m_copydata (m=0x0, off=-1, len=1, cp=0xf0790868 "") at ../../kern/uipc_mbuf.c:371 371 panic("m_copydata"); (kgdb) up ##3 0xf013b9b5 in tcp_output (tp=0xf07c3f00) at ../../netinet/tcp_output.c:476 476 m_copydata(so->so_snd.sb_mb, off, (int) len, (kgdb) print tp $1 = (struct tcpcb *) 0xf07c3f00 (kgdb) print *tp $2 = {seg_next = 0xf079d62c, seg_prev = 0xf079d62c, t_state = 4, t_timer = {0, 0, 14400, 0}, t_rxtshift = 0, t_rxtcur = 128, t_dupacks = 0, t_maxseg = 492, t_maxopd = 512, t_force = 0, t_flags = 25057, t_template = 0xf07a1794, t_inpcb = 0xf079d500, snd_una = 376136494, snd_nxt = 376136493, snd_up = 376136493, snd_wl1 = 2939487243, snd_wl2 = 376136494, iss = 376136493, snd_wnd = 16728, rcv_wnd = 16728, rcv_nxt = 2939487234, rcv_up = 2939487234, irs = 2939487233, rcv_adv = 2939503962, snd_max = 376136494, snd_cwnd = 492, snd_ssthresh = 984, t_idle = 0, t_rtt = 0, t_rtseq = 376136493, t_srtt = 488, t_rttvar = 122, t_rttmin = 2, max_sndwnd = 16728, t_oobflags = 0 '\000', t_iobc = 0 '\000', t_softerror = 0, snd_scale = 0 '\000', rcv_scale = 0 '\000', request_r_scale = 0 '\000', requested_s_scale = 0 '\000', ts_recent = 2228926, ts_recent_age = 3908, last_ack_sent = 2939487234, cc_send = 56, cc_recv = 31598, t_duration = 58, t_tuba_pcb = 0x0, t_rttupdated = 1} (kgdb) print t_inpcb No symbol "t_inpcb" in current context. (kgdb) print tp->t_inpcb $3 = (struct inpcb *) 0xf079d500 (kgdb) print *tp->t_inpcb $4 = {inp_list = {le_next = 0xf0784d00, le_prev = 0xf01a04dc}, inp_hash = { le_next = 0x0, le_prev = 0xf06a5e60}, inp_pcbinfo = 0xf01a0338, inp_faddr = {s_addr = 1912703949}, inp_fport = 38150, inp_laddr = { s_addr = 1836213633}, inp_lport = 28928, inp_socket = 0xf082c100, inp_ppcb = 0xf07c3f00 ",Öyð,Öyð\004", inp_route = {ro_rt = 0xf082c900, ro_dst = {sa_len = 16 '\020', sa_family = 2 '\002', sa_data = "\000\000Í\213\001r\000\000\000\000\000\000\000"}}, inp_flags = 0, inp_ip = {ip_hl = 0 '\000', ip_v = 0 '\000', ip_tos = 0 '\000', ip_len = 0, ip_id = 0, ip_off = 0, ip_ttl = 64 '@', ip_p = 0 '\000', ip_sum = 0, ip_src = {s_addr = 0}, ip_dst = { (kgdb) print *tp->t_template $5 = {ti_i = {ih_next = 0x0, ih_prev = 0x0, ih_x1 = 0 '\000', ih_pr = 6 '\006', ih_len = 5120, ih_src = {s_addr = 1836213633}, ih_dst = { s_addr = 1912703949}}, ti_t = {th_sport = 28928, th_dport = 38150, th_seq = 0, th_ack = 0, th_x2 = 0 '\000', th_off = 5 '\005', th_flags = 0 '\000', th_win = 0, th_sum = 0, th_urp = 0}} (kgdb) up ##4 0xf013ac4a in tcp_input (m=0xf079d600, iphlen=20) at ../../netinet/tcp_input.c:1629 1629 (void) tcp_output(tp); (kgdb) print ti $6 = (struct tcpiphdr *) 0xf079d62c (kgdb) print *ti $7 = {ti_i = {ih_next = 0xf07c3f00 ",Öyð,Öyð\004", ih_prev = 0xf07c3f00 ",Öyð,Öyð\004", ih_x1 = 0 '\000', ih_pr = 6 '\006', ih_len = 0, ih_src = {s_addr = 1912703949}, ih_dst = { s_addr = 1836213633}}, ti_t = {th_sport = 54784, th_dport = 61561, th_seq = 2939487243, th_ack = 376136494, th_x2 = 0 '\000', th_off = 10 '\n', th_flags = 17 '\021', th_win = 16728, th_sum = 0, th_urp = 0}} (kgdb) faried From owner-freebsd-current Tue Dec 19 17:14:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA20308 for current-outgoing; Tue, 19 Dec 1995 17:14:35 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA20254 Tue, 19 Dec 1995 17:12:07 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA05296; Wed, 20 Dec 1995 12:06:54 +1100 Date: Wed, 20 Dec 1995 12:06:54 +1100 From: Bruce Evans Message-Id: <199512200106.MAA05296@godzilla.zeta.org.au> To: fty@mcnc.org, jkh@time.cdrom.com Subject: Re: ppp Cc: FreeBSD-current@freebsd.org, jmb@freebsd.org, p.richards@elsevier.co.uk Sender: owner-current@freebsd.org Precedence: bulk >Maybe what has to happen first is you need to figure out a way of >causing ppp to kill your system *without* running X, e.g. so that >we can get into ddb and see what's panicing! Just use a serial console. Bruce From owner-freebsd-current Tue Dec 19 18:57:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA24529 for current-outgoing; Tue, 19 Dec 1995 18:57:46 -0800 (PST) Received: from oasis.txdirect.net (oasis.txdirect.net [204.57.120.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA24523 Tue, 19 Dec 1995 18:57:40 -0800 (PST) Received: (from rsnow@localhost) by oasis.txdirect.net (8.6.12/8.6.9) id UAA00376; Tue, 19 Dec 1995 20:56:46 -0600 Date: Tue, 19 Dec 1995 20:56:46 -0600 (CST) From: Rob Snow To: "Jonathan M. Bresler" cc: "Jordan K. Hubbard" , "Frank E. Terhaar-Yonkers" , p.richards@elsevier.co.uk, FreeBSD-current@FreeBSD.org Subject: Re: ppp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Tue, 19 Dec 1995, Jonathan M. Bresler wrote: > On Tue, 19 Dec 1995, Jordan K. Hubbard wrote: > > > Maybe what has to happen first is you need to figure out a way of > > causing ppp to kill your system *without* running X, e.g. so that > > we can get into ddb and see what's panicing! > > > > it aint ppp. it may well be the configuration that the user has > spec'ed to ppp, but it aint ppp. > > excuse me for being so bloody insistent. it took a while to get > ppp set up correctly. being the kook that i am, i keep hammering on it > till i got the setup right (for me at least). now everyone at my > previous employer uses my config files for ppp, works like a charm. > > BUT you gotta beware of "delete ALL" and setup up your routes > first, during boot, as in: > > ifconfig tun0 inet 198.138.38.205 198.138.38.21 netmask 255.255.255.0 > route add default 198.138.38.205 > > then in /etc/rc.local get ppp going and active > /usr/sbin/ppp -auto atinc > /sbin/ping -c 10 198.138.38.21 > > ONLY THEN do you start X. i use xdm ;) > > Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG > play go. ride bike. hack FreeBSD.--ah the good life > i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG > Hmm, I don't touch tun0 during boot as I found this caused me problems. Here's what my ppp.linkup looks like: ################ BEGIN /etc/ppp/ppp.linkup ################ MYADDR: delete ALL add 0 0 HISADDR ################ END /etc/ppp/ppp.linkup ################## and relevant excerpts from my ppp.conf: ################ BEGIN /etc/ppp/ppp.conf ################## default: set device /dev/cuaa1 set speed 57600 # set mru 1460 disable lqr deny lqr # disable pred1 # deny pred1 # disable vjcomp # deny vjcomp set debug phase set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATZE1Q0 OK-AT-OK \\dATM0DT\\T TIMEOUT 40 CONNECT" ondemand: set phone >PHONE_NUMBER< set login "TIMEOUT 5 login:-\\r-login: >LOGIN< word: >PASSWORD<" set timeout 600 set ifaddr 204.57.120.34/24 204.57.120.3/24 add 0 255.255.255.0 204.57.120.3 ################# END /etc/ppp/ppp.conf ################ This has been working for MONTHS 10-15 minutes an hour 24/7. X is always running and I often kill ppp and restart it from within X. It worked for 23 days once, unattended, while I was out of state. BTW, under both 205 & 210 with hylafax running and Seyon running a script once an evening. __________________________________________________________________ Rob Snow Powered by FreeBSD rsnow@txdirect.net http://www.freebsd.org From owner-freebsd-current Tue Dec 19 22:05:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA01331 for current-outgoing; Tue, 19 Dec 1995 22:05:28 -0800 (PST) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA01326 for ; Tue, 19 Dec 1995 22:05:23 -0800 (PST) Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelayMX-SVR4_1.2/RBINF) id HAA06475; Wed, 20 Dec 1995 07:05:20 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id HAA17180; Wed, 20 Dec 1995 07:05:18 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id HAA04413; Wed, 20 Dec 1995 07:05:15 +0100 To: current@freebsd.org Subject: Re: panic: m_copydata In-reply-to: Your message of "Tue, 19 Dec 1995 16:45:43 PST." <199512200045.QAA28519@waldrog.cs.uidaho.edu> Date: Wed, 20 Dec 1995 07:05:14 +0100 Message-ID: <4412.819439514@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@freebsd.org Precedence: bulk On Tue, 19 Dec 1995 16:45:43 PST, faried nawaz wrote: > from the last core dump i had, > ... Thanks for the info, I'll do my best to find the problem. Andras From owner-freebsd-current Tue Dec 19 23:16:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA03437 for current-outgoing; Tue, 19 Dec 1995 23:16:23 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA03428 for ; Tue, 19 Dec 1995 23:16:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA21287; Wed, 20 Dec 1995 18:15:48 +1100 Date: Wed, 20 Dec 1995 18:15:48 +1100 From: Bruce Evans Message-Id: <199512200715.SAA21287@godzilla.zeta.org.au> To: current@freebsd.org, nate@rocky.sri.MT.net Subject: Re: Mis-feature in -current Sender: owner-current@freebsd.org Precedence: bulk >This one was a strange one, but I finally figured it out. I'm trying to >build kernels which contain all of the necessary 'debug' symbols in >them, so I'm not compiling the code with '-O'. Kernels compiled with any level of optimization (and -g) should contain all the necessary debug symbols. >However, I've noticed that if you don't compile the code with '-O', gcc >no longer optimizes out the calls to strlen. What this means is that >the kernel will no longer link if you compile any modules which uses >strlen(). I found another interesting case related to this. ipx_input() uses an inefficient auto initializer for ipx_ipx. gcc-2.7.0 makes a static copy of the initial data and copies it to the variable a word at a time, but gcc-2.7.2 pessimizes the initialization to two assignments and a memset call. Linking fails because memset isn't in the library. Bruce From owner-freebsd-current Tue Dec 19 23:24:38 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA03782 for current-outgoing; Tue, 19 Dec 1995 23:24:38 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA03775 for ; Tue, 19 Dec 1995 23:24:28 -0800 (PST) Received: from mordillo (oberon.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id IAA23829; Wed, 20 Dec 1995 08:22:46 +0100 (MET) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id VAA01253; Tue, 19 Dec 1995 21:46:32 +0100 From: Thomas Graichen Message-Id: <199512192046.VAA01253@mordillo> Subject: Re: pcnfsd.. To: ulf@z-code.ncd.com (Ulf Zimmermann) Date: Tue, 19 Dec 1995 21:46:31 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <9512190842.ZM13685@zolaris.z-code.com> from "Ulf Zimmermann" at Dec 19, 95 08:42:33 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > On Dec 19, 9:32, Nate Williams wrote: > > Subject: Re: pcnfsd.. > > [ PCNFSD in main FreeBSD source tree ] > > > > > I would say, yes it should be in the main tree, as every "Up-to-date" > > > unix now delivers it. Or least together with their NFS package ;-) > > > > Hmm, although Solaris 2.5 is almost out so I can't check it, both > > Solaris 2.4 and SunOS 4.1 don't ship with pcnfsd. As a matter of fact, > > I don't know of any commercial OS which delivers it. > > > > > > Nate > >-- End of excerpt from Nate Williams > > BSDI, SGI Irix 5.3 for example. > ... DEC OSF/1^H^H^H^H^H^H^H^Higital UNIX, NetBSD ... t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-current Wed Dec 20 00:55:08 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07574 for current-outgoing; Wed, 20 Dec 1995 00:55:08 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07568 for ; Wed, 20 Dec 1995 00:55:03 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA06805; Wed, 20 Dec 1995 09:51:06 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA29078; Wed, 20 Dec 1995 09:51:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id JAA08692; Wed, 20 Dec 1995 09:49:05 +0100 From: J Wunsch Message-Id: <199512200849.JAA08692@uriah.heep.sax.de> Subject: Re: more on 'lost console' To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Wed, 20 Dec 1995 09:49:05 +0100 (MET) Cc: freebsd-current@freefall.freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199512192056.VAA20567@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Dec 19, 95 09:56:42 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG Precedence: bulk As Christoph P. Kukulies wrote: > > I reported that sort of lost console under PCVT. > Fact is, I can't use PCVT-vt-switching at all under > that version of a three weeks old -current. Hmm, does it also resist against software switch attempts (scon -c)? I'm not running -current, but i'm going to upgrade next week. Let me see if i can reproduce 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-current Wed Dec 20 01:10:07 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA08286 for current-outgoing; Wed, 20 Dec 1995 01:10:07 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA08239 for ; Wed, 20 Dec 1995 01:08:44 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA22496; Wed, 20 Dec 1995 10:09:26 +0100 Message-Id: <199512200909.KAA22496@gilberto.physik.rwth-aachen.de> Subject: Re: more on 'lost console' To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 20 Dec 1995 10:09:25 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-current@freefall.freebsd.org In-Reply-To: <199512200849.JAA08692@uriah.heep.sax.de> from "J Wunsch" at Dec 20, 95 09:49:05 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk > > As Christoph P. Kukulies wrote: > > > > I reported that sort of lost console under PCVT. > > Fact is, I can't use PCVT-vt-switching at all under > > that version of a three weeks old -current. > > Hmm, does it also resist against software switch attempts (scon -c)? Interestingly this works. I can e.g. scon -c 2 and get new login: > > I'm not running -current, but i'm going to upgrade next week. Let me > see if i can reproduce 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. ;-) > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Wed Dec 20 03:37:17 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA15435 for current-outgoing; Wed, 20 Dec 1995 03:37:17 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA15430 for ; Wed, 20 Dec 1995 03:37:14 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id DAA03249; Wed, 20 Dec 1995 03:37:01 -0800 (PST) Date: Wed, 20 Dec 1995 03:37:01 -0800 (PST) Message-Id: <199512201137.DAA03249@silvia.HIP.Berkeley.EDU> To: msmith@atrad.adelaide.edu.au CC: nate@rocky.sri.MT.net, jkh@time.cdrom.com, current@freefall.freebsd.org In-reply-to: <199512192252.JAA10809@genesis.atrad.adelaide.edu.au> (message from Michael Smith on Wed, 20 Dec 1995 09:21:59 +1030 (CST)) Subject: Re: pcnfsd.. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG Precedence: bulk * If it moves, so does samba and that DHCP daemon that I keep hearing about 8) * I'd say that they get an awful lot more use than pcnfsd. (Or would if * people knew about them 8) Hmm. Jordan, can you please explain why it can't be happy as a port/package? I can't understand why putting it in the main distribution is going to win over a binary package, which is even on the CD! Satoshi From owner-freebsd-current Wed Dec 20 03:43:47 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA15671 for current-outgoing; Wed, 20 Dec 1995 03:43:47 -0800 (PST) Received: (from jkh@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA15665 for current@freebsd.org; Wed, 20 Dec 1995 03:43:46 -0800 (PST) Date: Wed, 20 Dec 1995 03:43:46 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199512201143.DAA15665@freefall.freebsd.org> To: current@freebsd.org Subject: conf.c and USL copyright at top Sender: owner-current@freebsd.org Precedence: bulk I'm wondering if this can reasonably be assumed to be USL copywritable anymore? :-) It's been almost entirely ripped to shreds by Julian! :-) Jordan From owner-freebsd-current Wed Dec 20 04:06:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA16687 for current-outgoing; Wed, 20 Dec 1995 04:06:56 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA16682 for ; Wed, 20 Dec 1995 04:06:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id EAA00587; Wed, 20 Dec 1995 04:06:49 -0800 To: asami@cs.berkeley.edu (Satoshi Asami) Cc: current@freebsd.org Subject: Re: pcnfsd.. In-reply-to: Your message of "Wed, 20 Dec 1995 03:37:01 PST." <199512201137.DAA03249@silvia.HIP.Berkeley.EDU> Date: Wed, 20 Dec 1995 04:06:48 -0800 Message-ID: <585.819461208@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk It makes enabling it in /etc/sysconfig a one step operation. I can live with it being a two-stepper, but I can't always count on access to the package collection.. :-( Jordan > * If it moves, so does samba and that DHCP daemon that I keep hearing about 8) > * I'd say that they get an awful lot more use than pcnfsd. (Or would if > * people knew about them 8) > > Hmm. > > Jordan, can you please explain why it can't be happy as a > port/package? I can't understand why putting it in the main > distribution is going to win over a binary package, which is even on > the CD! > > Satoshi From owner-freebsd-current Wed Dec 20 04:12:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA16823 for current-outgoing; Wed, 20 Dec 1995 04:12:27 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA16816 for ; Wed, 20 Dec 1995 04:12:24 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id EAA03386; Wed, 20 Dec 1995 04:12:17 -0800 (PST) Date: Wed, 20 Dec 1995 04:12:17 -0800 (PST) Message-Id: <199512201212.EAA03386@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: current@freebsd.org In-reply-to: <585.819461208@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: pcnfsd.. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org Precedence: bulk * It makes enabling it in /etc/sysconfig a one step operation. I can * live with it being a two-stepper, but I can't always count on access * to the package collection.. :-( Well, that's the problem that all programs have, which just happen to not have an entry in /etc/sysconfig. I think things like tcsh and emacs are infinitely (or pretty close to that) more used than pcnfsd on average. Satoshi From owner-freebsd-current Wed Dec 20 04:26:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA17241 for current-outgoing; Wed, 20 Dec 1995 04:26:12 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA17236 for ; Wed, 20 Dec 1995 04:26:09 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id EAA03436; Wed, 20 Dec 1995 04:25:40 -0800 (PST) Date: Wed, 20 Dec 1995 04:25:40 -0800 (PST) Message-Id: <199512201225.EAA03436@silvia.HIP.Berkeley.EDU> To: mark@grondar.za CC: current@FreeBSD.org In-reply-to: <199512191936.VAA12859@grumble.grondar.za> (message from Mark Murray on Tue, 19 Dec 1995 21:35:59 +0200) Subject: Re: Museum pieces... From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.org Precedence: bulk * Also, this was discussed, bit I do not remember the outcome - There are * some X games in the source tree that some of us figured should go to ports/ * (gnuchess also). Can I go ahead? It was me that brought it up the last time. Someone said that they came on the 4.4Lite tape so they should stay. And the discussion kinda died there. I'm all for removing them. If we can't remove something as obvious as this from the main src tree, we have no hope of un-bloating the base system! :> Satoshi From owner-freebsd-current Wed Dec 20 04:27:08 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA17281 for current-outgoing; Wed, 20 Dec 1995 04:27:08 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA17276 for ; Wed, 20 Dec 1995 04:27:04 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id MAA05730; Wed, 20 Dec 1995 12:25:16 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Wed, 20 Dec 1995 12:25:43 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id MAA23325; Wed, 20 Dec 1995 12:25:36 GMT From: Paul Richards Message-Id: <199512201225.MAA23325@cadair.elsevier.co.uk> Subject: Re: pcnfsd.. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 20 Dec 1995 12:25:36 +0000 (GMT) Cc: asami@cs.berkeley.edu, current@FreeBSD.org In-Reply-To: <585.819461208@time.cdrom.com> from "Jordan K. Hubbard" at Dec 20, 95 04:06:48 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > It makes enabling it in /etc/sysconfig a one step operation. I can > live with it being a two-stepper, but I can't always count on access > to the package collection.. :-( > It's not a good idea to try and have evey possible package that people might want to use configured from /etc/sysconfig. I'm not happy about apache being started from /etc/rc for example. This just isn't the way things should be. The "system" startup configuration should only deal with the core functionality that every unix box needs to run. Stuff that only particular sites would use should use some other mechanism. Umm, not to go over old wounds, but the code I changed in sysconfig made this straightforward, which looked in a user-definable directory for startup files which packages would stick there when they were installed. If you want to make it easy to configure pcnfsd then all you do is add a default startup file to the package and when you run pkg_add it just appears on the next reboot as though it was part of the system. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Wed Dec 20 05:25:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA19209 for current-outgoing; Wed, 20 Dec 1995 05:25:30 -0800 (PST) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA19204 Wed, 20 Dec 1995 05:25:27 -0800 (PST) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id IAA15614; Wed, 20 Dec 1995 08:25:20 -0500 for Date: Wed, 20 Dec 1995 08:25:20 -0500 From: "Frank E. Terhaar-Yonkers" Message-Id: <199512201325.IAA15614@robin.mcnc.org.mcnc.org> To: jmb@FreeBSD.org Subject: Re: ppp Cc: FreeBSD-current@FreeBSD.org X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@FreeBSD.org Precedence: bulk Nope. No "delete ALL". If the phone lines are "having a good day" it's solid. But I have days where the lines are so bad, the modem gets confused (USR 28.8 on both ends) and I've no recourse other than killing ppp and restarting. > do you have "delete ALL" in your /etc/ppp/ppp.{linkup,conf} > > this seems to be an X killer. > > every night i start ppp with "ppp -auto foobar". before sleep i >kill ppp with kill -9. X and my machine have been up for 10 days. >X never gets hammered. > > the man page stinks to high heaven. someone needs to read the >code and write a new manpage detailing all the gotchas. a blank line in >/etc/ppp/ppp.conf serves as a null label > >jmb >> > >Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG >play go. ride bike. hack FreeBSD.--ah the good life >i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Wed Dec 20 05:54:51 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA19955 for current-outgoing; Wed, 20 Dec 1995 05:54:51 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA19946 for ; Wed, 20 Dec 1995 05:54:37 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA02773; Thu, 21 Dec 1995 00:49:00 +1100 Date: Thu, 21 Dec 1995 00:49:00 +1100 From: Bruce Evans Message-Id: <199512201349.AAA02773@godzilla.zeta.org.au> To: faulkner@mpd.tandem.com, se@zpr.uni-koeln.de Subject: Re: iozone and mount -o async Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk I'm reopening this old topic. Stefan's mail dated 9 Nov is quoted in full at the end. I happened to try `iozone 900 65536' on a fresh 1GB partition (on the 3rd quarter of a 4G Grand Prix drive with a BT445C controller) mounted with -o async, and noticed that writing is much slower: 3206878 bytes/second for writing the file 5106987 bytes/second for reading the file The sync results are: 4880600 bytes/second for writing the file 5105829 bytes/second for reading the file In old mail, I said that the slowdown is because -o async unavoidably writes in a bad order, and that this didn't matter a lot because it mainly affects stupid benchmarks such as iozone. Now I think that slowdown is because of concurrency problems, not because of a bad order. With -o async, almost all writes are delayed a relatively long time. Huge sequential writes result in the buffer cache becoming full of dirty buffers. These are written one at a time in LRU order in getblk(). LRU order is ideal for huge sequential writes, but getblk() has to wait a lot for free buffers. For non-sequential writes, a cache full of dirty buffers causes bad ordering too. Writing dirty buffers in blkno order when the cache becomes too dirty should work better. sync() should do something similar when a buffer has been dirty for too long. It's important to write nearby dirty buffers if writing them has a low cost (if clustering is done at a lower level and the drive[r] doesn't combine commands, then writing an extra buffer might reduce the number of writes and have a negative cost!). Because of this, sorting shouldn't be left to the hardware - the hardware can't optimize for buffers that will be written 30 seconds later. Bruce >On Nov 8, 16:12, Boyd Faulkner wrote: >} Subject: iozone and mount -o async >} With my Maxtor 235M SCSI 1 drive mounted normally >} >} iozone 32 gives >} IOZONE performance measurements: >} 804903 bytes/second for writing the file >} 1112974 bytes/second for reading the file >} >} mounted with -o async >} IOZONE performance measurements: >} 714042 bytes/second for writing the file >} 1115575 bytes/second for reading the file >I'm seeing slower writes, too, and surprisingly >by about the same absolute amount (some 100KB/s). >My "iozone 32" results are: >se@x14> tail -3 /tmp/sync.io >IOZONE performance measurements: > 2529427 bytes/second for writing the file > 4446135 bytes/second for reading the file >se@x14> tail -3 /tmp/async.io >IOZONE performance measurements: > 2422429 bytes/second for writing the file > 4423241 bytes/second for reading the file >Bonnie gives significantly different results, too: > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >sync 100 1505 98.6 3267 31.2 2167 42.3 1656 98.5 5929 72.1 78.4 9.2 >async 100 1425 96.4 2661 24.3 2077 41.7 1644 98.0 5923 72.1 78.9 9.1 >All tests on the half ful inner (slower) half of my >2GB Atlas driven by an ASUS SP3G, 486DX2/66, NCR SCSI. >Regards, STefan >-- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================== > http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Wed Dec 20 06:06:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA20250 for current-outgoing; Wed, 20 Dec 1995 06:06:46 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA20244 for ; Wed, 20 Dec 1995 06:06:38 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA03231; Thu, 21 Dec 1995 01:01:16 +1100 Date: Thu, 21 Dec 1995 01:01:16 +1100 From: Bruce Evans Message-Id: <199512201401.BAA03231@godzilla.zeta.org.au> To: current@freebsd.org, jkh@freefall.freebsd.org Subject: Re: conf.c and USL copyright at top Sender: owner-current@freebsd.org Precedence: bulk >I'm wondering if this can reasonably be assumed to be USL copywritable >anymore? :-) It's been almost entirely ripped to shreds by Julian! :-) USL probably wrote these parts: the filename :-) their copyright :-) `struct bdevsw ' `int nblkdev = ' `struct cdevsw ' `int nchrdev = ' The rest is probably new in 4.4lite (only device classification functions are left, and they are mainly used to support security levels). It was a mistake to add code to encumbered files. Bruce From owner-freebsd-current Wed Dec 20 06:42:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA21317 for current-outgoing; Wed, 20 Dec 1995 06:42:53 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA21310 for ; Wed, 20 Dec 1995 06:42:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id GAA01142; Wed, 20 Dec 1995 06:42:21 -0800 To: Bruce Evans cc: current@freebsd.org, jkh@freefall.freebsd.org Subject: Re: conf.c and USL copyright at top In-reply-to: Your message of "Thu, 21 Dec 1995 01:01:16 +1100." <199512201401.BAA03231@godzilla.zeta.org.au> Date: Wed, 20 Dec 1995 06:42:21 -0800 Message-ID: <1140.819470541@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk OK, so it was a mistake to add code to encumbered files. No argument from anybody on that point, I'm pretty sure. However, do we just throw up our hands in defeat? I surely hope not! Your analysis below would certainly suggest to me that removing the USL copyright is now an option we can realistically entertain. It's not even remotely "derived" from now. In our CVS tree, we're no worse off than before. In our exported tree, it's one less encumbered file, right? Jordan > >I'm wondering if this can reasonably be assumed to be USL copywritable > >anymore? :-) It's been almost entirely ripped to shreds by Julian! :-) > > USL probably wrote these parts: > > the filename :-) > their copyright :-) > `struct bdevsw ' > `int nblkdev = ' > `struct cdevsw ' > `int nchrdev = ' > > The rest is probably new in 4.4lite (only device classification functions > are left, and they are mainly used to support security levels). > > It was a mistake to add code to encumbered files. > > Bruce From owner-freebsd-current Wed Dec 20 07:08:42 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA22481 for current-outgoing; Wed, 20 Dec 1995 07:08:42 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA22476 for ; Wed, 20 Dec 1995 07:08:37 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id HAA04952; Wed, 20 Dec 1995 07:08:30 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id HAA00180; Wed, 20 Dec 1995 07:08:30 -0800 Message-Id: <199512201508.HAA00180@corbin.Root.COM> To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: conf.c and USL copyright at top In-reply-to: Your message of "Wed, 20 Dec 95 06:42:21 PST." <1140.819470541@time.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 20 Dec 1995 07:08:30 -0800 Sender: owner-current@freebsd.org Precedence: bulk >OK, so it was a mistake to add code to encumbered files. No argument >from anybody on that point, I'm pretty sure. However, do we just >throw up our hands in defeat? I surely hope not! Your analysis below >would certainly suggest to me that removing the USL copyright is now >an option we can realistically entertain. It's not even remotely >"derived" from now. In our CVS tree, we're no worse off than before. >In our exported tree, it's one less encumbered file, right? conf.c will be going away in the near future, anyway, so why is this an issue? -DG From owner-freebsd-current Wed Dec 20 07:14:43 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA22791 for current-outgoing; Wed, 20 Dec 1995 07:14:43 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA22786 for ; Wed, 20 Dec 1995 07:14:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id HAA01396; Wed, 20 Dec 1995 07:14:32 -0800 To: davidg@Root.COM cc: current@freebsd.org Subject: Re: conf.c and USL copyright at top In-reply-to: Your message of "Wed, 20 Dec 1995 07:08:30 PST." <199512201508.HAA00180@corbin.Root.COM> Date: Wed, 20 Dec 1995 07:14:32 -0800 Message-ID: <1393.819472472@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk Are you sure it's genuinely _going away_ or is it just going to become a repository for miscellaneous stub declarations? Jordan > >OK, so it was a mistake to add code to encumbered files. No argument > >from anybody on that point, I'm pretty sure. However, do we just > >throw up our hands in defeat? I surely hope not! Your analysis below > >would certainly suggest to me that removing the USL copyright is now > >an option we can realistically entertain. It's not even remotely > >"derived" from now. In our CVS tree, we're no worse off than before. > >In our exported tree, it's one less encumbered file, right? > > conf.c will be going away in the near future, anyway, so why is this an > issue? > > -DG From owner-freebsd-current Wed Dec 20 07:23:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23396 for current-outgoing; Wed, 20 Dec 1995 07:23:33 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA23391 for ; Wed, 20 Dec 1995 07:23:28 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id HAA04988; Wed, 20 Dec 1995 07:23:27 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id HAA00128; Wed, 20 Dec 1995 07:23:27 -0800 Message-Id: <199512201523.HAA00128@corbin.Root.COM> To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: conf.c and USL copyright at top In-reply-to: Your message of "Wed, 20 Dec 95 07:14:32 PST." <1393.819472472@time.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 20 Dec 1995 07:23:27 -0800 Sender: owner-current@freebsd.org Precedence: bulk >Are you sure it's genuinely _going away_ or is it just going to become >a repository for miscellaneous stub declarations? It's not useful and makes no sense in the future framework of DEVFS. I can't think of any reason why we would would want to keep it. Any declarations that remain after removing bdevsw/cdevsw should be moved to some other file. -DG From owner-freebsd-current Wed Dec 20 07:26:38 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23703 for current-outgoing; Wed, 20 Dec 1995 07:26:38 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA23683 for ; Wed, 20 Dec 1995 07:26:29 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA06304; Thu, 21 Dec 1995 02:23:37 +1100 Date: Thu, 21 Dec 1995 02:23:37 +1100 From: Bruce Evans Message-Id: <199512201523.CAA06304@godzilla.zeta.org.au> To: bde@zeta.org.au, jkh@time.cdrom.com Subject: Re: conf.c and USL copyright at top Cc: current@freebsd.org, jkh@freefall.freebsd.org Sender: owner-current@freebsd.org Precedence: bulk >OK, so it was a mistake to add code to encumbered files. No argument >from anybody on that point, I'm pretty sure. However, do we just >throw up our hands in defeat? I surely hope not! Your analysis below >would certainly suggest to me that removing the USL copyright is now >an option we can realistically entertain. It's not even remotely >"derived" from now. In our CVS tree, we're no worse off than before. >In our exported tree, it's one less encumbered file, right? It's academic for conf.c because the whole file should go away when devfs is finished. tty_conf.c is more interesting. It could be handled more dynamically like conf.c. There isn't as much to gain because the analogue of the major numbers -- the line discipline numbers -- can't be avoided because there is no by-name user interface. Bruce From owner-freebsd-current Wed Dec 20 08:18:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA27452 for current-outgoing; Wed, 20 Dec 1995 08:18:12 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA27427 for ; Wed, 20 Dec 1995 08:18:05 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id RAA02822; Wed, 20 Dec 1995 17:16:38 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: Bruce Evans , current@freebsd.org, jkh@freefall.freebsd.org Subject: Re: conf.c and USL copyright at top In-reply-to: Your message of "Wed, 20 Dec 1995 06:42:21 PST." <1140.819470541@time.cdrom.com> Date: Wed, 20 Dec 1995 17:16:38 +0100 Message-ID: <2820.819476198@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > OK, so it was a mistake to add code to encumbered files. No argument > from anybody on that point, I'm pretty sure. However, do we just > throw up our hands in defeat? I surely hope not! Your analysis below > would certainly suggest to me that removing the USL copyright is now > an option we can realistically entertain. It's not even remotely > "derived" from now. In our CVS tree, we're no worse off than before. > In our exported tree, it's one less encumbered file, right? right. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Dec 20 08:20:51 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA27710 for current-outgoing; Wed, 20 Dec 1995 08:20:51 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA27703 for ; Wed, 20 Dec 1995 08:20:47 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id RAA02868; Wed, 20 Dec 1995 17:19:00 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Bruce Evans cc: jkh@time.cdrom.com, current@freebsd.org, jkh@freefall.freebsd.org Subject: Re: conf.c and USL copyright at top In-reply-to: Your message of "Thu, 21 Dec 1995 02:23:37 +1100." <199512201523.CAA06304@godzilla.zeta.org.au> Date: Wed, 20 Dec 1995 17:19:00 +0100 Message-ID: <2866.819476340@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > >OK, so it was a mistake to add code to encumbered files. No argument > >from anybody on that point, I'm pretty sure. However, do we just > >throw up our hands in defeat? I surely hope not! Your analysis below > >would certainly suggest to me that removing the USL copyright is now > >an option we can realistically entertain. It's not even remotely > >"derived" from now. In our CVS tree, we're no worse off than before. > >In our exported tree, it's one less encumbered file, right? > > It's academic for conf.c because the whole file should go away when > devfs is finished. > > tty_conf.c is more interesting. It could be handled more dynamically > like conf.c. There isn't as much to gain because the analogue of the > major numbers -- the line discipline numbers -- can't be avoided because > there is no by-name user interface. Well, we solved the same thing in VFS with a linker-set... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Dec 20 08:27:01 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA28167 for current-outgoing; Wed, 20 Dec 1995 08:27:01 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA28151 for ; Wed, 20 Dec 1995 08:26:53 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id RAA02795; Wed, 20 Dec 1995 17:15:04 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: asami@cs.berkeley.edu (Satoshi Asami) cc: mark@grondar.za, current@FreeBSD.org Subject: Re: Museum pieces... In-reply-to: Your message of "Wed, 20 Dec 1995 04:25:40 PST." <199512201225.EAA03436@silvia.HIP.Berkeley.EDU> Date: Wed, 20 Dec 1995 17:15:03 +0100 Message-ID: <2793.819476103@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org Precedence: bulk > * Also, this was discussed, bit I do not remember the outcome - There are > * some X games in the source tree that some of us figured should go to ports / > * (gnuchess also). Can I go ahead? > > It was me that brought it up the last time. Someone said that they > came on the 4.4Lite tape so they should stay. And the discussion > kinda died there. > > I'm all for removing them. If we can't remove something as obvious as > this from the main src tree, we have no hope of un-bloating the base > system! :> kill'em. & the old 1.1.5 install in etc as well. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Dec 20 08:41:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA29611 for current-outgoing; Wed, 20 Dec 1995 08:41:46 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA29596 for ; Wed, 20 Dec 1995 08:41:32 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA08865; Thu, 21 Dec 1995 03:36:32 +1100 Date: Thu, 21 Dec 1995 03:36:32 +1100 From: Bruce Evans Message-Id: <199512201636.DAA08865@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.tfs.com Subject: Re: conf.c and USL copyright at top Cc: current@freebsd.org, jkh@freefall.freebsd.org, jkh@time.cdrom.com Sender: owner-current@freebsd.org Precedence: bulk >> tty_conf.c is more interesting. It could be handled more dynamically >> like conf.c. There isn't as much to gain because the analogue of the >> major numbers -- the line discipline numbers -- can't be avoided because >> there is no by-name user interface. >Well, we solved the same thing in VFS with a linker-set... Linker sets can't be used to sove problems related to magic numbers in the user interface. Bruce From owner-freebsd-current Wed Dec 20 08:47:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA00172 for current-outgoing; Wed, 20 Dec 1995 08:47:24 -0800 (PST) Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA00158 for ; Wed, 20 Dec 1995 08:47:14 -0800 (PST) Received: (from nate@localhost) by trout.sri.MT.net (8.6.12/8.6.12) id JAA10218 for current@FreeBSD.org; Wed, 20 Dec 1995 09:47:08 -0700 Date: Wed, 20 Dec 1995 09:47:08 -0700 From: Nate Williams Message-Id: <199512201647.JAA10218@trout.sri.MT.net> To: current@FreeBSD.org Subject: ATAPI patch Sender: owner-current@FreeBSD.org Precedence: bulk Path: helena.MT.net!news.sprintlink.net!newsserver.pixel.kodak.com!bloom-beacon.mit.edu!newsfeed.internetmci.com!in2.uu.net!ulowell.uml.edu!swlnews.msd.ray.com!not-for-mail From: wag@swl.msd.ray.com (William Gianopoulos {84718}) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Patch for ATAPI CD-ROM dirver (wcd.c) to allow playing audio CD's Date: 19 Dec 1995 21:54:39 -0500 Organization: Raytheon Company Lines: 87 Message-ID: <4b7ttf$hme@swlpak.msd.ray.com> NNTP-Posting-Host: swlpak.msd.ray.com I previously reported a problem whereby I could not get xcdplayer to work on an ATAPI CD-ROM drive. I have since determined that there are 2 problems involved. One is that there is no mechanism in the wcd.c driver to read the LEADOUT track data, and the second is that the code to convert the TOC entries to MSF format incorrectly calulates the number of entries to convert. The following patch corrects both problems: *** wcd.c.orig Tue Dec 19 20:24:48 1995 --- wcd.c Tue Dec 19 21:37:58 1995 *************** *** 732,745 **** struct toc *toc = &t->toc; struct toc buf; u_long len; if (! t->toc.hdr.ending_track) return (EIO); ! if (te->starting_track < toc->hdr.starting_track || ! te->starting_track > toc->hdr.ending_track) ! return (EINVAL); ! len = (toc->hdr.ending_track - te->starting_track + 2) * sizeof(toc->tab[0]); if (te->data_len < len) len = te->data_len; --- 732,752 ---- struct toc *toc = &t->toc; struct toc buf; u_long len; + u_char trk; + if (! t->toc.hdr.ending_track) return (EIO); ! if (te->starting_track == 0xAA) { ! trk = toc->hdr.ending_track + 1; ! } else { ! trk = te->starting_track; ! if (trk < toc->hdr.starting_track || ! trk > toc->hdr.ending_track) ! return (EINVAL); ! } ! len = (toc->hdr.ending_track - trk + 2) * sizeof(toc->tab[0]); if (te->data_len < len) len = te->data_len; *************** *** 752,764 **** buf = t->toc; toc = &buf; ! e = toc->tab + toc->hdr.ending_track - ! te->starting_track + 2; while (--e >= toc->tab) lba2msf (e->addr.lba, &e->addr.msf.minute, &e->addr.msf.second, &e->addr.msf.frame); } ! if (copyout (toc->tab + te->starting_track - toc->hdr.starting_track, te->data, len) != 0) error = EFAULT; break; --- 759,771 ---- buf = t->toc; toc = &buf; ! e = toc->tab - toc->hdr.starting_track + ! trk + 2; while (--e >= toc->tab) lba2msf (e->addr.lba, &e->addr.msf.minute, &e->addr.msf.second, &e->addr.msf.frame); } ! if (copyout (toc->tab + trk - toc->hdr.starting_track, te->data, len) != 0) error = EFAULT; break; This still leaves a problem for which I have no patch, which is that the code to set the volume does not work, but my speakers have volume controls which I find easier to use anyway, so I didn't spend all that much time looking for that problem! -- William A. Gianopoulos; Raytheon Electronic Systems wag@swl.msd.ray.com -------------------------------------------------------- This is my personal opinion and not that of my employer. From owner-freebsd-current Wed Dec 20 08:58:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA01057 for current-outgoing; Wed, 20 Dec 1995 08:58:35 -0800 (PST) Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA01052 for ; Wed, 20 Dec 1995 08:58:30 -0800 (PST) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id KAA04047 for ; Wed, 20 Dec 1995 10:58:26 -0600 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Wed, 20 Dec 95 10:58 CST Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Wed, 20 Dec 95 10:58 CST Message-Id: Subject: Changes to sio/tty devices over the last 2 weeks To: current@freebsd.org Date: Wed, 20 Dec 1995 10:58:24 -0600 (CST) From: "Lars Fredriksen" X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk Hi, I just rebuilt current as of yesterday, and I am now seeing problems both with pppd and faxgetty. Tip seems ok. pppd will not finish lcp negotiation(times out), and faxgetty is unsuccessfull setting up the modem. The output from the faxgetty log shows: Dec 20 09:01:10 fredriks FaxGetty[179]: MODEM set DTR ON Dec 20 09:01:10 fredriks FaxGetty[179]: MODEM set baud rate: 57600 baud, input f low RTS/CTS, output flow RTS/CTS Dec 20 09:01:10 fredriks FaxGetty[179]: MODEM flush i/o Dec 20 09:01:10 fredriks FaxGetty[179]: <-- [43:AT&B1&N0&S0*F0S18=3S38.3=1S39=0E 0V1Q0S0=0H0] Dec 20 09:01:11 fredriks FaxGetty[179]: --> [28:AT&B1&N0&S0*F0S180V1Q0S0=0H0] Dec 20 09:01:11 fredriks FaxGetty[179]: --> [5:ERROR] Dec 20 09:01:11 fredriks FaxGetty[179]: MODEM Command error Dec 20 09:01:11 fredriks FaxGetty[179]: MODEM set DTR OFF Dec 20 09:01:11 fredriks FaxGetty[179]: MODEM set baud rate: 0 baud (flow contro l unchanged) Dec 20 09:01:11 fredriks FaxGetty[179]: /dev/ttyd0: Can not deduce modem type. Dec 20 09:01:11 fredriks login: ROOT LOGIN (root) ON ttyv0 It looks like the modem only gets about half the characters sent to it. This should look like this: Dec 20 09:06:55 fredriks FaxGetty[182]: MODEM set DTR ON Dec 20 09:06:55 fredriks FaxGetty[182]: MODEM set baud rate: 57600 baud, input f low RTS/CTS, output flow RTS/CTS Dec 20 09:06:55 fredriks FaxGetty[182]: MODEM flush i/o Dec 20 09:06:55 fredriks FaxGetty[182]: <-- [43:AT&B1&N0&S0*F0S18=3S38.3=1S39=0E 0V1Q0S0=0H0] Dec 20 09:06:55 fredriks FaxGetty[182]: --> [43:AT&B1&N0&S0*F0S18=3S38.3=1S39=0E 0V1Q0S0=0H0] Dec 20 09:06:55 fredriks FaxGetty[182]: --> [2:OK] The pppd log shows: Dec 20 00:05:21 fredriks pppd[72]: sent [LCP ConfReq id=0x1 ] Dec 20 00:05:22 fredriks pppd[72]: rcvd [LCP ConfReq id=0x5 < 13 03 00>] Dec 20 00:05:22 fredriks pppd[72]: sent [LCP ConfRej id=0x5 < 13 03 00>] Dec 20 00:05:24 fredriks pppd[72]: sent [LCP ConfReq id=0x1 ] Dec 20 00:05:27 fredriks pppd[72]: LCP: timeout sending Config-Requests Dec 20 00:05:27 fredriks pppd[72]: Connection terminated. Dec 20 00:05:27 fredriks pppd[72]: Exit. Here is a good one: Dec 20 09:09:30 fredriks pppd[244]: sent [LCP ConfAck id=0x1 ] Dec 20 09:09:33 fredriks pppd[244]: sent [LCP ConfReq id=0x1 ] Dec 20 09:09:33 fredriks pppd[244]: rcvd [LCP ConfAck id=0x1 ] Dec 20 09:09:33 fredriks pppd[244]: sent [IPCP ConfReq id=0x1 ] Dec 20 09:09:33 fredriks pppd[244]: sent [CCP ConfReq id=0x1 ] Dec 20 09:09:33 fredriks pppd[244]: rcvd [IPCP ConfReq id=0x2 ] Dec 20 09:09:33 fredriks pppd[244]: sent [IPCP ConfAck id=0x2 ] Dec 20 09:09:33 fredriks pppd[244]: rcvd [proto=0x8029] 01 03 00 04 Dec 20 09:09:33 fredriks pppd[244]: Unknown protocol (0x8029) received Dec 20 09:09:33 fredriks pppd[244]: sent [LCP ProtRej id=0x2 80 29 01 03 00 04] Dec 20 09:09:33 fredriks pppd[244]: rcvd [IPCP ConfAck id=0x1 ] Dec 20 09:09:33 fredriks pppd[244]: local IP address 199.3.36.197 Dec 20 09:09:33 fredriks pppd[244]: remote IP address 199.3.35.100 Does Bruce or someone have an idea of what might be going on here? I saw some patches flying yesterday regarding serial stuff. Are they relevant to this problem? Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks.pr.mcs.net (home-home) fredriks@asiago.cs.wisc.edu From owner-freebsd-current Wed Dec 20 09:34:15 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA04575 for current-outgoing; Wed, 20 Dec 1995 09:34:15 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA04570 for ; Wed, 20 Dec 1995 09:34:09 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id RAA06664 for ; Wed, 20 Dec 1995 17:32:27 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Wed, 20 Dec 1995 17:33:00 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id RAA27092 for FreeBSD-current@FreeBSD.org; Wed, 20 Dec 1995 17:32:58 GMT From: Paul Richards Message-Id: <199512201732.RAA27092@cadair.elsevier.co.uk> Subject: Re: conf.c and USL copyright at top To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Wed, 20 Dec 1995 17:32:58 +0000 (GMT) In-Reply-To: <2820.819476198@critter.tfs.com> from "Poul-Henning Kamp" at Dec 20, 95 05:16:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Poul-Henning Kamp who said > > > OK, so it was a mistake to add code to encumbered files. No argument > > from anybody on that point, I'm pretty sure. However, do we just > > throw up our hands in defeat? I surely hope not! Your analysis below > > would certainly suggest to me that removing the USL copyright is now > > an option we can realistically entertain. It's not even remotely > > "derived" from now. In our CVS tree, we're no worse off than before. > > In our exported tree, it's one less encumbered file, right? > right. > I don't think you can do that. Even if it's all completely new code you've been sticking it in a file with a USL copyright. You can't just rip off that copyright. Whoever made the changes released them under the USL copyright, I don't think you can do that either :-) You need to replace it with a completely rewritten file like Bill has done with the yp stuff. Of course, if a lot of the lines in the old file are yours and you type them into the new file because they're in your head then that's up to you :-) Not relevant for conf.c but it's worth getting the principle understood so people know what they can and can't do. The one thing you definately shouldn't do is check the thing out and then check it back in with a different copyright because it's not your copyright to remove. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Wed Dec 20 09:56:59 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA06760 for current-outgoing; Wed, 20 Dec 1995 09:56:59 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06755 for ; Wed, 20 Dec 1995 09:56:54 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA21859; Wed, 20 Dec 1995 12:56:53 -0500 Date: Wed, 20 Dec 1995 12:56:53 -0500 From: "Garrett A. Wollman" Message-Id: <9512201756.AA21859@halloran-eldar.lcs.mit.edu> To: FreeBSD-Current Mailing List Subject: More ancient IP broadcast cruft to be removed Sender: owner-current@FreeBSD.ORG Precedence: bulk ip_input() currently contains the following piece of code: /* * Look for all-0's host part (old broadcast addr), * either for subnet or net. */ t = ntohl(ip->ip_dst.s_addr); if (t == ia->ia_subnet) goto ours; if (t == ia->ia_net) goto ours; The function of this code is to accept `broadcasts' sent to the host-all-zeros address, which was used in 4.2 as the broadcast address, IN ADDITION TO anything that happens to be configured as an explicit broadcast address. I believe that this code is a waste of time. If the user wants to accept broadcasts on the host-all-zeros address, then she should configure the interface for that broadcast address. (Using the standard broadcast address would not work to communicate with old machines anyway, so this hack doesn't really gain one anything.) I plan to disable this code, unless someone has a correctly-configured network which doesn't work without it. Speak now or forever hold your peace! -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Dec 20 10:05:43 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA07387 for current-outgoing; Wed, 20 Dec 1995 10:05:43 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA07382 for ; Wed, 20 Dec 1995 10:05:40 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.1+2.6Wbeta4/3.3W9) with ESMTP id DAA00568 for ; Thu, 21 Dec 1995 03:05:38 +0900 (JST) Message-Id: <199512201805.DAA00568@marble.eps.nagoya-u.ac.jp> To: current@freebsd.org Subject: outb in random.c X-Mailer: Mew beta version 0.96 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 21 Dec 1995 03:05:37 +0900 From: KATO Takenori Sender: owner-current@freebsd.org Precedence: bulk The function add_timer_randomness() in sys/i386/isa/random.c contains: outb(TIMER_LATCH|TIMER_SEL0, TIMER_MODE); /* latch the count ASAP */ This is outb(data, port). I think this should be outb(TIMER_MODE, TIMER_LATCH|TIMER_SEL0); /* latch the count ASAP */ ---- KATO Takenori Dept. Earth Planet. Sci. Nagoya Univ. Nagoya 464-01 Voice: +81-52-789-2529 E-mail: kato@eclogite.eps.nagoya-u.ac.jp From owner-freebsd-current Wed Dec 20 10:12:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA07965 for current-outgoing; Wed, 20 Dec 1995 10:12:34 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA07957 for ; Wed, 20 Dec 1995 10:12:28 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tSSwU-0000zcC; Wed, 20 Dec 95 12:08 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tSSnz-000CB9C; Wed, 20 Dec 95 11:59 WET Message-Id: Date: Wed, 20 Dec 95 11:59 WET To: current@freebsd.org, jkh@freefall.freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Wed Dec 20 1995, 11:59:55 CST Subject: Re: conf.c and USL copyright at top Sender: owner-current@freebsd.org Precedence: bulk [2]The ground shaketh and jkh said to the people: [2]OK, so it was a mistake to add code to encumbered files. No argument [2]from anybody on that point, I'm pretty sure. However, do we just [2]throw up our hands in defeat? I surely hope not! Your analysis below [2]would certainly suggest to me that removing the USL copyright is now [2]an option we can realistically entertain. It's not even remotely [2]"derived" from now. In our CVS tree, we're no worse off than before. [2]In our exported tree, it's one less encumbered file, right? According to the lawyers at two major corporations I have worked at, if you have changed more than 12% of the functional code, it's yours. (Changing variable names and comments don't count.) Apparently the 12% is some magic number applied to adaptations of novels and music by the US Copyright Office. Ever notice how a piece of music written three hundred years ago has a 1976 copyright? Well, someone wrote a descant consisting of a dozen held notes and Walla! In the US you get a free copyright on the "new" work, even though probably nobody will play that variation at all. Well these software company lawyers says the same rule applies to all works that can exist on paper and software falls in that category. Even if we all agree that it is no longer contains USLs code (or the faintest shadow of USLs code), should we at least give credit (but no copyright) to USL, much in the same way we ask for credit in the BSD Copyright if someone "rips to shreds" but uses our code? Perhaps a simple "Thanks to USL for their original work on %s" would suffice. Or perhaps credit the person actually responsible, rather than USL which wasn't even around when this stuff was written. Frank Durda IV |"I'm not a lawyer, but I sound or uhclem%nemesis@fw.ast.com (Fastest Route)| like one." - Firesign theatre ...letni!rwsys!nemesis!uhclem |"I'm not a lawyer, but I got ...decvax!fw.ast.com!nemesis!uhclem | deposed by one." - ME From owner-freebsd-current Wed Dec 20 17:11:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA27646 for current-outgoing; Wed, 20 Dec 1995 17:11:46 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA27638 for ; Wed, 20 Dec 1995 17:11:26 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA26975; Thu, 21 Dec 1995 12:06:57 +1100 Date: Thu, 21 Dec 1995 12:06:57 +1100 From: Bruce Evans Message-Id: <199512210106.MAA26975@godzilla.zeta.org.au> To: current@FreeBSD.ORG, kato@eclogite.eps.nagoya-u.ac.jp Subject: Re: outb in random.c Sender: owner-current@FreeBSD.ORG Precedence: bulk The function add_timer_randomness() in sys/i386/isa/random.c contains: > outb(TIMER_LATCH|TIMER_SEL0, TIMER_MODE); /* latch the count ASAP */ >This is outb(data, port). I think this should be > outb(TIMER_MODE, TIMER_LATCH|TIMER_SEL0); /* latch the count ASAP */ Gak! outb() and inb() are well known to have back to front args in Linux, where this code was derived from. This outb clobbers i/o port 0 (part of the address for DMA channel 0) and the following inb's give a result that is random in a different way than was intended. Bruce From owner-freebsd-current Wed Dec 20 17:16:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA27809 for current-outgoing; Wed, 20 Dec 1995 17:16:36 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA27802 for ; Wed, 20 Dec 1995 17:16:21 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA27086; Thu, 21 Dec 1995 12:11:34 +1100 Date: Thu, 21 Dec 1995 12:11:34 +1100 From: Bruce Evans Message-Id: <199512210111.MAA27086@godzilla.zeta.org.au> To: current@freebsd.org, fredriks@mcs.com Subject: Re: Changes to sio/tty devices over the last 2 weeks Sender: owner-current@freebsd.org Precedence: bulk >Does Bruce or someone have an idea of what might be going on here? I saw >some patches flying yesterday regarding serial stuff. Are they relevant to >this problem? Don't know. The only changes to sio/tty lately were an increase of the guaranteed output queue size and buggy 16650 support. I'll disable the latter later today. Bruce From owner-freebsd-current Wed Dec 20 21:09:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA11815 for current-outgoing; Wed, 20 Dec 1995 21:09:04 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA11799 for ; Wed, 20 Dec 1995 21:08:59 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA02636; Thu, 21 Dec 1995 16:02:31 +1100 Date: Thu, 21 Dec 1995 16:02:31 +1100 From: Bruce Evans Message-Id: <199512210502.QAA02636@godzilla.zeta.org.au> To: mi@aldan.star89.galstar.com Subject: Re: Chalenging strength of the BSD net-code (Re: Second modem and ppp1) Newsgroups: muc.lists.freebsd.questions,comp.unix.bsd.freebsd.misc In-Reply-To: <4b5lio$d44@news.bu.edu> References: <4atqh5$mhp@news.bu.edu> Organization: Kralizec Dialup Unix Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk This still causes a panic in freebsd-current. bcmp is called with a null source pointer. The stack trace according to ddb is: _bcmp _ifa_ifwithroute _rtrequest _route_output _raw_usrreq _route_usrreq _sosend _soo_write _write _syscall Bruce In article <4b5lio$d44@news.bu.edu> you write: >In article <4atqh5$mhp@news.bu.edu>, I wrote: >>If I start the second pppd, all goes fine, I'm getting a >>new name, ip-address. But, when I try to, say, telnet to >>the second peer, connection goes thru the FIRST one. And >>the other modem, stays idle. My experiments with >> route add >> route change >>were rather unsuccessful so far ): >> > >Here is what I did and caused crash (not once -- can be repeated): > pppd file /etc/ppp/options cuaa2 > pppd file /etc/ppp/options.second cuaa1 > route add -net 204 -link ppp1 > >Boom, Trap 12. Reboot. If anybody cares, kernel with tracing and debugging >is being built now. In the mean time, how to configure routes safely, so >that some packets will go thru the second modem (ppp1 link)? Thanks a lot! > > -mi From owner-freebsd-current Wed Dec 20 21:21:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA13191 for current-outgoing; Wed, 20 Dec 1995 21:21:33 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA13180 for ; Wed, 20 Dec 1995 21:21:29 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA18215 for ; Thu, 21 Dec 1995 06:21:25 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA08153 for freebsd-current@FreeBSD.org; Thu, 21 Dec 1995 06:21:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id AAA12464 for freebsd-current@FreeBSD.org; Thu, 21 Dec 1995 00:32:48 +0100 From: J Wunsch Message-Id: <199512202332.AAA12464@uriah.heep.sax.de> Subject: disklabel -r -w rz2 rzxx To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 21 Dec 1995 00:32:47 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk Geeze. I've been installing a new SCSI disk at a customer lately who is running digital unix. Interestingly enough, everything around the file system (disklabel, newfs) looked very confident to me. Well, they've got one (undocumented, of course) feature i found interesting: in order to write the disklabel for the first time onto an unlabelled disk, you could provide it with the argument "rzxx", and the system figured out the basic parameters of the drive (and made an initial suggestion for the file systems). I thought of this being a neat idea, and actually all we need in order to implement it would be that ioctl(DIOCGDINFO) would fill in as much parameters for an unlabelled disk as the driver does already know. Of course, "rzxx" is a poor naming, i would rather suggest "auto". -- 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-current Wed Dec 20 22:41:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA17040 for current-outgoing; Wed, 20 Dec 1995 22:41:46 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA17033 for ; Wed, 20 Dec 1995 22:41:36 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id HAA14719 ; Thu, 21 Dec 1995 07:41:31 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id HAA25768 ; Thu, 21 Dec 1995 07:41:24 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id AAA13591; Thu, 21 Dec 1995 00:01:57 +0100 (MET) From: Ollivier Robert Message-Id: <199512202301.AAA13591@keltia.freenix.fr> Subject: Re: pcnfsd.. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 21 Dec 1995 00:01:57 +0100 (MET) Cc: asami@cs.berkeley.edu, current@freebsd.org In-Reply-To: <585.819461208@time.cdrom.com> from "Jordan K. Hubbard" at Dec 20, 95 04:06:48 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1449 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk It seems that Jordan K. Hubbard said: > It makes enabling it in /etc/sysconfig a one step operation. I can > live with it being a two-stepper, but I can't always count on access > to the package collection.. :-( Well, to be honest, Apache is in /etc/sysconfig and still in ports only so I think pcnfsd can stay in ports. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Dec 18 00:50:47 MET 1995 From owner-freebsd-current Wed Dec 20 23:11:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA17789 for current-outgoing; Wed, 20 Dec 1995 23:11:35 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA17780 for ; Wed, 20 Dec 1995 23:11:31 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id IAA24481 for current@freebsd.org; Thu, 21 Dec 1995 08:00:17 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id HAA00558 for ; Thu, 21 Dec 1995 07:18:26 +0100 (MET) Date: Thu, 21 Dec 1995 07:18:26 +0100 (MET) From: Andreas Klemm To: current@freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512191632.JAA26625@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Tue, 19 Dec 1995, Nate Williams wrote: > [ PCNFSD in main FreeBSD source tree ] > > > I would say, yes it should be in the main tree, as every "Up-to-date" > > unix now delivers it. Or least together with their NFS package ;-) > > Hmm, although Solaris 2.5 is almost out so I can't check it, both > Solaris 2.4 and SunOS 4.1 don't ship with pcnfsd. As a matter of fact, > I don't know of any commercial OS which delivers it. Sun doesn't ship it with Solaris 1 and 2. Sun ships it with PC-NFS. As far as I know SCO ships it with the main system as well as HP. I disussed this with people from ESKER who sell the connectivity package TUN. They didn't know, that SUN doesn't ship it but ... they relied upon it ;-) I think it would be kind of extra service, to integrate this basic connectivity product into the base system. -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Wed Dec 20 23:20:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA18104 for current-outgoing; Wed, 20 Dec 1995 23:20:56 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA18099 for ; Wed, 20 Dec 1995 23:20:53 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id IAA24485; Thu, 21 Dec 1995 08:00:19 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id HAA00564; Thu, 21 Dec 1995 07:19:49 +0100 (MET) Date: Thu, 21 Dec 1995 07:19:48 +0100 (MET) From: Andreas Klemm To: Paul Richards cc: Nate Williams , kuku@gilberto.physik.rwth-aachen.de, current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512191755.RAA09280@cadair.elsevier.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Tue, 19 Dec 1995, Paul Richards wrote: > In reply to Nate Williams who said > > > > I didn't say it was useless. I said it wasn't useful for the generic > > user. And, with it so easy to get as a port I don't see why it should > > become part of the system. I suspect 'fvwm' is more useful to the > > generic user, but it's not part of the base sources. :) > > Or Samba :-) Very clever argued ;-) What about z-modem ? ;-) -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Thu Dec 21 00:08:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA20178 for current-outgoing; Thu, 21 Dec 1995 00:08:12 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA20169 for ; Thu, 21 Dec 1995 00:08:06 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA09744; Thu, 21 Dec 1995 19:05:57 +1100 Date: Thu, 21 Dec 1995 19:05:57 +1100 From: Bruce Evans Message-Id: <199512210805.TAA09744@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: disklabel -r -w rz2 rzxx Sender: owner-current@FreeBSD.org Precedence: bulk >Geeze. I've been installing a new SCSI disk at a customer lately who >is running digital unix. Interestingly enough, everything around the >file system (disklabel, newfs) looked very confident to me. >Well, they've got one (undocumented, of course) feature i found >interesting: in order to write the disklabel for the first time onto >an unlabelled disk, you could provide it with the argument "rzxx", and >the system figured out the basic parameters of the drive (and made an >initial suggestion for the file systems). >I thought of this being a neat idea, and actually all we need in order >to implement it would be that ioctl(DIOCGDINFO) would fill in as much >parameters for an unlabelled disk as the driver does already know. It already does. The known parameters are available for the whole drive and can easily be used for dangerously dedicated drives, e.g., disklabel /dev/rsd0 | sed -e 's/^rpm: 0$/rpm: 3600/' -e 's/^interleave: 0$/interleave: 1/' | disklabel -R -r /dev/rsd0 /dev/stdin Here the sed commands substitute some of the unknown values with possibly-bogus but working values. Of course, the fact that this works means that the label isn't necessary except for its partitioning function. Handling slices is more complicated. Apart from DIOCGDINFO only being implemented for slices that already have a BSD label, it is important for the slices to be allocated before the labels. How does digital handle the extra layer of complications? ;-) Bruce From owner-freebsd-current Thu Dec 21 03:28:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA03692 for current-outgoing; Thu, 21 Dec 1995 03:28:11 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA03483 for ; Thu, 21 Dec 1995 03:23:29 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA12045 for ; Thu, 21 Dec 1995 12:21:24 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id MAA10248 for freebsd-current@FreeBSD.org; Thu, 21 Dec 1995 12:21:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id JAA14524 for freebsd-current@FreeBSD.org; Thu, 21 Dec 1995 09:51:42 +0100 From: J Wunsch Message-Id: <199512210851.JAA14524@uriah.heep.sax.de> Subject: Re: disklabel -r -w rz2 rzxx To: freebsd-current@FreeBSD.org Date: Thu, 21 Dec 1995 09:51:42 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199512210805.TAA09744@godzilla.zeta.org.au> from "Bruce Evans" at Dec 21, 95 07:05:57 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > >I thought of this being a neat idea, and actually all we need in order > >to implement it would be that ioctl(DIOCGDINFO) would fill in as much > >parameters for an unlabelled disk as the driver does already know. > > It already does. The known parameters are available for the whole > drive and can easily be used for dangerously dedicated drives, e.g., > > disklabel /dev/rsd0 | > sed -e 's/^rpm: 0$/rpm: 3600/' -e 's/^interleave: 0$/interleave: 1/' | > disklabel -R -r /dev/rsd0 /dev/stdin > > Here the sed commands substitute some of the unknown values with > possibly-bogus but working values. Hmm, interesting. For which devices? Short of a real empty disk to test with, i've only been playing with vn devices :), and all i've got was: Dec 21 00:19:43 uriah /kernel: vn0: invalid primary partition table: no magic Dec 21 00:20:17 uriah /kernel: vn0: invalid primary partition table: no magic Dec 21 00:20:17 uriah /kernel: vn0: invalid primary partition table: no magic Dec 21 00:21:51 uriah last message repeated 5 times Dec 21 00:21:51 uriah last message repeated 5 times (I would have played with floppies, too, but i realized that they are not even supposed to work. Though it's probably not a big deal to make them work.) > Of course, the fact that this works means that the label isn't necessary > except for its partitioning function. That's what i'm expecting. > Handling slices is more complicated. Apart from DIOCGDINFO only being > implemented for slices that already have a BSD label, it is important > for the slices to be allocated before the labels. How does digital > handle the extra layer of complications? ;-) What's a slice? :-) :-) -- 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-current Thu Dec 21 04:29:37 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA05821 for current-outgoing; Thu, 21 Dec 1995 04:29:37 -0800 (PST) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA05814 for ; Thu, 21 Dec 1995 04:29:34 -0800 (PST) Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id NAA05083; Thu, 21 Dec 1995 13:28:42 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Bruce Evans cc: current@freebsd.org, jkh@freefall.freebsd.org, jkh@time.cdrom.com Subject: Re: conf.c and USL copyright at top In-reply-to: Your message of "Thu, 21 Dec 1995 03:36:32 +1100." <199512201636.DAA08865@godzilla.zeta.org.au> Date: Thu, 21 Dec 1995 13:28:42 +0100 Message-ID: <5081.819548922@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > >> tty_conf.c is more interesting. It could be handled more dynamically > >> like conf.c. There isn't as much to gain because the analogue of the > >> major numbers -- the line discipline numbers -- can't be avoided because > >> there is no by-name user interface. > > >Well, we solved the same thing in VFS with a linker-set... > > Linker sets can't be used to sove problems related to magic numbers in > the user interface. Filesystems have a magic number as well. What I meant was that we could register the line-disciplines along the lines we register VFS's. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Dec 21 05:59:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA08927 for current-outgoing; Thu, 21 Dec 1995 05:59:44 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA08922 Thu, 21 Dec 1995 05:59:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id FAA19603; Thu, 21 Dec 1995 05:59:32 -0800 To: ache@freebsd.org cc: current@freebsd.org Subject: Major changes to libdialog planned. Date: Thu, 21 Dec 1995 05:59:32 -0800 Message-ID: <19594.819554372@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk Just a heads-up in case you (or anybody else) are doing any work in there? I'd like to bring in some fundamental changes that will be entirely backwards compatible with old client code but definitely not internally. With my next commit, the libdialog API will support an additional calling syntax which allows individual menu items to support "check" and "fire" actions. In radio/multi-choice menus, the check action can manipulate internal variables to control mutual exclusion and such (sysinstall can *definitely* use this feature!). Individual fire actions do away with having to parse that evil `result' string when you're just using libdialog from an application. While I was at it, I also gave you the ability to change the labels in the "OK and Cancel" buttons as well as wire callbacks to them for special case handling. After I finish up this commit, I have plans to go into print_autowrap() and add character attributes and colors. It's the first step to being able to write a decent HTML display text box so we can shake our reliance on lynx (though that's quite a bit farther into the future, so we'll see!) and of immediate use in sparking up the documentation a bit. Then maybe I'll add character entry callbacks to the text entry routines. :-) Any objections, scream now, though I'd actually rather that folks wait for my commit before doing so too much. One of the other things I'm bringing in is a *man page* for libdialog which explains how the whole system works and it'd be nice if people at least read the spec before flaming it. :-) Jordan From owner-freebsd-current Thu Dec 21 09:09:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA18850 for current-outgoing; Thu, 21 Dec 1995 09:09:16 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA18844 for ; Thu, 21 Dec 1995 09:09:13 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA26246; Thu, 21 Dec 1995 12:09:10 -0500 Date: Thu, 21 Dec 1995 12:09:10 -0500 From: "Garrett A. Wollman" Message-Id: <9512211709.AA26246@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@freebsd.org Subject: MOUNT_* constants In-Reply-To: <5081.819548922@critter.tfs.com> References: <199512201636.DAA08865@godzilla.zeta.org.au> <5081.819548922@critter.tfs.com> Sender: owner-current@freebsd.org Precedence: bulk < said: >> Linker sets can't be used to sove problems related to magic numbers in >> the user interface. > Filesystems have a magic number as well. It's intended that said magic number will go away, and all mapping will be dynamic. There is almost no need for them now, except the compatibility cruft in the mount_* programs. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Dec 21 09:21:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA19808 for current-outgoing; Thu, 21 Dec 1995 09:21:56 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA19798 for ; Thu, 21 Dec 1995 09:21:49 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA27383; Thu, 21 Dec 1995 12:21:28 -0500 Date: Thu, 21 Dec 1995 12:21:28 -0500 From: "Garrett A. Wollman" Message-Id: <9512211721.AA27383@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: mi@aldan.star89.galstar.com, current@FreeBSD.org Subject: Re: Chalenging strength of the BSD net-code (Re: Second modem and ppp1) Newsgroups: muc.lists.freebsd.questions,comp.unix.bsd.freebsd.misc In-Reply-To: <199512210502.QAA02636@godzilla.zeta.org.au> References: <4atqh5$mhp@news.bu.edu> <4b5lio$d44@news.bu.edu> <199512210502.QAA02636@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.org Precedence: bulk <> Here is what I did and caused crash (not once -- can be repeated): >> pppd file /etc/ppp/options cuaa2 >> pppd file /etc/ppp/options.second cuaa1 >> route add -net 204 -link ppp1 This `route' command is invalid, so it is not at all surprising to me that it does not work for you. (It shouldn't cause a panic, though. If you could provide more detailed information, I might be able to track it down.) First off, it does not make any sense to add a route to network 0.0.0.204 (which, when masked with the default netmask for a class A, turns into 0.0.0.0). Secondly, it doesn't make any sense to specify `-link ppp1' for this sort of route. You should instead specify the address of the /other end/ of the PPP interface. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Dec 21 10:06:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22664 for current-outgoing; Thu, 21 Dec 1995 10:06:41 -0800 (PST) Received: from deep-thought.demos.su (root@deep-thought.demos.su [194.87.1.76]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA22654 Thu, 21 Dec 1995 10:06:13 -0800 (PST) Received: by deep-thought.demos.su id VAA02547; (8.7.3/D) Thu, 21 Dec 1995 21:04:06 +0300 (MSK) To: current@freebsd.org Cc: nate@freebsd.org Message-ID: Organization: DEMOS Date: Thu, 21 Dec 1995 21:04:05 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: LD hits again :-( Lines: 14 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Watch this: cc -O2 -m486 -fno-strength-reduce -L/usr/src/secure/usr.bin/bdes/../../lib/libcipher/obj -o bdes bdes.o -lcipher bdes.o: WARNING! des_setkey(3) not present in the system! bdes.o: WARNING! des_cipher(3) not present in the system! Note: shared libchipher exists in given -Lpath. You can reproduce it by yourself in -current. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Dec 21 10:27:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA23803 for current-outgoing; Thu, 21 Dec 1995 10:27:28 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA23798 Thu, 21 Dec 1995 10:27:23 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA03382; Thu, 21 Dec 1995 11:29:07 -0700 Date: Thu, 21 Dec 1995 11:29:07 -0700 From: Nate Williams Message-Id: <199512211829.LAA03382@rocky.sri.MT.net> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) Cc: current@freebsd.org, nate@freebsd.org Subject: Re: LD hits again :-( In-Reply-To: References: Sender: owner-current@freebsd.org Precedence: bulk > cc -O2 -m486 -fno-strength-reduce -L/usr/src/secure/usr.bin/bdes/../../lib/libcipher/obj -o bdes bdes.o -lcipher > bdes.o: WARNING! des_setkey(3) not present in the system! > bdes.o: WARNING! des_cipher(3) not present in the system! > > Note: shared libchipher exists in given -Lpath. I've seen this, but I don't know why this is being printed. It's certainly not a function of the linker. Ahh, I see. It's picking up the versions in libc rather than the static versions in lib/libcipher/obj/libcipher.a. I agree it's a bug, and it *will* be looked at. However, we're still resolving the last of the ld.so changes, so until that gets done the other stuff won't get done. :( Nate From owner-freebsd-current Thu Dec 21 10:28:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA24005 for current-outgoing; Thu, 21 Dec 1995 10:28:12 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA24000 for ; Thu, 21 Dec 1995 10:28:08 -0800 (PST) Received: (from julian@localhost) by jhome.DIALix.COM (8.7.3/8.7.3) id SAA07395; Thu, 21 Dec 1995 18:27:37 GMT From: Julian Elischer Message-Id: <199512211827.SAA07395@jhome.DIALix.COM> Subject: Re: MOUNT_* constants To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Thu, 21 Dec 1995 18:27:36 +0000 () Cc: phk@critter.tfs.com, current@freebsd.org In-Reply-To: <9512211709.AA26246@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Dec 21, 95 12:09:10 pm X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > > > > < said: > > >> Linker sets can't be used to sove problems related to magic numbers in > >> the user interface. > > > Filesystems have a magic number as well. > > It's intended that said magic number will go away, and all mapping > will be dynamic. There is almost no need for them now, except the > compatibility cruft in the mount_* programs. The other thing I want to make dynamic is AF_INET and related constants... I see no reason to not have a pointer to a string "inet" for compatibility we can make pointers < 32 be treated as the old constant, but I hope to redefine AF_INET as "inet" some time this millenium :) > > -GAWollman > > -- > Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... > wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. > Opinions not those of| It is a bond more powerful than absence. We like people > MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant > From owner-freebsd-current Thu Dec 21 10:43:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA25425 for current-outgoing; Thu, 21 Dec 1995 10:43:44 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA25414 for ; Thu, 21 Dec 1995 10:43:37 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA27199; Thu, 21 Dec 1995 13:43:16 -0500 Date: Thu, 21 Dec 1995 13:43:16 -0500 From: "Garrett A. Wollman" Message-Id: <9512211843.AA27199@halloran-eldar.lcs.mit.edu> To: Julian Elischer Cc: wollman@lcs.mit.edu (Garrett A. Wollman), phk@critter.tfs.com, current@freebsd.org Subject: Re: MOUNT_* constants In-Reply-To: <199512211827.SAA07395@jhome.DIALix.COM> References: <9512211709.AA26246@halloran-eldar.lcs.mit.edu> <199512211827.SAA07395@jhome.DIALix.COM> Sender: owner-current@freebsd.org Precedence: bulk < said: > The other thing I want to make dynamic is > AF_INET and related constants... > I see no reason to not have a pointer to a string "inet" > for compatibility we can make pointers < 32 be treated as the old > constant, but I hope to redefine AF_INET as "inet" > some time this millenium :) Actually, there are a number of very strong reasons why you need to keep these constants relatively small, short, easy to compare, and valid arguments to a switch statement. The same is true of the filesystem indexes; what I have come close to getting rid of is /not/ the need for the constants themselves (which I believe will continue to exist), but rather, the static mapping from name to number implied in the MOUNT_* constants in . This is reasonable to do because mount and statfs requests are relatively infrequent. Calls to the socket functions, and the manipulation that is done internally of these numbers by the socket code, are so frequent that it does not make sense to do so. (We can't afford to take a speed hit in the networking code, it's too slow as it is!) -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Dec 21 10:55:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA26452 for current-outgoing; Thu, 21 Dec 1995 10:55:34 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA26445 Thu, 21 Dec 1995 10:55:30 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA03453; Thu, 21 Dec 1995 11:57:18 -0700 Date: Thu, 21 Dec 1995 11:57:18 -0700 From: Nate Williams Message-Id: <199512211857.LAA03453@rocky.sri.MT.net> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) Cc: current@freebsd.org, nate@freebsd.org Subject: Re: LD hits again :-( In-Reply-To: References: Sender: owner-current@freebsd.org Precedence: bulk > cc -O2 -m486 -fno-strength-reduce -L/usr/src/secure/usr.bin/bdes/../../lib/libcipher/obj -o bdes bdes.o -lcipher > bdes.o: WARNING! des_setkey(3) not present in the system! > bdes.o: WARNING! des_cipher(3) not present in the system! > > Note: shared libchipher exists in given -Lpath. This one has me baffled. I'm not even sure if it's something to do with the warning code being incorrectly called, or if indeed it's not linking in the correct libraries. I'm pretty sure it's the linker stating that warning (whether it needs to or not) and not an actual link bug. I verified this by adding warning symbols to the crypt.c in libcipher, and the linker now says. /usr/bin/ld -e start -dc -dp -o bdes /usr/lib/crt0.o -L../../lib/libcipher bdes.o -lcipher /usr/lib/libgcc.a -lc /usr/lib/libgcc.a ld: /usr/lib/libc.so.2.2: multiple definitions for warning symbol `_des_setkey' ld: /usr/lib/libc.so.2.2: multiple definitions for warning symbol `_des_cipher' bdes.o: WARNING! new des_setkey(3) is present in the system! bdes.o: WARNING! new des_cipher(3) is present in the system! For now, I'm going to ignore it. Although it is still a bug, I don't consider it a critical bug. Nate From owner-freebsd-current Thu Dec 21 10:58:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA26730 for current-outgoing; Thu, 21 Dec 1995 10:58:13 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA26723 for ; Thu, 21 Dec 1995 10:58:09 -0800 (PST) Received: (from julian@localhost) by jhome.DIALix.COM (8.7.3/8.7.3) id SAA14092; Thu, 21 Dec 1995 18:57:31 GMT From: Julian Elischer Message-Id: <199512211857.SAA14092@jhome.DIALix.COM> Subject: Re: MOUNT_* constants To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Thu, 21 Dec 1995 18:57:28 +0000 () Cc: wollman@lcs.mit.edu, phk@critter.tfs.com, current@freebsd.org In-Reply-To: <9512211843.AA27199@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Dec 21, 95 01:43:16 pm X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > > > > < said: > > > The other thing I want to make dynamic is > > AF_INET and related constants... > > I see no reason to not have a pointer to a string "inet" > > for compatibility we can make pointers < 32 be treated as the old > > constant, but I hope to redefine AF_INET as "inet" > > some time this millenium :) > > Actually, there are a number of very strong reasons why you need to > keep these constants relatively small, short, easy to compare, and > valid arguments to a switch statement. The same is true of the > filesystem indexes; what I have come close to getting rid of is /not/ > the need for the constants themselves (which I believe will continue > to exist), but rather, the static mapping from name to number implied > in the MOUNT_* constants in . There is the problem however of adding new protocols.. you need to add new constants in to socket.h which is a ROYAL PAIN in the neck. at TFS I have two protocols I add and I know there are other people who have proprietary protocols they add. Within the kernel, sure use an offsett if you want.. A compare of protocol names won't be much slower when looking for a protocols table however.. most string comparisons fail in the first 2 characters anyway.. this is not to be confused with the ETHERTYPE_INET type of constant that might be done at every packet.. I tend to have my AF_TFS value defined in a separate .h file from socket.h anyhow, so I don't have to modify that file.. > This is reasonable to do > because mount and statfs requests are relatively infrequent. Calls to > the socket functions, and the manipulation that is done internally of > these numbers by the socket code, are so frequent that it does not > make sense to do so. (We can't afford to take a speed hit in the > networking code, it's too slow as it is!) once you have openned a socket, then within the kernel, you can use some integer as an identifier, but I think the user interface should be more dynamic.. I think I got the idea from Mike Karels But I'm not sure.. > > -GAWollman From owner-freebsd-current Thu Dec 21 11:46:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA01532 for current-outgoing; Thu, 21 Dec 1995 11:46:13 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA01523 for ; Thu, 21 Dec 1995 11:46:09 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA22304 for current@freebsd.org; Thu, 21 Dec 1995 20:30:40 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id TAA04542 for ; Thu, 21 Dec 1995 19:47:00 +0100 (MET) Date: Thu, 21 Dec 1995 19:47:00 +0100 (MET) From: Andreas Klemm To: current@freebsd.org Subject: New sendmail sucks a bit ... (host map: lookup (wup.de): deferred) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi ! Have some problems with sendmail on -current. Even if I have a sendmail config file, that tells sendmail not to use dns lookup, it does... These are my two master configuration sendmail files: for uucp only, no dns lookup: divert(-1) include(`../m4/cf.m4') VERSIONID(`@(#)knobel.mc 1.1 (AKL) 10/08/95') OSTYPE(bsd4.4)dnl Dmknobel.gun.de define(`confDOMAIN_NAME', `$m')dnl define(`UUCP_MAX_SIZE', 2000000)dnl define(`SMART_HOST', `uucp-dom:easix')dnl define(`UUCP_RELAY', `uucp-dom:easix')dnl FEATURE(nodns)dnl FEATURE(use_cw_file) FEATURE(always_add_domain)dnl MAILER(local)dnl MAILER(smtp)dnl MAILER(uucp)dnl If I'm online via dialup ppp: divert(-1) include(`../m4/cf.m4') VERSIONID(`@(#)knobel-ip.mc 1.0 (Klemm) 9/16/95') OSTYPE(bsd4.4)dnl Dmknobel.gun.de define(`confDOMAIN_NAME', `$m')dnl FEATURE(nouucp) FEATURE(use_cw_file) FEATURE(always_add_domain)dnl MAILER(local) MAILER(smtp) a shellscript of mine internet on|off copies sendmail.UUCP.cf or sendmail.IP.cf to /etc/sendmail.cf depending on if I'm online or not. When I'm using the UUCP only sendmail.cf file, mails will be stuck in the mqueue, since host map lookup can't be resolved... knobel# mailq Mail Queue (2 requests) --Q-ID-- --Size-- -----Q-Time----- ------------Sender/Recipient------------ TAA04471 7 Thu Dec 21 19:38 andreas (host map: lookup (wup.de): deferred) andreas@wup.de TAA04487 5 Thu Dec 21 19:39 andreas (host map: lookup (wup.de): deferred) andreas@wup.de Only way out is to enable ppp, make internet connection and wait for sendmail to requeue... :( Any help ? Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Thu Dec 21 11:47:08 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA01626 for current-outgoing; Thu, 21 Dec 1995 11:47:08 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA01601 for ; Thu, 21 Dec 1995 11:47:01 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA22204; Thu, 21 Dec 1995 20:30:18 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id TAA04263; Thu, 21 Dec 1995 19:31:06 +0100 (MET) Date: Thu, 21 Dec 1995 19:31:06 +0100 (MET) From: Andreas Klemm To: Thomas Neumann cc: Nate Williams , current@freebsd.org Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) In-Reply-To: <877mzv5gwn.fsf@smart.ruhr.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk BTW: since I'm ruinning -current I don't get silo overflows any more. (I have a ASUS P55 board with the 16550 UARTS, or the compatible chip, to be more precise). The 1496EG+ modem is driven via hardware handshaking at 57600 Baud. So I'm really satisfied with current ;-) -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Thu Dec 21 11:47:25 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA01694 for current-outgoing; Thu, 21 Dec 1995 11:47:25 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA01681 for ; Thu, 21 Dec 1995 11:47:21 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA22301; Thu, 21 Dec 1995 20:30:35 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id HAA00609; Thu, 21 Dec 1995 07:26:00 +0100 (MET) Date: Thu, 21 Dec 1995 07:26:00 +0100 (MET) From: Andreas Klemm To: Thomas Graichen cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512191711.SAA02380@mordillo> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Tue, 19 Dec 1995, Thomas Graichen wrote: > > > > Is freely redistributable software, right? At least that's what the > > man page says, anyway.. I'm wondering if this isn't something that > > *should* move out of ports and into the main tree? It currently represents > > something of an imperfect match, at best, as simply reading the man page > > or doing the two-step configuration process for it will readily attest. > > > > Jordan > ... did you set up a NetBSD machine ? :-) (first the ypset man-page > from NetBSD and now pcnfsd which is also part of NetBSD ...) I'd say yes to integrate this service, because it's a basic connectivity service. In this case a very small package, that doesn't cost many K's in the source tree. If you do so, I'd recommend to add a sample /etc/rpc.pcnfsd file into /etc. You can find some examples in the manpage of pcnfsd. One should set a sample uid-range and perhaps an example of sharing the default lineprinter lp. andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Thu Dec 21 11:48:00 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA01791 for current-outgoing; Thu, 21 Dec 1995 11:48:00 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA01771 for ; Thu, 21 Dec 1995 11:47:54 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA22227; Thu, 21 Dec 1995 20:30:22 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id TAA04235; Thu, 21 Dec 1995 19:28:44 +0100 (MET) Date: Thu, 21 Dec 1995 19:28:44 +0100 (MET) From: Andreas Klemm To: Thomas Neumann cc: Nate Williams , current@freebsd.org Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) In-Reply-To: <877mzv5gwn.fsf@smart.ruhr.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On 18 Dec 1995, Thomas Neumann wrote: > Folks, don't you think that this "discussion" is gaining a > dangerous amount of emotional momentum - lets try to keep > it 'professional' instead of 'personal'. Well on the way ;-) > Personally, I'm experiencing relatively few problems with -current. True. I installed current two days ago and must say, that it's running fine so far with only few exceptions. Let me tell you the experiences I made. Base system was FreeBSD-stable 2.1. I supped the -current of 19.12.95 - make world: stopped when compiling ypserv. rpcgen (2.1 version) didn't understand the new commandline flags of the -current version. So I commented out ypserv. I build it later. - the top utility can't be compiled. There is a machine dependend file for FreeBSD-2.2 missing. A top version compiled on 2.1 dies with a core dump. Possibly other utilities might be affected by this, too. Things in 2.2 seems to have changed. Would be nice, if there would be a list of changes in /usr/src, so that it's clear, where to dig around, if something doesn't compile or run. - problems with du when being in roots home dir it dies in the middle: root# du 1 ./.tin/.news 1 ./.tin/.save 1 ./.tin/.mail 15 ./.tin 1 ./Mail/inbox 1 ./Mail/drafts 3 ./Mail 1 ./News 1 ./.elm 2 ./.tkined 3 ./.nn du: fts_read: No such file or directory - rtin I configured rtin to look into /etc/nntpserver to get the name of the nntp server. My old 2.1 binary shows the following mis- behaviour: connecting /etc/nntpserver /etc/nntpserver: unknown host it's the new beta of tin. Worked under 2.1. - screensaver: on startup the following error message: undefined entry symbol '_saver_init' ld: Spurious undefined symbols: # undefined symbols 1, reposted 0 My sysconfig configuration: blanktime=600 saver=green - strange sendmail messages on startup, when there are still mails in the mailqueue waiting for the nameserver ... (waiting to be sent via smtp). But when I run off the net... Dec 21 06:46:41 knobel sendmail[190]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): erro r on output channel sending "451 before main() initmaps: fd 1 not open: Bad file descriptor": Input/output error Dec 21 06:46:41 knobel sendmail[190]: NOQUEUE: SYSERR(root): before main() initm aps: fd 1 not open: Bad file descriptor Dec 21 06:46:41 knobel sendmail[190]: NOQUEUE: SYSERR(root): before main() initm aps: fd 2 not open: Bad file descriptor FreeBSD-current runs stable so far. No crashes. Ok, I have fine std hardware.... I think I can live with current. Would be fine, if some of the above mentioned things could be fixed. And concerning the history of important changes ... This should be a must. Puh, just had problems with my freshly compiled pine... malloc warning: free(): already free chunk I'm currently in X11, fired up pine in an xterm. Loaded the 900 messages long -current mailinglist folder. Edited this reply. Edited a 20MB large messages file with vi in parallel. Truncated it to 1M length. When I wanted to send the message I got /var filesystem full message, first. Deceided to save the 1 MB messages file and to leave vi. Checked space in /var. Then I got the free(): message... Since then cursor positioning in vi wasn't ok. Wrote the file to /tmp/xxx (/tmp is a 90M large memory filesystem). And wrote it to /tmp/yyy. When I entered pine this time, I wanted to include /tmp/xxx as my reply. The file was empty (surprise, surprise). /tmp/yyy was ok, puh... ;-) I think I'm surely the one and only who got this result ;-)) If there are any questions ... ?! Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Thu Dec 21 11:48:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA02021 for current-outgoing; Thu, 21 Dec 1995 11:48:30 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA01988 for ; Thu, 21 Dec 1995 11:48:25 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA22300; Thu, 21 Dec 1995 20:30:33 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id HAA00636; Thu, 21 Dec 1995 07:34:56 +0100 (MET) Date: Thu, 21 Dec 1995 07:34:56 +0100 (MET) From: Andreas Klemm To: Michael Smith cc: Nate Williams , jkh@time.cdrom.com, current@freefall.freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512192252.JAA10809@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Wed, 20 Dec 1995, Michael Smith wrote: > Nate Williams stands accused of saying: > > > > > Is freely redistributable software, right? At least that's what the > > > man page says, anyway.. I'm wondering if this isn't something that > > > *should* move out of ports and into the main tree? > > > > How useful is it for the general user of FreeBSD? > > > > (I'd say a *very* small percentage of users actually have use for it) > > If it moves, so does samba and that DHCP daemon that I keep hearing about 8) > I'd say that they get an awful lot more use than pcnfsd. (Or would if > people knew about them 8) Well, I'd recommend to let the samba code in the ports area, since it's changing very rapidly. People wouldn't want to use the "old" samba in the FreeBSD-RELEASE. I assume, they would want to have the newest one... Perhaps we should discuss that at a later time, when samba has reached a 'not rapidly changing' state (as pcnfsd for example). Generally I'd vote for it. But maybe not now. -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Thu Dec 21 11:52:51 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA02780 for current-outgoing; Thu, 21 Dec 1995 11:52:51 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA02772 for ; Thu, 21 Dec 1995 11:52:46 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id LAA01796 for ; Thu, 21 Dec 1995 11:52:44 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA01616; Fri, 22 Dec 1995 06:48:12 +1100 Date: Fri, 22 Dec 1995 06:48:12 +1100 From: Bruce Evans Message-Id: <199512211948.GAA01616@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.tfs.com Subject: Re: conf.c and USL copyright at top Cc: current@FreeBSD.org, jkh@freefall.freebsd.org, jkh@time.cdrom.com Sender: owner-current@FreeBSD.org Precedence: bulk >> >> tty_conf.c is more interesting. It could be handled more dynamically >> >> like conf.c. There isn't as much to gain because the analogue of the >> >> major numbers -- the line discipline numbers -- can't be avoided because >> >> there is no by-name user interface. >> >> >Well, we solved the same thing in VFS with a linker-set... >> >> Linker sets can't be used to sove problems related to magic numbers in >> the user interface. >Filesystems have a magic number as well. And this doesn't work. Try `find / -o -fstype msdos'. Fixed in 4.4lite2 by using getvfsbyname() more. >What I meant was that we could register the line-disciplines along the >lines we register VFS's. And change the user interface...? Bruce From owner-freebsd-current Thu Dec 21 11:53:01 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA02805 for current-outgoing; Thu, 21 Dec 1995 11:53:01 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA02737 for ; Thu, 21 Dec 1995 11:52:29 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA22299; Thu, 21 Dec 1995 20:30:31 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id HAA00670; Thu, 21 Dec 1995 07:47:00 +0100 (MET) Date: Thu, 21 Dec 1995 07:47:00 +0100 (MET) From: Andreas Klemm To: Paul Richards cc: "Jordan K. Hubbard" , asami@cs.berkeley.edu, current@freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <199512201225.MAA23325@cadair.elsevier.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Wed, 20 Dec 1995, Paul Richards wrote: > In reply to Jordan K. Hubbard who said > > > > It makes enabling it in /etc/sysconfig a one step operation. I can > > live with it being a two-stepper, but I can't always count on access > > to the package collection.. :-( > > > > It's not a good idea to try and have evey possible package that people > might want to use configured from /etc/sysconfig. I think, too, it might be too large. Then you create nearly such a monster like Windows win.ini, you know that ? ;-) Ok, sysconfig is very very better documented ! But too large is perhaps a bad idea. > I'm not happy about > apache being started from /etc/rc for example. This just isn't the > way things should be. The "system" startup configuration should only > deal with the core functionality that every unix box needs to run. > Stuff that only particular sites would use should use some other mechanism. I like the SYSVR4 mechanism of having a generic /etc/init.d and /etc/rc1.d /etc/rc2.d ... You know that ??? Then you could relatively easy add start an kill scripts into init.d via a port configure script. This script will be linked into the suitable runlevel directory as a start or kill script ... What about a hack in /etc/rc.local, to look into a /etc/addon-services directory, where script files reside to start additional services ? rc.local: if [ -d /etc/addon-services ]; then cd /etc/addon-services for i in * do /bin/sh $i done fi /etc/addon-services/inn /etc/addon-services/apache /etc/addon-services/... Or something similar. Then you would'n need to poke around in a file like /etc/rc.local. You could very simple add a script into that directory ... > If you want to make it easy to configure pcnfsd then all you do is add > a default startup file to the package and when you run pkg_add it just > appears on the next reboot as though it was part of the system. Well, it would really be a good idea, that the packages would be reworked to install really smart ... This means, that system files like /etc/services or /etc/inetd.conf are updated by an postinstallation script, so that the package is really ready to work ! -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Thu Dec 21 12:11:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA04730 for current-outgoing; Thu, 21 Dec 1995 12:11:48 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA04716 for ; Thu, 21 Dec 1995 12:11:39 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA02300; Fri, 22 Dec 1995 07:07:02 +1100 Date: Fri, 22 Dec 1995 07:07:02 +1100 From: Bruce Evans Message-Id: <199512212007.HAA02300@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: disklabel -r -w rz2 rzxx Sender: owner-current@FreeBSD.ORG Precedence: bulk >> It already does. The known parameters are available for the whole >> drive and can easily be used for dangerously dedicated drives, e.g., >> >> disklabel /dev/rsd0 | >> sed -e 's/^rpm: 0$/rpm: 3600/' -e 's/^interleave: 0$/interleave: 1/' | >> disklabel -R -r /dev/rsd0 /dev/stdin >> >> Here the sed commands substitute some of the unknown values with >> possibly-bogus but working values. >Hmm, interesting. For which devices? All those whose size can be determined automatically: wd (except for old drives), sd, vn. >Short of a real empty disk to test with, i've only been playing with >vn devices :), and all i've got was: >Dec 21 00:19:43 uriah /kernel: vn0: invalid primary partition table: no magic >... This is normal. It might be necessary to start with a clean MBR with no magic. I created a vn file by dd'ing from /dev/zero so it was very clean. >(I would have played with floppies, too, but i realized that they are >not even supposed to work. Though it's probably not a big deal to >make them work.) We never committed the support for them. I tested with floppies here. Bruce From owner-freebsd-current Thu Dec 21 12:38:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA07211 for current-outgoing; Thu, 21 Dec 1995 12:38:30 -0800 (PST) Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA07206 for ; Thu, 21 Dec 1995 12:38:27 -0800 (PST) Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.6.12/8.6.9) with ESMTP id MAA00467 for ; Thu, 21 Dec 1995 12:38:23 -0800 Message-Id: <199512212038.MAA00467@pain.csrv.uidaho.edu> To: current@freebsd.org Subject: another m_copydata crash MIME-Version: 1.0 Content-Type: text/plain; charset="x-unknown" Content-ID: <461.819578301.1@pain.csrv.uidaho.edu> Content-Transfer-Encoding: quoted-printable Date: Thu, 21 Dec 1995 12:38:22 -0800 From: Faried Nawaz Sender: owner-current@freebsd.org Precedence: bulk i had > 3 crashes today, but /var/crash (actually /usr/crash) filled up so i only got the first dump. Script started on Thu Dec 21 12:35:25 1995 ; gdb -k -q (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.20 (kgdb) core-file /var/crash/vmcore.20 IdlePTD 1a2000 current pcb at 1937fc panic: m_copydata #0 boot (howto=3D256) at ../../i386/i386/machdep.c:913 913 savectx(&dumppcb, 0); (kgdb) where #0 boot (howto=3D256) at ../../i386/i386/machdep.c:913 #1 0xf010fbc3 in panic (fmt=3D0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 #2 0xf0118751 in m_copydata (m=3D0x0, off=3D-1, len=3D1, cp=3D0xf082a0e8 = "") at ../../kern/uipc_mbuf.c:371 #3 0xf013b9b5 in tcp_output (tp=3D0xf06cba00) at ../../netinet/tcp_output= .c:476 #4 0xf013ac4a in tcp_input (m=3D0xf082f280, iphlen=3D20) at ../../netinet/tcp_input.c:1629 #5 0xf0135b69 in ipintr () at ../../netinet/ip_input.c:464 #6 0xf0159ffd in swi_net_next () #7 0xf015f0d8 in cpu_switch () (kgdb) up #1 0xf010fbc3 in panic (fmt=3D0xf0118724 "m_copydata") at ../../kern/subr_prf.c:124 124 boot(bootopt); (kgdb) up #2 0xf0118751 in m_copydata (m=3D0x0, off=3D-1, len=3D1, cp=3D0xf082a0e8 = "") at ../../kern/uipc_mbuf.c:371 371 panic("m_copydata"); (kgdb) up #3 0xf013b9b5 in tcp_output (tp=3D0xf06cba00) at ../../netinet/tcp_output= .c:476 476 m_copydata(so->so_snd.sb_mb, off, (int) len, (kgdb) print *tp $1 =3D {seg_next =3D 0xf082f2ac, seg_prev =3D 0xf082f2ac, t_state =3D 4, t= _timer =3D {0, = 0, 14400, 0}, t_rxtshift =3D 0, t_rxtcur =3D 128, t_dupacks =3D 0, = t_maxseg =3D 492, t_maxopd =3D 512, t_force =3D 0, t_flags =3D 25057, = t_template =3D 0xf081b414, t_inpcb =3D 0xf076d700, snd_una =3D 406370359= 4, = snd_nxt =3D 4063703593, snd_up =3D 4063703593, snd_wl1 =3D 1720394763, = snd_wl2 =3D 4063703594, iss =3D 4063703593, snd_wnd =3D 16728, rcv_wnd =3D= 16728, = rcv_nxt =3D 1720394754, rcv_up =3D 1720394754, irs =3D 1720394753, = rcv_adv =3D 1720411482, snd_max =3D 4063703594, snd_cwnd =3D 492, = snd_ssthresh =3D 984, t_idle =3D 0, t_rtt =3D 0, t_rtseq =3D 4063703593,= = t_srtt =3D 480, t_rttvar =3D 120, t_rttmin =3D 2, max_sndwnd =3D 16728, = t_oobflags =3D 0 '\000', t_iobc =3D 0 '\000', t_softerror =3D 0, = snd_scale =3D 0 '\000', rcv_scale =3D 0 '\000', request_r_scale =3D 0 '\= 000', = requested_s_scale =3D 0 '\000', ts_recent =3D 2539439, ts_recent_age =3D= 309962, = last_ack_sent =3D 1720394754, cc_send =3D 4064, cc_recv =3D 37581, = t_duration =3D 58, t_tuba_pcb =3D 0x0, t_rttupdated =3D 1} (kgdb) up #4 0xf013ac4a in tcp_input (m=3D0xf082f280, iphlen=3D20) at ../../netinet/tcp_input.c:1629 1629 (void) tcp_output(tp); (kgdb) print *m $2 =3D {m_hdr =3D {mh_next =3D 0x0, mh_nextpkt =3D 0x0, mh_len =3D 0, = mh_data =3D 0xf082f2e8 "", mh_type =3D 1, mh_flags =3D 2}, M_dat =3D {= MH =3D { MH_pkthdr =3D {len =3D 60, rcvif =3D 0xf0193c7c}, MH_dat =3D {MH_ext= =3D { ext_buf =3D 0x4000e898
, = ext_free =3D 0x48782d33, ext_size =3D 17563648}, = MH_databuf =3D "\230=E8\000@3-xH\000\000\f\001\022\b\b\000\000=BAl= =F0\000=BAl=F0\000\006\000\000=CD\213\001r\201erm\200=F2\202=F0\013$\213f*= 27=F2=A0\021XA\000\000\000\000\001\001\b\n\000&=BF=EB\000\004=BA=CA\001\00= 1\013\006\000\000\222=CD\000\000\000\000\000\000\000\000\001", '\000' }}, = M_databuf =3D "<\000\000\000|<\031=F0\230=E8\000@3-xH\000\000\f\001\02= 2\b\b\000\000=BAl=F0\000=BAl=F0\000\006\000\000=CD\213\001r\201erm\200=F2\= 202=F0\013$\213f*27=F2=A0\021XA\000\000\000\000\001\001\b\n\000&=BF=EB\000= \004=BA=CA\001\001\013\006\000\000\222=CD\000\000\000\000\000\000\000\000\= 001", '\000' }} (kgdb) print *ti $3 =3D {ti_i =3D {ih_next =3D 0xf06cba00 "=AC=F2\202=F0=AC=F2\202=F0\004",= = ih_prev =3D 0xf06cba00 "=AC=F2\202=F0=AC=F2\202=F0\004", ih_x1 =3D 0 '= \000', = ih_pr =3D 6 '\006', ih_len =3D 0, ih_src =3D {s_addr =3D 1912703949}, = ih_dst =3D { s_addr =3D 1836213633}}, ti_t =3D {th_sport =3D 62080, th_dport =3D = 61570, = th_seq =3D 1720394763, th_ack =3D 4063703594, th_x2 =3D 0 '\000', = th_off =3D 10 '\n', th_flags =3D 17 '\021', th_win =3D 16728, th_sum =3D= 0, = th_urp =3D 0}} (kgdb) up #5 0xf0135b69 in ipintr () at ../../netinet/ip_input.c:464 464 goto next; (kgdb) quit ; exit Script done on Thu Dec 21 12:36:41 1995 From owner-freebsd-current Thu Dec 21 12:52:09 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA08010 for current-outgoing; Thu, 21 Dec 1995 12:52:09 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA07999 for ; Thu, 21 Dec 1995 12:52:03 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id UAA11057 for ; Thu, 21 Dec 1995 20:50:16 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Thu, 21 Dec 1995 20:50:48 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id UAA11834; Thu, 21 Dec 1995 20:50:45 GMT From: Paul Richards Message-Id: <199512212050.UAA11834@cadair.elsevier.co.uk> Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) To: andreas@knobel.gun.de (Andreas Klemm) Date: Thu, 21 Dec 1995 20:50:44 +0000 (GMT) Cc: tom@smart.ruhr.de, nate@rocky.sri.MT.net, current@FreeBSD.org In-Reply-To: from "Andreas Klemm" at Dec 21, 95 07:28:44 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Andreas Klemm who said > > I'm currently in X11, fired up pine in an xterm. Loaded the > 900 messages long -current mailinglist folder. Edited this reply. > Edited a 20MB large messages file with vi in parallel. Truncated it > to 1M length. When I wanted to send the message I got /var filesystem > full message, first. Deceided to save the 1 MB messages file and to > leave vi. Checked space in /var. Then I got the free(): message... > > Since then cursor positioning in vi wasn't ok. Wrote the file to /tmp/xxx > (/tmp is a 90M large memory filesystem). And wrote it to /tmp/yyy. > When I entered pine this time, I wanted to include /tmp/xxx as my > reply. The file was empty (surprise, surprise). /tmp/yyy was ok, > puh... ;-) > > I think I'm surely the one and only who got this result ;-)) I'm not quite sure what the chain of events here was but it looks like something that's bitten me a few times and I really don't like the way this works. If you try and write a file to a nearly full filesystem and that write fails because the filesytem fills up, the file gets truncated. This is a very nasty thing to happen. I'm not sure what the actual course of events are but I'd really like to find some way of preventing it from happening. I'd be satisfied if I just ended up with part of the file but losing the whole thing can be really annoying if it's a chapter of your thesis, which is what once happened to me. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Thu Dec 21 13:04:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA08945 for current-outgoing; Thu, 21 Dec 1995 13:04:46 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA08935 for ; Thu, 21 Dec 1995 13:04:37 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA03866; Thu, 21 Dec 1995 14:05:39 -0700 Date: Thu, 21 Dec 1995 14:05:39 -0700 From: Nate Williams Message-Id: <199512212105.OAA03866@rocky.sri.MT.net> To: Paul Richards Cc: current@FreeBSD.org Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) In-Reply-To: <199512212050.UAA11834@cadair.elsevier.co.uk> References: <199512212050.UAA11834@cadair.elsevier.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk Paul Richards writes: > If you try and write a file to a nearly full filesystem and that write > fails because the filesytem fills up, the file gets truncated. This is > a very nasty thing to happen. I'm not sure what the actual course of > events are but I'd really like to find some way of preventing it from > happening. I'd be satisfied if I just ended up with part of the file but > losing the whole thing can be really annoying if it's a chapter of your > thesis, which is what once happened to me. This has been the way FreeBSD has worked since day one, and although I believe it would be nice to see this changed, unless someone wants to get down and dirty with the kernel to see how it can be fixed it's not gonna get fixed. :( Nate From owner-freebsd-current Thu Dec 21 13:07:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09156 for current-outgoing; Thu, 21 Dec 1995 13:07:45 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA09144 for ; Thu, 21 Dec 1995 13:07:40 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id VAA11087 for ; Thu, 21 Dec 1995 21:05:58 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Thu, 21 Dec 1995 21:06:29 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id VAA11901; Thu, 21 Dec 1995 21:06:09 GMT From: Paul Richards Message-Id: <199512212106.VAA11901@cadair.elsevier.co.uk> Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) To: nate@rocky.sri.MT.net (Nate Williams) Date: Thu, 21 Dec 1995 21:06:09 +0000 (GMT) Cc: current@FreeBSD.org In-Reply-To: <199512212105.OAA03866@rocky.sri.MT.net> from "Nate Williams" at Dec 21, 95 02:05:39 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Nate Williams who said > > This has been the way FreeBSD has worked since day one, and although I yeah I know but I'm still interested in why this happens. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Thu Dec 21 13:36:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA11602 for current-outgoing; Thu, 21 Dec 1995 13:36:26 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA11593 for ; Thu, 21 Dec 1995 13:36:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id NAA29656; Thu, 21 Dec 1995 13:32:30 -0800 To: Andreas Klemm cc: Thomas Graichen , current@freebsd.org Subject: Re: pcnfsd.. In-reply-to: Your message of "Thu, 21 Dec 1995 07:26:00 +0100." Date: Thu, 21 Dec 1995 13:32:30 -0800 Message-ID: <29652.819581550@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > I'd say yes to integrate this service, because it's a basic > connectivity service. In this case a very small package, that > doesn't cost many K's in the source tree. Actually, I have a confession to make. Ahem. This is very difficult. I have come to (ooph, ack) agree with Paul! I think that the ${local_startup} trick has potential and it should be the package that drops its startup glue there. sysinstall should just do a pkg_add on pcnfsd and expect the right side-effects to happen (likewise with pkg_delete - you'd want to remove the initialization!). Of course, version-smash will still be a constant headache to be lived with, but I expect that the packagers will simply have to sort that out for themselves as they go along. I think the package specific junk should come out of sysconfig and the other associated files in /etc. The current approach is simply a bad idea and I'm sorry that I ever defended it. It's a great mechanism for configuring the *base system* behavior, but no more than that. The local config stuff is fat. I'll go turn over the appropriate files in -current with a stick. Jordan From owner-freebsd-current Thu Dec 21 13:43:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA12136 for current-outgoing; Thu, 21 Dec 1995 13:43:02 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA12129 for ; Thu, 21 Dec 1995 13:42:55 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA29747; Thu, 21 Dec 1995 16:42:40 -0500 Date: Thu, 21 Dec 1995 16:42:40 -0500 From: "Garrett A. Wollman" Message-Id: <9512212142.AA29747@halloran-eldar.lcs.mit.edu> To: Julian Elischer Cc: wollman@lcs.mit.edu (Garrett A. Wollman), phk@critter.tfs.com, current@FreeBSD.org Subject: Re: MOUNT_* constants In-Reply-To: <199512211857.SAA14092@jhome.DIALix.COM> References: <9512211843.AA27199@halloran-eldar.lcs.mit.edu> <199512211857.SAA14092@jhome.DIALix.COM> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > you want.. A compare of protocol names won't be much slower > when looking for a protocols table however.. You can't fit a protocol name in a `struct sockaddr'. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Dec 21 14:18:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA15151 for current-outgoing; Thu, 21 Dec 1995 14:18:05 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA15142 for ; Thu, 21 Dec 1995 14:18:00 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA04267; Thu, 21 Dec 1995 15:20:19 -0700 Date: Thu, 21 Dec 1995 15:20:19 -0700 From: Nate Williams Message-Id: <199512212220.PAA04267@rocky.sri.MT.net> To: "Jordan K. Hubbard" Cc: Andreas Klemm , Thomas Graichen , current@freebsd.org Subject: Re: pcnfsd.. In-Reply-To: <29652.819581550@time.cdrom.com> References: <29652.819581550@time.cdrom.com> Sender: owner-current@freebsd.org Precedence: bulk > > I'd say yes to integrate this service, because it's a basic > > connectivity service. In this case a very small package, that > > doesn't cost many K's in the source tree. > > Actually, I have a confession to make. Ahem. This is very difficult. > I have come to (ooph, ack) agree with Paul! I think that the > ${local_startup} trick has potential and it should be the package that > drops its startup glue there. ... > I think the package specific junk should come out of sysconfig and the > other associated files in /etc. The current approach is simply a bad > idea and I'm sorry that I ever defended it. It's a great mechanism > for configuring the *base system* behavior, but no more than that. > The local config stuff is fat. Yay! We've come to an agreement. It *must* be the holidays or something. Nate From owner-freebsd-current Thu Dec 21 14:41:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA17359 for current-outgoing; Thu, 21 Dec 1995 14:41:16 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA17354 for ; Thu, 21 Dec 1995 14:41:10 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA01699 ; Thu, 21 Dec 1995 23:40:50 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA29050 ; Thu, 21 Dec 1995 23:40:50 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id XAA00264; Thu, 21 Dec 1995 23:40:37 +0100 (MET) From: Ollivier Robert Message-Id: <199512212240.XAA00264@keltia.freenix.fr> Subject: Re: Mouse not working for two days To: bde@zeta.org.au (Bruce Evans) Date: Thu, 21 Dec 1995 23:40:37 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) In-Reply-To: <199512180051.LAA27345@godzilla.zeta.org.au> from "Bruce Evans" at Dec 18, 95 11:51:05 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1449 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk It seems that Bruce Evans said: > Try the following change. It keeps the FIFO enabled and fixes a > bitrotted name and comment. > > Bruce It works fine, thanks Bruce ! -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Dec 18 00:50:47 MET 1995 From owner-freebsd-current Thu Dec 21 14:52:59 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA18114 for current-outgoing; Thu, 21 Dec 1995 14:52:59 -0800 (PST) Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA18108 for ; Thu, 21 Dec 1995 14:52:53 -0800 (PST) Received: (from root@localhost) by sbstark.cs.sunysb.edu (8.6.12/8.6.9) with UUCP id RAA03693 for current@freebsd.org; Thu, 21 Dec 1995 17:52:28 -0500 Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.6.11/8.6.9) id IAA27582; Thu, 21 Dec 1995 08:01:12 -0500 Date: Thu, 21 Dec 1995 08:01:12 -0500 From: Gene Stark Message-Id: <199512211301.IAA27582@starkhome.cs.sunysb.edu> To: fw.ast.com!uhclem%nemesis@sbstark.cs.sunysb.edu (Frank Durda IV) Cc: current@freebsd.org In-reply-to: fw.ast.com!uhclem%nemesis@sbstark.cs.sunysb.edu's message of Wed, 20 Dec 95 11:59 WET Subject: Re: conf.c and USL copyright at top References: <4ba07r$opl@starkhome.cs.sunysb.edu> Sender: owner-current@freebsd.org Precedence: bulk >According to the lawyers at two major corporations I have worked at, >if you have changed more than 12% of the functional code, it's yours. >(Changing variable names and comments don't count.) "It's yours" just means you can add your own copyright to it, not delete the original one, right? I have trouble believing that simply by changing 12% of something, you erase its status as a "derived work" and then can delete the original copyright. - Gene Stark From owner-freebsd-current Thu Dec 21 14:57:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA18424 for current-outgoing; Thu, 21 Dec 1995 14:57:36 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA18419 for ; Thu, 21 Dec 1995 14:57:32 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tStsj-0000zcC; Thu, 21 Dec 95 16:54 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tStkJ-000Cn2C; Thu, 21 Dec 95 16:45 WET Message-Id: Date: Thu, 21 Dec 95 16:45 WET To: current@freebsd.org, gene@starkhome.cs.sunysb.edu From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Thu Dec 21 1995, 16:45:55 CST Subject: Re: conf.c and USL copyright at top Sender: owner-current@freebsd.org Precedence: bulk [1]According to the lawyers at two major corporations I have worked at, [1]if you have changed more than 12% of the functional code, it's yours. [1](Changing variable names and comments don't count.) [2]Gene Stark writes: [2]"It's yours" just means you can add your own copyright to it, [2]not delete the original one, right? In 99% of the instances where this took place that I am aware of (twenty or thirty), the original copyright or authorship was not mentioned in the derived work. There was no payment or license to the original person or company either. Then they filed new copyrights that were accepted (there aren't any checks worth mentioning on infringing copyrights). In one case, the derived work did mention the original source simply for marketing reasons, ie "based on the best-selling works of %s", that sort of thing. More specific as "100% compatible with" or "just as fast as". I've even seen some of my own work end up in a product of another vendor, covered by only a few hundred bytes of "extensions". [2]I have trouble believing that simply by changing 12% of something, [2]you erase its status as a "derived work" and then can delete the [2]original copyright. Again, I am not a lawyer but I do know that the known laws of physics seem to go on hold when the legal system is involved. So what seems obvious, fair or makes sense has no place in how it really works. Look at some of software patents that have been granted if you want your sanity really tested. Circular queues and ring buffers were patented in 1982! I guess nobody every used them before then - just ignore those samples in Knuth that date back into the 70s. Please see the USC or a lawyer familiar with copyright and patent law for information on this subject. Oh, and be sure to insert quarters before you try to start it. If you discover the 12% rule is obsolete or doesn't apply, I'd like to know. Frank Durda IV |"Everything you know is wrong." or uhclem%nemesis@fw.ast.com (Fastest Route)| - Firesign Theatre ...letni!rwsys!nemesis!uhclem |Why do I quote these guys on all ...decvax!fw.ast.com!nemesis!uhclem |legal topics? From owner-freebsd-current Thu Dec 21 15:33:01 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA20949 for current-outgoing; Thu, 21 Dec 1995 15:33:01 -0800 (PST) Received: from dworshak.cs.uidaho.edu (root@dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA20944 for ; Thu, 21 Dec 1995 15:32:57 -0800 (PST) Received: from hoodoo.cs.uidaho.edu (hoodoo.cs.uidaho.edu [129.101.100.34]) by dworshak.cs.uidaho.edu (8.6.12/1.1) with ESMTP id PAA09797; Thu, 21 Dec 1995 15:32:54 -0800 Received: from localhost (localhost [127.0.0.1]) by hoodoo.cs.uidaho.edu (8.6.10/1.0) with SMTP id PAA13403; Thu, 21 Dec 1995 15:29:18 -0800 Message-Id: <199512212329.PAA13403@hoodoo.cs.uidaho.edu> X-Authentication-Warning: hoodoo.cs.uidaho.edu: Host localhost didn't use HELO protocol To: Andreas Klemm cc: current@freebsd.org Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) In-reply-to: Your message of "Thu, 21 Dec 1995 19:28:44 PST." Date: Thu, 21 Dec 1995 15:29:17 PST From: faried nawaz Sender: owner-current@freebsd.org Precedence: bulk Andreas Klemm wrote... - the top utility can't be compiled. There is a machine dependend file for FreeBSD-2.2 missing. A top version compiled on 2.1 dies with a core dump. Possibly other utilities might be affected by this, too. Things in 2.2 seems to have changed. Would be nice, if there would be a list of changes in /usr/src, so that it's clear, where to dig around, if something doesn't compile or run. you need to add #include to one of the files. i've mailed the port-owner. - screensaver: on startup the following error message: undefined entry symbol '_saver_init' ld: Spurious undefined symbols: # undefined symbols 1, reposted 0 your rc.i386 is outdated, i think. use /usr/src/etc/etc.i386/rc.i386. From owner-freebsd-current Thu Dec 21 15:49:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21593 for current-outgoing; Thu, 21 Dec 1995 15:49:03 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA21581 Thu, 21 Dec 1995 15:48:51 -0800 (PST) Received: by sovcom.kiae.su id AA21427 (5.65.kiae-1 ); Fri, 22 Dec 1995 02:41:31 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Fri, 22 Dec 95 02:41:31 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id CAA00442; Fri, 22 Dec 1995 02:20:44 +0300 (MSK) To: Nate Williams Cc: current@freebsd.org, nate@freebsd.org References: <199512211829.LAA03382@rocky.sri.MT.net> In-Reply-To: <199512211829.LAA03382@rocky.sri.MT.net>; from Nate Williams at Thu, 21 Dec 1995 11:29:07 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Fri, 22 Dec 1995 02:20:44 +0300 (MSK) X-Mailer: Mail/@ [v2.41 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: LD hits again :-( Lines: 22 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message <199512211829.LAA03382@rocky.sri.MT.net> Nate Williams writes: >> cc -O2 -m486 -fno-strength-reduce -L/usr/src/secure/usr.bin/bdes/../../lib/libcipher/obj -o bdes bdes.o -lcipher >> bdes.o: WARNING! des_setkey(3) not present in the system! >> bdes.o: WARNING! des_cipher(3) not present in the system! >> >> Note: shared libchipher exists in given -Lpath. ^^^^^^^ >I've seen this, but I don't know why this is being printed. It's >certainly not a function of the linker. Ahh, I see. It's picking up >the versions in libc rather than the static versions in ^^^^^^ NO!!!! SHARED VERSION! >lib/libcipher/obj/libcipher.a. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Dec 21 15:50:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21668 for current-outgoing; Thu, 21 Dec 1995 15:50:05 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA21632 Thu, 21 Dec 1995 15:49:48 -0800 (PST) Received: by sovcom.kiae.su id AA21445 (5.65.kiae-1 ); Fri, 22 Dec 1995 02:41:39 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Fri, 22 Dec 95 02:41:39 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id CAA00449; Fri, 22 Dec 1995 02:23:30 +0300 (MSK) To: Nate Williams Cc: current@freebsd.org, nate@freebsd.org References: <199512211857.LAA03453@rocky.sri.MT.net> In-Reply-To: <199512211857.LAA03453@rocky.sri.MT.net>; from Nate Williams at Thu, 21 Dec 1995 11:57:18 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Fri, 22 Dec 1995 02:23:30 +0300 (MSK) X-Mailer: Mail/@ [v2.41 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: LD hits again :-( Lines: 27 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message <199512211857.LAA03453@rocky.sri.MT.net> Nate Williams writes: >I'm pretty sure it's the linker stating that warning (whether it needs >to or not) and not an actual link bug. I verified this by adding >warning symbols to the crypt.c in libcipher, and the linker now says. >/usr/bin/ld -e start -dc -dp -o bdes /usr/lib/crt0.o -L../../lib/libcipher bdes.o -lcipher /usr/lib/libgcc.a -lc /usr/lib/libgcc.a ^^^^^^^^^^^^^^^^^^^^ Your linker path is wrong, here you need to update Makefile to -current >ld: /usr/lib/libc.so.2.2: multiple definitions for warning symbol `_des_setkey' >ld: /usr/lib/libc.so.2.2: multiple definitions for warning symbol `_des_cipher' >bdes.o: WARNING! new des_setkey(3) is present in the system! >bdes.o: WARNING! new des_cipher(3) is present in the system! >For now, I'm going to ignore it. Although it is still a bug, I don't >consider it a critical bug. Secure is always critical. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Dec 21 15:54:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21809 for current-outgoing; Thu, 21 Dec 1995 15:54:21 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA21804 Thu, 21 Dec 1995 15:54:13 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA04638; Thu, 21 Dec 1995 16:56:26 -0700 Date: Thu, 21 Dec 1995 16:56:26 -0700 From: Nate Williams Message-Id: <199512212356.QAA04638@rocky.sri.MT.net> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) Cc: Nate Williams , current@freebsd.org, nate@freebsd.org Subject: Re: LD hits again :-( In-Reply-To: References: <199512211857.LAA03453@rocky.sri.MT.net> Sender: owner-current@freebsd.org Precedence: bulk > > >I'm pretty sure it's the linker stating that warning (whether it needs > >to or not) and not an actual link bug. I verified this by adding > >warning symbols to the crypt.c in libcipher, and the linker now says. > > >/usr/bin/ld -e start -dc -dp -o bdes /usr/lib/crt0.o -L../../lib/libcipher bdes.o -lcipher /usr/lib/libgcc.a -lc /usr/lib/libgcc.a > ^^^^^^^^^^^^^^^^^^^^ > Your linker path is wrong, here > you need to update Makefile to -current Read what I have above Andrey. That's not a 'cc' line, that's a ld line which is *exactly* the same line as cc uses. > >For now, I'm going to ignore it. Although it is still a bug, I don't > >consider it a critical bug. > > Secure is always critical. But the bug is not a link bug, but a 'warning' bug. The reason it shows up in -current and not in -stable is because Poul added the warning symbols to the crypt sources in libc/gen/crypt.c. The bug is a 'visual' bug, and not a functional bug. Nate From owner-freebsd-current Thu Dec 21 19:37:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA01798 for current-outgoing; Thu, 21 Dec 1995 19:37:54 -0800 (PST) Received: from nandi.com (root@Nandi.COM [206.205.75.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA01789 for ; Thu, 21 Dec 1995 19:37:49 -0800 (PST) Received: from kailash.nandi.com (kailash.Nandi.COM [206.205.75.3]) by nandi.com (8.7/8.6.9) with ESMTP id WAA22524 for ; Thu, 21 Dec 1995 22:38:29 GMT Received: from [127.0.0.1] ([127.0.0.1]) by kailash.nandi.com (8.7/8.7) with SMTP id WAA03127 for ; Thu, 21 Dec 1995 22:37:28 -0500 (EST) Message-Id: <199512220337.WAA03127@kailash.nandi.com> X-Authentication-Warning: kailash.nandi.com: Host [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: Recent book reccomendation in here. Date: Thu, 21 Dec 1995 22:37:27 EST From: Shiva Ramabadran Sender: owner-current@freebsd.org Precedence: bulk While discussing NFS on this list recently, someone mentioned, and others seconded a book which had a very good treatise on this and other UNIX concepts. For the life of me, I can't find that reference which I thought I had saved. Could someone please email me the reference again, if they have it ? Thanks, -Shiva -=- From owner-freebsd-current Thu Dec 21 23:24:38 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA10793 for current-outgoing; Thu, 21 Dec 1995 23:24:38 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA10787 for ; Thu, 21 Dec 1995 23:24:33 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id IAA04142 ; Fri, 22 Dec 1995 08:24:28 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id IAA00127 ; Fri, 22 Dec 1995 08:24:27 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id IAA01560; Fri, 22 Dec 1995 08:23:31 +0100 (MET) From: Ollivier Robert Message-Id: <199512220723.IAA01560@keltia.freenix.fr> Subject: Re: New sendmail sucks a bit ... (host map: lookup (wup.de): deferred) To: andreas@knobel.gun.de (Andreas Klemm) Date: Fri, 22 Dec 1995 08:23:31 +0100 (MET) Cc: current@freebsd.org In-Reply-To: from "Andreas Klemm" at Dec 21, 95 07:47:00 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1449 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk It seems that Andreas Klemm said: > not to use dns lookup, it does... Add FEATURE(nocanonify) for the UUCP case. > These are my two master configuration sendmail files: > > for uucp only, no dns lookup: > > divert(-1) > include(`../m4/cf.m4') > VERSIONID(`@(#)knobel.mc 1.1 (AKL) 10/08/95') > Only way out is to enable ppp, make internet connection and > wait for sendmail to requeue... :( "sendmail -q" will make it run the queue immediately. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Dec 18 00:50:47 MET 1995 From owner-freebsd-current Fri Dec 22 00:06:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA12262 for current-outgoing; Fri, 22 Dec 1995 00:06:13 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA12257 for ; Fri, 22 Dec 1995 00:06:10 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id AAA06934; Fri, 22 Dec 1995 00:06:01 -0800 (PST) Date: Fri, 22 Dec 1995 00:06:01 -0800 (PST) Message-Id: <199512220806.AAA06934@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@FreeBSD.org In-reply-to: <29652.819581550@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: pcnfsd.. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.org Precedence: bulk * Actually, I have a confession to make. Ahem. This is very difficult. * I have come to (ooph, ack) agree with Paul! I think that the * ${local_startup} trick has potential and it should be the package that * drops its startup glue there. sysinstall should just do a pkg_add on * pcnfsd and expect the right side-effects to happen (likewise with * pkg_delete - you'd want to remove the initialization!). And the X ports have no clue where the heck that tree is. C'mon Jordan, we've been through this before. SysV allergies aside, there are reasons why none of the ideas were implemented. Please don't touch anything in there until we can reach at least a partial agreement. Starting off with a wrong design is worse than starting from nothing, when we finally get the solution. Satoshi From owner-freebsd-current Fri Dec 22 02:25:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA18052 for current-outgoing; Fri, 22 Dec 1995 02:25:27 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA18047 for ; Fri, 22 Dec 1995 02:25:22 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id KAA12085 for ; Fri, 22 Dec 1995 10:23:40 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Fri, 22 Dec 1995 10:24:39 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id KAA13494; Fri, 22 Dec 1995 10:24:28 GMT From: Paul Richards Message-Id: <199512221024.KAA13494@cadair.elsevier.co.uk> Subject: Re: pcnfsd.. To: asami@cs.berkeley.edu (Satoshi Asami) Date: Fri, 22 Dec 1995 10:24:27 +0000 (GMT) Cc: jkh@time.cdrom.com, andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@FreeBSD.org In-Reply-To: <199512220806.AAA06934@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Dec 22, 95 00:06:01 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Satoshi Asami who said > > And the X ports have no clue where the heck that tree is. > That's not important in this case. As long as the package knows to install a startup file in the ports_startup_file directory and there's a hook in sysconfig to go look in this directory, there can be a script in that directory for the X package that'll start it and known anything that needs to be known about it. All we're saying, for example is the line in /etc/rc that starts apache should become a startup script say /usr/local/etc/ports/startup/apache, or something better named :-) And that instead of lots of special case lines for each port in /etc/rc or sysconfig you have one hook that trawls through that directory running startup scripts. None of the other ports know where the heck that tree is either. I think you're mixing up the idea of config files and startup files, X config files will still end up in the X tree which is something we should be a bit more forcefull about with the X folks because it's a badly broken concept. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Fri Dec 22 04:13:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA22422 for current-outgoing; Fri, 22 Dec 1995 04:13:29 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA22415 for ; Fri, 22 Dec 1995 04:13:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id EAA02792; Fri, 22 Dec 1995 04:08:05 -0800 To: asami@cs.berkeley.edu (Satoshi Asami) cc: andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@FreeBSD.org Subject: Re: pcnfsd.. In-reply-to: Your message of "Fri, 22 Dec 1995 00:06:01 PST." <199512220806.AAA06934@silvia.HIP.Berkeley.EDU> Date: Fri, 22 Dec 1995 04:08:05 -0800 Message-ID: <2783.819634085@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > And the X ports have no clue where the heck that tree is. > > C'mon Jordan, we've been through this before. SysV allergies aside, > there are reasons why none of the ideas were implemented. Well, there are ways around that, certainly. Consider for a moment the fact that nobody seemed to be all that keen to continue extending sysconfig or the other /etc files, either, and we're quickly running out of possible options to *debate* here! It's not like there are that many different approaches available to us - either we code implicit knowledge of our ports tree into our system startup files (current approach) or we enhance the "rendevous" mechanism enough that we don't have to. Are the X ports your only concern? We could take Paul's suggestion and enhance it a little bit, e.g. rather than being a directory it could now be a list of directories: local_startup=/usr/local/etc/rc.d /usr/X11R6/etc/rc.d OK? Jordan From owner-freebsd-current Fri Dec 22 04:49:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA23942 for current-outgoing; Fri, 22 Dec 1995 04:49:34 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA23933 for ; Fri, 22 Dec 1995 04:49:31 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0tT6uT-0003x6C; Fri, 22 Dec 95 04:49 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id NAA01890; Fri, 22 Dec 1995 13:49:05 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: asami@cs.berkeley.edu (Satoshi Asami), andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@FreeBSD.org Subject: Re: pcnfsd.. In-reply-to: Your message of "Fri, 22 Dec 1995 04:08:05 PST." <2783.819634085@time.cdrom.com> Date: Fri, 22 Dec 1995 13:49:05 +0100 Message-ID: <1888.819636545@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org Precedence: bulk > we don't have to. Are the X ports your only concern? We could take > Paul's suggestion and enhance it a little bit, e.g. rather than being a > directory it could now be a list of directories: > > local_startup=/usr/local/etc/rc.d /usr/X11R6/etc/rc.d > > OK? YES!!! (and merry Xmas!) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Dec 22 08:11:08 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA03380 for current-outgoing; Fri, 22 Dec 1995 08:11:08 -0800 (PST) Received: from chemserv.umd.edu (chemserv.umd.edu [129.2.64.40]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA03373 for ; Fri, 22 Dec 1995 08:11:03 -0800 (PST) Received: from mocha.eng.umd.edu (mocha.eng.umd.edu [129.2.98.16]) by chemserv.umd.edu (8.7.3/8.7) with ESMTP id LAA15139; Fri, 22 Dec 1995 11:10:59 -0500 (EST) Received: (chuckr@localhost) by mocha.eng.umd.edu (8.7.3/8.6.4) id LAA02760; Fri, 22 Dec 1995 11:10:58 -0500 (EST) Date: Fri, 22 Dec 1995 11:10:57 -0500 (EST) From: Chuck Robey X-Sender: chuckr@mocha.eng.umd.edu To: Shiva Ramabadran cc: current@FreeBSD.org Subject: Re: Recent book reccomendation in here. In-Reply-To: <199512220337.WAA03127@kailash.nandi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Thu, 21 Dec 1995, Shiva Ramabadran wrote: > > While discussing NFS on this list recently, someone mentioned, > and others seconded a book which had a very good treatise on this > and other UNIX concepts. > > For the life of me, I can't find that reference which I thought > I had saved. > > Could someone please email me the reference again, if they > have it ? I don't remember the post you're referring to, but a standard answer is Richard Stevens book, Unix Network Programming. It's very, very good. > > Thanks, > > -Shiva > -=- > > > ============================================================================ Chuck Robey chuckr@eng.umd.edu -- I run FreeBSD on n3lxx and Journey2 --------------------------------------------------------------------------- The Dilbert Zone is Dilbert's new WWW home! The area features never-before-seen original sketches of Dilbert, a photo tour of Scott Adams' studio, Dilbert Trivia and memorabilia, high school photos and much more!: From owner-freebsd-current Fri Dec 22 08:46:55 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA05734 for current-outgoing; Fri, 22 Dec 1995 08:46:55 -0800 (PST) Received: from nandi.com (root@Nandi.COM [206.205.75.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA05722 for ; Fri, 22 Dec 1995 08:46:46 -0800 (PST) Received: from localhost (shiva@localhost [127.0.0.1]) by nandi.com (8.7/8.6.9) with SMTP id LAA23443 for ; Fri, 22 Dec 1995 11:47:28 GMT Message-Id: <199512221147.LAA23443@nandi.com> X-Authentication-Warning: nandi.com: Host shiva@localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: Re: Recent book reccomendation in here. In-reply-to: Your message of "Fri, 22 Dec 1995 10:11:58 CST." <199512221611.KAA13803@right.PCS> Date: Fri, 22 Dec 1995 11:47:27 +0000 From: Shiva Ramabadran Sender: owner-current@freebsd.org Precedence: bulk } } Unix Internals, the New Frontier } by Suresh Valhalia. } That was it! That should be enough to go on. Many Thanks, -Shiva -=- From owner-freebsd-current Fri Dec 22 09:41:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA08556 for current-outgoing; Fri, 22 Dec 1995 09:41:28 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA08544 for ; Fri, 22 Dec 1995 09:41:18 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id SAA14440 ; Fri, 22 Dec 1995 18:41:07 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id SAA01738 ; Fri, 22 Dec 1995 18:41:07 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id SAA03395; Fri, 22 Dec 1995 18:12:54 +0100 (MET) From: Ollivier Robert Message-Id: <199512221712.SAA03395@keltia.freenix.fr> Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) To: andreas@knobel.gun.de (Andreas Klemm) Date: Fri, 22 Dec 1995 18:12:54 +0100 (MET) Cc: tom@smart.ruhr.de, nate@rocky.sri.MT.net, current@FreeBSD.org In-Reply-To: from "Andreas Klemm" at Dec 21, 95 07:28:44 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1449 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that Andreas Klemm said: > - make world: > stopped when compiling ypserv. > rpcgen (2.1 version) didn't understand the new > commandline flags of the -current version. So I commented > out ypserv. I build it later. Probably the include/rpcsvc/yp.x changes. make "all install" in "include/rpcsvc" should fix it. > Puh, just had problems with my freshly compiled pine... > > malloc warning: > free(): already free chunk Our malloc is warning you that Pine does a double free() on some thing. The problem is in Pine. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Dec 18 00:50:47 MET 1995 From owner-freebsd-current Fri Dec 22 13:15:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA17906 for current-outgoing; Fri, 22 Dec 1995 13:15:04 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA17885 for ; Fri, 22 Dec 1995 13:14:58 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id NAA02901; Fri, 22 Dec 1995 13:13:25 -0800 (PST) Date: Fri, 22 Dec 1995 13:13:25 -0800 (PST) Message-Id: <199512222113.NAA02901@silvia.HIP.Berkeley.EDU> To: p.richards@elsevier.co.uk CC: jkh@time.cdrom.com, andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@FreeBSD.org In-reply-to: <199512221024.KAA13494@cadair.elsevier.co.uk> (message from Paul Richards on Fri, 22 Dec 1995 10:24:27 +0000 (GMT)) Subject: Re: pcnfsd.. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.org Precedence: bulk * I think you're mixing up the idea of config files and startup files, X config * files will still end up in the X tree which is something we should be a bit * more forcefull about with the X folks because it's a badly broken concept. That's not what I meant. The X ports don't know where the local tree (usually "/usr/local") is, the way the ports mechanism is designed now. I made several suggestions on how to solve this (and the startup file situation), but none was good enough. Satoshi From owner-freebsd-current Fri Dec 22 13:18:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA18175 for current-outgoing; Fri, 22 Dec 1995 13:18:46 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA18165 for ; Fri, 22 Dec 1995 13:18:43 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id NAA02926; Fri, 22 Dec 1995 13:18:33 -0800 (PST) Date: Fri, 22 Dec 1995 13:18:33 -0800 (PST) Message-Id: <199512222118.NAA02926@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@FreeBSD.org In-reply-to: <2783.819634085@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: pcnfsd.. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.org Precedence: bulk * we don't have to. Are the X ports your only concern? We could take To me, yes. As long as we don't go editing files (i.e., each port has its own file), that's ok for me. * Paul's suggestion and enhance it a little bit, e.g. rather than being a * directory it could now be a list of directories: * * local_startup=/usr/local/etc/rc.d /usr/X11R6/etc/rc.d I can certainly live with that, as it wouldn't get in our way when we try to change that in the future to get the "/usr/local" and "/usr/X11R6" from other places. (Right now they are defined in sys.mk, bsd.port.mk, /etc/make.conf, and maybe other files I can't remember at the moment.) Satoshi From owner-freebsd-current Fri Dec 22 14:00:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA20867 for current-outgoing; Fri, 22 Dec 1995 14:00:05 -0800 (PST) Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20824 for ; Fri, 22 Dec 1995 13:59:57 -0800 (PST) Received: (from scrappy@localhost) by hub.org (8.7.3/8.7.3) id QAA10144; Fri, 22 Dec 1995 16:59:58 -0500 (EST) Date: Fri, 22 Dec 1995 16:59:56 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org Subject: nfsiod under *-current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi... I'm trying to get nfsiod running under my *-current box, and, when I try to run it, come up with: freebsd# nfsiod -n 4 /lkm/nfs_mod.o: Undefined symbol `_vm_object_lookup' referenced from text segment /lkm/nfs_mod.o: Undefined symbol `_hostnamelen' referenced from text segment /lkm/nfs_mod.o: Undefined symbol `_enoioctl' referenced from data segment modload: /usr/bin/ld: return code 1 nfsiod: vfsload(nfs): Operation not permitted Figuring that maybe my lkm was out of date, I've tried to recompile that, but: freebsd# make ===> atapi echo "#define NWDC 2" > wdc.h cc -O2 -m486 -pipe -nostdinc -I. -I/sys -DATAPI -DATAPI_MODULE -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/atapi/../../sys -W -Wcomment -Wredundant-decls -c /usr/src/lkm/atapi/../../sys/i386/isa/atapi.c ld -r -static -o tmp.o atapi.o symorder -c symb.tmp tmp.o symorder: tmp.o: stripped: Inappropriate file type or format *** Error code 2 Stop. *** Error code 1 Stop. Figuring that there may be a problem with symorder...I recompiled that and installed ... same error. And this is where I get stuck :( The sources are current to 5am this morning... Ah, just found out *where* this lkm is...I'm doing a 'make nfs' on the lkm sources, which seems, so far, to be working, so, I guess, the question falls to...is there a known problem with compiling atapi under lkm? thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-current Fri Dec 22 14:19:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA22928 for current-outgoing; Fri, 22 Dec 1995 14:19:48 -0800 (PST) Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA22916 for ; Fri, 22 Dec 1995 14:19:43 -0800 (PST) Received: (from scrappy@localhost) by hub.org (8.7.3/8.7.3) id RAA10325; Fri, 22 Dec 1995 17:19:40 -0500 (EST) Date: Fri, 22 Dec 1995 17:19:39 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org Subject: More on nfsiod problem... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi... Well, it looks like the problem might be deeper then I first reported (or its a really stupid error on my part...you pick? *grin*) cc -O2 -m486 -pipe -DNFS -DINET -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/nfs/../../sys -W -Wcomment -Wredundant-decls -DVFS_LKM -DMODVNOPS=nfs_modvnops -I. -c /usr/src/lkm/nfs/../../sys/nfs/nfs_vnops.c ld -r -static -o tmp.o nfs_bio.o nfs_node.o nfs_nqlease.o nfs_serv.o nfs_socket.o nfs_srvcache.o nfs_subs.o nfs_syscalls.o nfs_vfsops.o nfs_vnops.o symorder -c symb.tmp tmp.o symorder: tmp.o: no string table: Inappropriate file type or format *** Error code 2 Stop. *** Error code 1 Stop. freebsd# file nfs/tmp.o nfs/tmp.o: PDP-11 executable not stripped PDP-11 executable? neat, and on a 486 even :) Any ideas? I'm assuming, maybe incorrectly, that it has nothing to do with the fact tht I'm using CFLAGS of '-O2 -m486 -pipe'...does it? gcc is 2.6.3 currently. Thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-current Fri Dec 22 14:29:31 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA23683 for current-outgoing; Fri, 22 Dec 1995 14:29:31 -0800 (PST) Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA23678 for ; Fri, 22 Dec 1995 14:29:23 -0800 (PST) Received: (from scrappy@localhost) by hub.org (8.7.3/8.7.3) id RAA10367; Fri, 22 Dec 1995 17:29:26 -0500 (EST) Date: Fri, 22 Dec 1995 17:29:26 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org Subject: Conclusion to nfsiod/lkm problem... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi... After my last posting, where at the very bottom I questioned my CFLAGS, I went into make.conf and removed the LDFLAGS=-static line I had added in... ...it compiles now. So, the question remains...what is it about lkm that its functions can't be statically linked? I'm not 100% certain of what lkm does, from the name, I would derive that it deals with kernel memory and possibly links from software to it? *shrug* Wild guess.. Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-current Fri Dec 22 15:00:15 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA25416 for current-outgoing; Fri, 22 Dec 1995 15:00:15 -0800 (PST) Received: from rmurphy.slip.bcm.tmc.edu (root@RMURPHY.SLIP.BCM.TMC.EDU [128.249.250.138]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA25409 for ; Fri, 22 Dec 1995 15:00:07 -0800 (PST) Received: (from rich@localhost) by rmurphy.slip.bcm.tmc.edu (8.6.12/8.6.9) id QAA02389; Fri, 22 Dec 1995 16:58:16 -0600 Date: Fri, 22 Dec 1995 16:58:16 -0600 Message-Id: <199512222258.QAA02389@rmurphy.slip.bcm.tmc.edu> From: Rich Murphey To: p.richards@elsevier.co.uk CC: asami@cs.berkeley.edu, jkh@time.cdrom.com, andreas@knobel.gun.de, graichen@omega.physik.fu-berlin.de, current@freebsd.org In-reply-to: <199512221024.KAA13494@cadair.elsevier.co.uk> (message from Paul Richards on Fri, 22 Dec 1995 10:24:27 +0000 (GMT)) Subject: Re: pcnfsd.. Reply-to: rich@lamprey.utmb.edu Sender: owner-current@freebsd.org Precedence: bulk |From: Paul Richards |I think you're mixing up the idea of config files and startup files, X config |files will still end up in the X tree which is something we should be a bit |more forcefull about with the X folks because it's a badly broken concept. Most of the critical X runtime config files such as XF86Config or xdm-config can be put in /etc so that the distribution copies in /usr/X11R6.. are ignored. What config files do you mean? Perhaps we can sort it out. Rich From owner-freebsd-current Fri Dec 22 16:46:22 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA29004 for current-outgoing; Fri, 22 Dec 1995 16:46:22 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA28999 for ; Fri, 22 Dec 1995 16:46:17 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id BAA16475; Sat, 23 Dec 1995 01:30:26 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id BAA00337; Sat, 23 Dec 1995 01:03:18 +0100 (MET) Date: Sat, 23 Dec 1995 01:03:18 +0100 (MET) From: Andreas Klemm To: Ollivier Robert cc: current@freebsd.org Subject: Re: New sendmail sucks a bit ... (host map: lookup (wup.de): deferred) In-Reply-To: <199512220723.IAA01560@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk > It seems that Andreas Klemm said: > > not to use dns lookup, it does... > > Add FEATURE(nocanonify) for the UUCP case. This works fine, thanks ! -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Fri Dec 22 18:58:32 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA01918 for current-outgoing; Fri, 22 Dec 1995 18:58:32 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA01848 for ; Fri, 22 Dec 1995 18:57:24 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA04398; Sat, 23 Dec 1995 13:53:57 +1100 Date: Sat, 23 Dec 1995 13:53:57 +1100 From: Bruce Evans Message-Id: <199512230253.NAA04398@godzilla.zeta.org.au> To: current@freebsd.org, scrappy@hub.org Subject: Re: Conclusion to nfsiod/lkm problem... Sender: owner-current@freebsd.org Precedence: bulk > After my last posting, where at the very bottom I questioned >my CFLAGS, I went into make.conf and removed the LDFLAGS=-static >line I had added in... > ...it compiles now. > So, the question remains...what is it about lkm that its functions >can't be statically linked? I'm not 100% certain of what lkm does, from Don't know, but LDFLAGS=-static means the same as LDFLAGS='-s tatic'. -s says to strip the object and the arg `tatic' is ignored. Perhaps you meant -Bstatic. Bruce From owner-freebsd-current Fri Dec 22 19:04:43 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA02113 for current-outgoing; Fri, 22 Dec 1995 19:04:43 -0800 (PST) Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA02106 for ; Fri, 22 Dec 1995 19:04:37 -0800 (PST) Received: (from scrappy@localhost) by hub.org (8.7.3/8.7.3) id WAA15929; Fri, 22 Dec 1995 22:04:19 -0500 (EST) Date: Fri, 22 Dec 1995 22:04:17 -0500 (EST) From: "Marc G. Fournier" To: Bruce Evans cc: current@freebsd.org Subject: Re: Conclusion to nfsiod/lkm problem... In-Reply-To: <199512230253.NAA04398@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sat, 23 Dec 1995, Bruce Evans wrote: > > After my last posting, where at the very bottom I questioned > >my CFLAGS, I went into make.conf and removed the LDFLAGS=-static > >line I had added in... > > > ...it compiles now. > > > So, the question remains...what is it about lkm that its functions > >can't be statically linked? I'm not 100% certain of what lkm does, from > > Don't know, but LDFLAGS=-static means the same as LDFLAGS='-s tatic'. > -s says to strip the object and the arg `tatic' is ignored. Perhaps you > meant -Bstatic. > Ack...ya, that's what I meant...thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-current Fri Dec 22 19:16:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA02544 for current-outgoing; Fri, 22 Dec 1995 19:16:29 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA02535 for ; Fri, 22 Dec 1995 19:16:20 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA04943 for current@freebsd.org; Sat, 23 Dec 1995 14:11:56 +1100 Date: Sat, 23 Dec 1995 14:11:56 +1100 From: Bruce Evans Message-Id: <199512230311.OAA04943@godzilla.zeta.org.au> To: current@freebsd.org Subject: cvs fails to remove no-longer-present files Sender: owner-current@freebsd.org Precedence: bulk `cvs update' and `cvs co' didn't do anything for the large batch of removed games/x11 and etc/etc.i386 files. I moved the directories out of the way. Then `cvs co' worked right. Bruce From owner-freebsd-current Fri Dec 22 19:46:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA04010 for current-outgoing; Fri, 22 Dec 1995 19:46:23 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA03991 for ; Fri, 22 Dec 1995 19:46:15 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA05736; Sat, 23 Dec 1995 14:41:30 +1100 Date: Sat, 23 Dec 1995 14:41:30 +1100 From: Bruce Evans Message-Id: <199512230341.OAA05736@godzilla.zeta.org.au> To: current@freebsd.org, kato@eclogite.eps.nagoya-u.ac.jp Subject: Re: outb in random.c Sender: owner-current@freebsd.org Precedence: bulk >The function add_timer_randomness() in sys/i386/isa/random.c contains: > outb(TIMER_LATCH|TIMER_SEL0, TIMER_MODE); /* latch the count ASAP */ >This is outb(data, port). I think this should be > outb(TIMER_MODE, TIMER_LATCH|TIMER_SEL0); /* latch the count ASAP */ This is now fixed. Thanks for the bug report. Bruce From owner-freebsd-current Fri Dec 22 19:47:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA04074 for current-outgoing; Fri, 22 Dec 1995 19:47:11 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA04069 for ; Fri, 22 Dec 1995 19:47:07 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id TAA01822; Fri, 22 Dec 1995 19:47:06 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id TAA00559; Fri, 22 Dec 1995 19:47:09 -0800 (PST) Message-Id: <199512230347.TAA00559@corbin.Root.COM> To: Bruce Evans cc: current@freebsd.org Subject: Re: cvs fails to remove no-longer-present files In-reply-to: Your message of "Sat, 23 Dec 95 14:11:56 +1100." <199512230311.OAA04943@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 22 Dec 1995 19:47:08 -0800 Sender: owner-current@freebsd.org Precedence: bulk >`cvs update' and `cvs co' didn't do anything for the large batch of >removed games/x11 and etc/etc.i386 files. I moved the directories >out of the way. Then `cvs co' worked right. You used "cvs update -Pd"? Works for me: cvs update: x11/Makefile is no longer in the repository cvs update: x11/xneko/Makefile is no longer in the repository cvs update: x11/xneko/xneko.6 is no longer in the repository cvs update: x11/xneko/xneko.c is no longer in the repository cvs update: x11/xneko/bitmaps/awake.xbm is no longer in the repository ... -DG From owner-freebsd-current Fri Dec 22 20:34:58 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA07194 for current-outgoing; Fri, 22 Dec 1995 20:34:58 -0800 (PST) Received: from bluenose.na.tuns.ca (bluenose.na.tuns.ca [134.190.5.184]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA07137 for ; Fri, 22 Dec 1995 20:34:53 -0800 (PST) Received: (from chuangjm@localhost) by bluenose.na.tuns.ca (8.7.3/8.6.12) id AAA24880 for FreeBSD-current@freefall.cdrom.com; Sat, 23 Dec 1995 00:31:27 GMT From: Jim Chuang Message-Id: <199512230031.AAA24880@bluenose.na.tuns.ca> Subject: Dump & Amanda in FreeBSD-current To: FreeBSD-current@freefall.FreeBSD.org Date: Sat, 23 Dec 1995 00:31:27 +0000 () X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk It appears that dump in FreeBSD-current is not consistent with amanda. The error message from amdump is as follow: driver: result time 21.911 from dumper0: FAILED 00-00001 [no dump size line] amanda was working fine with dump in FreeBSD-2.1.0-RELEASE. Is there any change of dump in FreeBSD-current? Thanks Jim From owner-freebsd-current Fri Dec 22 20:36:40 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA08346 for current-outgoing; Fri, 22 Dec 1995 20:36:40 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA08053 for ; Fri, 22 Dec 1995 20:36:13 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA07671; Sat, 23 Dec 1995 15:35:30 +1100 Date: Sat, 23 Dec 1995 15:35:30 +1100 From: Bruce Evans Message-Id: <199512230435.PAA07671@godzilla.zeta.org.au> To: bde@zeta.org.au, davidg@Root.COM Subject: Re: cvs fails to remove no-longer-present files Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk >>`cvs update' and `cvs co' didn't do anything for the large batch of >>removed games/x11 and etc/etc.i386 files. I moved the directories >>out of the way. Then `cvs co' worked right. > You used "cvs update -Pd"? Works for me: No, but it made no difference, and I tried "cvs co -P". The problem was still there when I moved some things back: cd $CVSROOT/src/etc/etc.i386 mv Attic/cpio* . cd /usr/src/etc/etc.i386 cvs update # check out cpio* again as expected cd $CVSROOT/src/etc/etc.i386 mv cpio* Attic cd /usr/src/etc/etc.i386 cvs update [-Pd] # didn't do anything and more interestingly: rm cpio* cvs update # checked out cpio* from the Attic! The new cvs apparently has a bugfeature of checking out old things from the Attic when there are references to the old things in CVS/Entries This is inconsistent with the old cvs, and breaks ctm, which doesn't export CVS/*. `cvs update -r HEAD' in etc.i386 works even worse. It checks out all the old stuff in the Attic. Oops. I made the mistake of trying this in sys/i386/i386 too, and it checked out lots of old files, e.g., bt742a.c. Bruce From owner-freebsd-current Fri Dec 22 20:38:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA09623 for current-outgoing; Fri, 22 Dec 1995 20:38:36 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA09558 for ; Fri, 22 Dec 1995 20:38:30 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id UAA01873; Fri, 22 Dec 1995 20:38:29 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id UAA00172; Fri, 22 Dec 1995 20:38:29 -0800 (PST) Message-Id: <199512230438.UAA00172@corbin.Root.COM> To: Bruce Evans cc: current@freebsd.org Subject: Re: cvs fails to remove no-longer-present files In-reply-to: Your message of "Sat, 23 Dec 95 15:35:30 +1100." <199512230435.PAA07671@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 22 Dec 1995 20:38:25 -0800 Sender: owner-current@freebsd.org Precedence: bulk >The new cvs apparently has a bugfeature of checking out old things from >the Attic when there are references to the old things in CVS/Entries >This is inconsistent with the old cvs, and breaks ctm, which doesn't >export CVS/*. Oh! I haven't switched to using the new cvs yet...that explains it. Peter? -DG From owner-freebsd-current Fri Dec 22 21:17:17 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA19959 for current-outgoing; Fri, 22 Dec 1995 21:17:17 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA19953 for ; Fri, 22 Dec 1995 21:17:12 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA07542; Fri, 22 Dec 1995 22:19:35 -0700 Date: Fri, 22 Dec 1995 22:19:35 -0700 From: Nate Williams Message-Id: <199512230519.WAA07542@rocky.sri.MT.net> To: davidg@Root.COM Cc: Bruce Evans , current@freebsd.org Subject: Re: cvs fails to remove no-longer-present files In-Reply-To: <199512230438.UAA00172@corbin.Root.COM> References: <199512230435.PAA07671@godzilla.zeta.org.au> <199512230438.UAA00172@corbin.Root.COM> Sender: owner-current@freebsd.org Precedence: bulk > >The new cvs apparently has a bugfeature of checking out old things from > >the Attic when there are references to the old things in CVS/Entries > >This is inconsistent with the old cvs, and breaks ctm, which doesn't > >export CVS/*. > > Oh! I haven't switched to using the new cvs yet...that explains it. > Peter? The new version of cvs removes files than the older binary (which is still used on freefall). The new version of CVS has 'death-support', which allows you to bring stuff in-out of the Repository w/out moving things in/out of the Attic. I'm not sure how to fix this other than to upgrade the version of CVS on freefall to the new version, and make sure all the developers also upgrade to it at the same time. (It would probably be good for the developers to upgrade to the newer version of rcs as well) Nate From owner-freebsd-current Fri Dec 22 21:58:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA20999 for current-outgoing; Fri, 22 Dec 1995 21:58:13 -0800 (PST) Received: from chrome.jdl.com (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA20994 for ; Fri, 22 Dec 1995 21:58:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chrome.jdl.com (8.6.12/8.6.12) with SMTP id XAA03288; Fri, 22 Dec 1995 23:57:38 -0600 Message-Id: <199512230557.XAA03288@chrome.jdl.com> X-Authentication-Warning: chrome.jdl.com: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: Bruce Evans , current@freebsd.org Subject: Re: cvs fails to remove no-longer-present files In-reply-to: Your message of "Fri, 22 Dec 1995 20:38:25 PST." <199512230438.UAA00172@corbin.Root.COM> Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Fri, 22 Dec 1995 23:57:33 -0600 From: Jon Loeliger Sender: owner-current@freebsd.org Precedence: bulk Apparently, David Greenman scribbled: > >The new cvs apparently has a bugfeature of checking out old things from > >the Attic when there are references to the old things in CVS/Entries > >This is inconsistent with the old cvs, and breaks ctm, which doesn't > >export CVS/*. > > Oh! I haven't switched to using the new cvs yet...that explains it. > Peter? Hmmm... I stumbled onto something similar too. What's the revision notion of "old" and "new" here? Thanks, jdl From owner-freebsd-current Fri Dec 22 22:40:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA21982 for current-outgoing; Fri, 22 Dec 1995 22:40:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA21977 for ; Fri, 22 Dec 1995 22:40:32 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id XAA21503; Fri, 22 Dec 1995 23:36:01 -0700 From: Terry Lambert Message-Id: <199512230636.XAA21503@phaeton.artisoft.com> Subject: Re: More ancient IP broadcast cruft to be removed To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Fri, 22 Dec 1995 23:36:01 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <9512201756.AA21859@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Dec 20, 95 12:56:53 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > I believe that this code is a waste of time. If the user wants to > accept broadcasts on the host-all-zeros address, then she should > configure the interface for that broadcast address. (Using the > standard broadcast address would not work to communicate with old > machines anyway, so this hack doesn't really gain one anything.) Gatewaying old and new broadcast formats on the same physical wire? Like a new net with old Apollo Domain systems? Any chance of #ifdef'ing 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-current Sat Dec 23 02:23:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA02364 for current-outgoing; Sat, 23 Dec 1995 02:23:56 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA02331 for ; Sat, 23 Dec 1995 02:23:48 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA20642; Sat, 23 Dec 1995 11:22:45 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id LAA01347; Sat, 23 Dec 1995 11:22:34 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id KAA22784; Sat, 23 Dec 1995 10:42:13 +0100 From: J Wunsch Message-Id: <199512230942.KAA22784@uriah.heep.sax.de> Subject: Re: New sendmail sucks a bit ... (host map: lookup (wup.de): deferred) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 23 Dec 1995 10:42:13 +0100 (MET) Cc: andreas@knobel.gun.de Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199512220723.IAA01560@keltia.freenix.fr> from "Ollivier Robert" at Dec 22, 95 08:23:31 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > > > Only way out is to enable ppp, make internet connection and > > wait for sendmail to requeue... :( > > "sendmail -q" will make it run the queue immediately. FWIW, Andreas, why don't you simply run your UUCP over TCP while your SLIP/PPP connection is up? This way, you can use the same configur- ation all the time. -- 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-current Sat Dec 23 03:51:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA05847 for current-outgoing; Sat, 23 Dec 1995 03:51:11 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA05841 for ; Sat, 23 Dec 1995 03:51:05 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA21798; Sat, 23 Dec 1995 12:51:01 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id MAA02246; Sat, 23 Dec 1995 12:51:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id MAA23396; Sat, 23 Dec 1995 12:43:47 +0100 From: J Wunsch Message-Id: <199512231143.MAA23396@uriah.heep.sax.de> Subject: Re: Dump & Amanda in FreeBSD-current To: chuangjm@bluenose.na.tuns.ca (Jim Chuang) Date: Sat, 23 Dec 1995 12:43:47 +0100 (MET) Cc: FreeBSD-current@freefall.freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199512230031.AAA24880@bluenose.na.tuns.ca> from "Jim Chuang" at Dec 23, 95 00:31:27 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG Precedence: bulk As Jim Chuang wrote: > > Is there any change of dump in FreeBSD-current? Yes. It seems that amanda is silly enough to insist on the second, redundant word "DUMP:" in the dump output. It looks now consistently like: DUMP: Date of this level 0 dump: Sat Dec 23 12:41:47 1995 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd1h (/tmp) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 1806 tape blocks on 0.05 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 1798 tape blocks on 1 volumes(s) DUMP: finished in 3 seconds, throughput 599 KBytes/sec DUMP: Closing /dev/null DUMP: DUMP IS DONE while the previous version was: DUMP: Date of this level 0 dump: Sat Dec 23 12:41:47 1995 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd1h (/tmp) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 1806 tape blocks on 0.05 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 1798 tape blocks on 1 volumes(s) ^^^^^^^^^^^^ DUMP: Closing /dev/null DUMP: DUMP IS DONE I've been removing the superfluous DUMP: in the best intentions when commiting Adreas Klemm's throughput changes. I'll back it out ASAP. (Sigh.) -- 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-current Sat Dec 23 06:21:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA11615 for current-outgoing; Sat, 23 Dec 1995 06:21:27 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA11609 for ; Sat, 23 Dec 1995 06:21:20 -0800 (PST) Received: from mordillo (oberon.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id PAA19202; Sat, 23 Dec 1995 15:20:50 +0100 (MET) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id JAA00586; Sat, 23 Dec 1995 09:32:26 +0100 From: Thomas Graichen Message-Id: <199512230832.JAA00586@mordillo> Subject: Re: More on nfsiod problem... To: scrappy@hub.org (Marc G. Fournier) Date: Sat, 23 Dec 1995 09:32:25 +0100 (MET) Cc: current@freebsd.org In-Reply-To: from "Marc G. Fournier" at Dec 22, 95 05:19:39 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk hasn't Marc G. Fournier said ? ... > freebsd# file nfs/tmp.o > nfs/tmp.o: PDP-11 executable not stripped > > PDP-11 executable? neat, and on a 486 even :) > do you have an old /etc/magic - mine says: # This covers object files, and is better than "PDP-11 executable" 0 lelong 000000407 impure format >16 lelong >0 not stripped and my 2.1 machine says: graichen@mordillo:~> file test.o test.o: NetBSD/i386 object file not stripped nice :-) t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-current Sat Dec 23 08:16:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA17014 for current-outgoing; Sat, 23 Dec 1995 08:16:11 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA17000 for ; Sat, 23 Dec 1995 08:16:05 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id RAA19543 ; Sat, 23 Dec 1995 17:15:52 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id RAA03633 ; Sat, 23 Dec 1995 17:15:51 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id RAA07527; Sat, 23 Dec 1995 17:11:32 +0100 (MET) From: Ollivier Robert Message-Id: <199512231611.RAA07527@keltia.freenix.fr> Subject: Re: New sendmail sucks a bit ... (host map: lookup (wup.de): deferred) To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 23 Dec 1995 17:11:32 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG, andreas@knobel.gun.de In-Reply-To: <199512230942.KAA22784@uriah.heep.sax.de> from "J Wunsch" at Dec 23, 95 10:42:13 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1449 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk It seems that J Wunsch said: > FWIW, Andreas, why don't you simply run your UUCP over TCP while your > SLIP/PPP connection is up? This way, you can use the same configur- > ation all the time. Seconded. That's what I use also. Just put two entries for the site you're calling like the following: system foo call-login * call-password * phone xxxxxxxx Time Any alternate address nn.nn.nn.nn port TCP protocol ig chat ogin: \L word \P When you're not connected the first entry will make uucico dial. When you're connected the first call will fail because ppp already use the device and the second one will succed with TCP. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Dec 18 00:50:47 MET 1995 From owner-freebsd-current Sat Dec 23 09:20:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA22033 for current-outgoing; Sat, 23 Dec 1995 09:20:34 -0800 (PST) Received: from sivka.carrier.kiev.ua (root@sivka.carrier.kiev.ua [193.125.68.130]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA21915 for ; Sat, 23 Dec 1995 09:19:37 -0800 (PST) Received: from elvisti.kiev.ua (uucp@localhost) by sivka.carrier.kiev.ua (Sendmail 8.who.cares/5) with UUCP id TAA01156 for current@freebsd.org; Sat, 23 Dec 1995 19:20:59 +0200 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.33]) by spider2.elvisti.kiev.ua (8.6.12/8.ElVisti) with ESMTP id TAA07925 for ; Sat, 23 Dec 1995 19:24:10 +0200 Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id TAA05535 for current@freebsd.org; Sat, 23 Dec 1995 19:24:10 +0200 From: "Andrew V. Stesin" Message-Id: <199512231724.TAA05535@office.elvisti.kiev.ua> Subject: (fwd) Fix for bug in all known versions of GCC To: current@freebsd.org Date: Sat, 23 Dec 1995 19:24:09 +0200 (EET) X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk ------- Forwarded Message Return-Path: Message-Id: Date: Tue, 19 Dec 95 20:50 CST From: Richard Henderson To: bug-gcc@prep.ai.mit.edu Cc: mmex@shadowland.res.cmu.edu, linux-kernel@vger.rutgers.edu Reply-To: rth@tamu.edu Subject: gcc 2.7.2 i386 strength-reduce bug fix Sender: owner-linux-kernel@vger.rutgers.edu The strength-reduction optimization in gcc 2.7.2 (and earlier) can produce incorrect code on the i386 platform. The problem is that the giv chosen to eliminate a biv may overflow, causing comparisons to fail. The temporary solution is to simply prevent the elimination. A more complete solution would use initial and final value information to assert that the replacement remains in range for the type. Another way the optimization might be retained is if the loop is transformed to: if (x < end) { do { ... } while (x != end); } Naturally, there are some severe restrictions on when this might be used, but a number of simple ones (such as the example below) that could benefit. Here is an example that reproduces the bug: - ------------------------------------------------------------ int A[3]; unsigned int B = 3; void printit(void) { int i; for(i = 0; i < B; i++) printf("A[%d] = %d\n", i, A[i]); } int main() { int i; for(i = 0; i < B; i++) A[i] = i-3; printit(); return 0; } - ------------------------------------------------------------ Here is a patch that defeats the elimination of a biv involved in a comparison. - ------------------------------------------------------------ *** loop.c.orig Tue Oct 3 11:17:16 1995 - --- loop.c Tue Dec 19 19:38:29 1995 *************** maybe_eliminate_biv_1 (x, insn, bl, elim *** 6119,6124 **** - --- 6119,6127 ---- else break; + /* Unless we can assert that the replacement giv does not + overflow, we cannot (simply) eliminate the biv. */ + #if 0 if (CONSTANT_P (arg)) { /* First try to replace with any giv that has constant positive *************** maybe_eliminate_biv_1 (x, insn, bl, elim *** 6264,6269 **** - --- 6267,6273 ---- } #endif } + #endif /* If we get here, the biv can't be eliminated. */ return 0; - ------------------------------------------------------------ r~ ------- End of Forwarded Message -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 An undocumented feature is a coding error. From owner-freebsd-current Sat Dec 23 12:00:42 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA27952 for current-outgoing; Sat, 23 Dec 1995 12:00:42 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA27947 for ; Sat, 23 Dec 1995 12:00:38 -0800 (PST) Received: by sequent.kiae.su id AA16804 (5.65.kiae-2 ); Sat, 23 Dec 1995 22:58:50 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 23 Dec 95 22:58:49 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id WAA01877; Sat, 23 Dec 1995 22:58:30 +0300 (MSK) To: current@freebsd.org Cc: mark@grondar.za, "Garrett A. Wollman" Message-Id: Organization: Olahm Ha-Yetzirah Date: Sat, 23 Dec 1995 22:58:30 +0300 (MSK) X-Mailer: Mail/@ [v2.41 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Kerberos damaged in -current or my fault... Lines: 21 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk The symptom is: passwd & kadmin not works, they says: Could not fetch local socket address It means that kadm_cli_conn() function fails, after investigation I found that it fails in bind(..., admin_addr, ...) which return errno = 48 (Address already in use) admin_addr correctly (?) initialized to kerberos_master,tcp and kadmin is running and listen this port (from netstat). It works for me month ago and I don't remember that I touch something. Please check your kadmin/passwd/eBones compiled in -current and tell, if it work for you or not or tell me, where is error. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sat Dec 23 12:37:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA29224 for current-outgoing; Sat, 23 Dec 1995 12:37:23 -0800 (PST) Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA29218 for ; Sat, 23 Dec 1995 12:37:16 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.7.3/8.6.9) with ESMTP id WAA08804; Sat, 23 Dec 1995 22:36:50 +0200 (SAT) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.6.9) with SMTP id WAA08653; Sat, 23 Dec 1995 22:36:49 +0200 (SAT) Message-Id: <199512232036.WAA08653@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) cc: current@freebsd.org, mark@grondar.za, "Garrett A. Wollman" Subject: Re: Kerberos damaged in -current or my fault... Date: Sat, 23 Dec 1995 22:36:48 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk Its the same for me. I have found the same hassle in the same places. I reported this (differently) to Justin and Garrett. M =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > The symptom is: > passwd & kadmin not works, they says: > Could not fetch local socket address > > It means that kadm_cli_conn() function fails, after investigation > I found that it fails in bind(..., admin_addr, ...) > which return errno = 48 (Address already in use) > > admin_addr correctly (?) initialized to kerberos_master,tcp > and kadmin is running and listen this port (from netstat). > > It works for me month ago and I don't remember that I touch > something. > Please check your kadmin/passwd/eBones compiled in -current > and tell, if it work for you or not or tell me, where is error. -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sat Dec 23 13:27:55 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA00877 for current-outgoing; Sat, 23 Dec 1995 13:27:55 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA00871 for ; Sat, 23 Dec 1995 13:27:51 -0800 (PST) Received: by sovcom.kiae.su id AA06306 (5.65.kiae-1 ); Sun, 24 Dec 1995 00:27:23 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 24 Dec 95 00:27:22 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id AAA00241; Sun, 24 Dec 1995 00:24:37 +0300 (MSK) To: Mark Murray Cc: current@freebsd.org, "Garrett A. Wollman" References: <199512232036.WAA08653@grumble.grondar.za> In-Reply-To: <199512232036.WAA08653@grumble.grondar.za>; from Mark Murray at Sat, 23 Dec 1995 22:36:48 +0200 Message-Id: Organization: Olahm Ha-Yetzirah Date: Sun, 24 Dec 1995 00:24:37 +0300 (MSK) X-Mailer: Mail/@ [v2.41 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Kerberos damaged in -current or my fault... Lines: 18 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message <199512232036.WAA08653@grumble.grondar.za> Mark Murray writes: >Its the same for me. I have found the same hassle in the same places. >I reported this (differently) to Justin and Garrett. >> and kadmin is running and listen this port (from netstat). ^^^^^^ I mean kadmind, of course. Well, it seems that TCP part damaged somehow, maybe in_pcb.c (in_pcbbind/in_pcblookup)??? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sat Dec 23 15:21:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA04767 for current-outgoing; Sat, 23 Dec 1995 15:21:20 -0800 (PST) Received: from gwydion.hns.st-louis.mo.us (dialup-92.icon-stl.net [199.217.153.92]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA04755 for ; Sat, 23 Dec 1995 15:20:54 -0800 (PST) Received: (from kenth@localhost) by gwydion.hns.st-louis.mo.us (8.7.3/8.7.2) id RAA00236 for freebsd-current@freebsd.org; Sat, 23 Dec 1995 17:19:29 -0600 (CST) From: Kent Hamilton Message-Id: <199512232319.RAA00236@gwydion.hns.st-louis.mo.us> Subject: Kernel Panic in Current To: freebsd-current@freebsd.org Date: Sat, 23 Dec 1995 17:19:29 -0600 (CST) Reply-To: KentH@HNS.St-Louis.Mo.US X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk I'm able to re-produce this pretty much at will by connecting using usermode ppp to my service provider, then connecting to a remote machine that is connected to the same provider via a 14.4 modem and SLIP. # what /kernel /kernel FreeBSD 2.2-CURRENT #0: Fri Dec 22 19:38:47 CST 1995 I did the sup Thursday evening and a make world, then re-built the kernel on Friday. Trace Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xf0155004 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 proccessor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = kernel: type 18 trap, code = 0 Stopped at _tcp_timers+0x124: divl 0x28(%ebx),%eax db> trace _tcp_timers(f083c900,0) at _tcp_timers+0x124 _tcp_usrreq(f083ca00,13,0,0,0) at _tcp_usrreq+0x3fd _tcp_slowtimo(0,f0124968,f01f3fb8,f010bddc,0) at _tcp_slowtimo+0x6b _pfslowtimo(0) at _pfslowtimo+0x23 _softclock(80000000,10,10,0,f0830100) at _softclock+0x64 doreti_swi(0,f01becb0,11111111,22222222,33333333) at doreti_swi+0xf _cpu_switch(11111111,22222222,33333333,44444444,555555555) at _cpu_switch If I do a "panic" then "continue" then I get panic 12. Sorry don't have that one handy. -- Kent Hamilton Work: KHamilton@Hunter.COM URL: http://www.icon-stl.net/~khamilto Play: KentH@HNS.St-Louis.Mo.US From owner-freebsd-current Sat Dec 23 17:10:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA08199 for current-outgoing; Sat, 23 Dec 1995 17:10:24 -0800 (PST) Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA08192 for ; Sat, 23 Dec 1995 17:10:18 -0800 (PST) Received: (from mark@localhost) by linus.demon.co.uk (8.7.3/8.7.3) id BAA00749; Sun, 24 Dec 1995 01:10:50 GMT Message-Id: <199512240110.BAA00749@linus.demon.co.uk> From: mark@linus.demon.co.uk (Mark Valentine) Date: Sun, 24 Dec 1995 01:10:50 +0000 In-Reply-To: Kent Hamilton's message of Dec 23, 5:19pm X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: KentH@HNS.St-Louis.Mo.US, freebsd-current@FreeBSD.ORG Subject: Re: Kernel Panic in Current Sender: owner-current@FreeBSD.ORG Precedence: bulk > From: Kent Hamilton > Date: Sat 23 Dec, 1995 > Subject: Kernel Panic in Current > I'm able to re-produce this pretty much at will by connecting using > usermode ppp to my service provider, then connecting to a remote > machine that is connected to the same provider via a 14.4 modem and > SLIP. Garrett committed a fix for this recently - see sys/netinet/tcp_subr.c. * $Id: tcp_subr.c,v 1.25 1995/12/20 17:42:28 wollman Exp $ If you're up to date and still having problems, I can probably help you with a workaround... Cheers, Mark. From owner-freebsd-current Sat Dec 23 19:18:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA16409 for current-outgoing; Sat, 23 Dec 1995 19:18:14 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA16397 Sat, 23 Dec 1995 19:18:10 -0800 (PST) Message-Id: <199512240318.TAA16397@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) cc: Mark Murray , current@freebsd.org Subject: Re: Kerberos damaged in -current or my fault... In-reply-to: Your message of "Sun, 24 Dec 1995 00:24:37 +0300." Date: Sat, 23 Dec 1995 19:18:10 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org Precedence: bulk Oh, I almost forgot... Commit this fix to both branches once its tested. Thanks -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sat Dec 23 21:40:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA00528 for current-outgoing; Sat, 23 Dec 1995 21:40:30 -0800 (PST) Received: from gwydion.hns.st-louis.mo.us (root@dialup-66.icon-stl.net [199.217.153.66]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA00519 for ; Sat, 23 Dec 1995 21:40:26 -0800 (PST) Received: (from kenth@localhost) by gwydion.hns.st-louis.mo.us (8.7.3/8.7.2) id XAA00316; Sat, 23 Dec 1995 23:39:54 -0600 (CST) From: Kent Hamilton Message-Id: <199512240539.XAA00316@gwydion.hns.st-louis.mo.us> Subject: Re: Kernel Panic in Current To: mark@linus.demon.co.uk (Mark Valentine) Date: Sat, 23 Dec 1995 23:39:54 -0600 (CST) Cc: KentH@HNS.St-Louis.Mo.US, freebsd-current@FreeBSD.ORG In-Reply-To: <199512240110.BAA00749@linus.demon.co.uk> from "Mark Valentine" at Dec 24, 95 01:10:50 am Reply-To: KentH@HNS.St-Louis.Mo.US X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > > > > From: Kent Hamilton > > Date: Sat 23 Dec, 1995 > > Subject: Kernel Panic in Current > > > I'm able to re-produce this pretty much at will by connecting using > > usermode ppp to my service provider, then connecting to a remote > > machine that is connected to the same provider via a 14.4 modem and > > SLIP. > > Garrett committed a fix for this recently - see sys/netinet/tcp_subr.c. > > * $Id: tcp_subr.c,v 1.25 1995/12/20 17:42:28 wollman Exp $ > > If you're up to date and still having problems, I can probably help you > with a workaround... I'm current on it and I'm still getting the panic. I guess I'd like to get some info about the work-around since I consult for the person I'm connecting to and this is my way of getting in to do work. :-) -- Kent Hamilton Work: KHamilton@Hunter.COM URL: http://www.icon-stl.net/~khamilto Play: KentH@HNS.St-Louis.Mo.US From owner-freebsd-current Sat Dec 23 22:59:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06627 for current-outgoing; Sat, 23 Dec 1995 22:59:04 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA06622 for ; Sat, 23 Dec 1995 22:59:00 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (sendmail) id OAA13537 for freebsd-current@freebsd.org; Sun, 24 Dec 1995 14:58:54 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 24 Dec 1995 14:58:50 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <4bitna$d6q$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199512230435.PAA07671@godzilla.zeta.org.au>, <199512230438.UAA00172@corbin.Root.COM> Subject: Re: cvs fails to remove no-longer-present files Sender: owner-current@freebsd.org Precedence: bulk davidg@Root.COM (David Greenman) writes: >>The new cvs apparently has a bugfeature of checking out old things from >>the Attic when there are references to the old things in CVS/Entries >>This is inconsistent with the old cvs, and breaks ctm, which doesn't >>export CVS/*. > Oh! I haven't switched to using the new cvs yet...that explains it. > Peter? >-DG The death support code in the new cvs is getting tripped up because we are writing the repository with the old cvs. The new cvs creates the files in a way that is totally backwards compatable with the old cvs, but it's not perfect the other way around. With cvs-1.5 and later, the state of the file is stored in the state field: 1.1 date 94.06.22.06.57.25; author peter; state Exp; ^^^^^^^^^^ Since files can now be added and removed over and over again without having Attic conflicts, the new cvs has to go purely on the "state" of the revision it is dealing with rather than the global "Attic" state. Specifically... Under old cvs, if somebody does a 'cvs rm' on a file on the HEAD, it is moved to the Attic - this is a global change. If you do an 'cvs update -r yesterday' your tree will no longer build because the file was not recovered. However, with the new cvs writing the repository, this does exactly what you'd expect.. If you did an 'update -r yesterday' (and the file was only just removed), the file will reappear again. When you do the 'update -A' it will disappear again. This is useful for things like in -current at the moment, where i386/conf.c is about to be removed. Once it is gone, under the old cvs, it will no longer be possible to do a 'cvs update -r "december 1st"' and get a buildable system. The "fix" is to install cvs from -current on freefall. This is overdue.. I've just made the changes on freefall to enable it to be compiled there... -Peter From owner-freebsd-current Sat Dec 23 23:08:25 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA07657 for current-outgoing; Sat, 23 Dec 1995 23:08:25 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA07646 for ; Sat, 23 Dec 1995 23:08:22 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.1+2.6Wbeta4/3.3W9) with ESMTP id QAA00452 for ; Sun, 24 Dec 1995 16:08:19 +0900 (JST) Message-Id: <199512240708.QAA00452@marble.eps.nagoya-u.ac.jp> To: current@freebsd.org Subject: return value of ffs_blkpref() X-Mailer: Mew beta version 0.96 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 24 Dec 1995 16:08:18 +0900 From: KATO Takenori Sender: owner-current@freebsd.org Precedence: bulk The return value of ffs_blkpref() is checked in most cases like if (pref >= fs_fs_size) pref = 0; to avoid miserable destruction of file system (c.f. ffs_alloc() function). However, the value set in ffs_reallocblks() has never been checked. In this function, the value is set by [line 397 in ffs_alloc.c] pref = ffs_blkpref(ip, start_lbn, soff, sbap); Then, pref variable is used by [line 416 in ffs_alloc.c] if ((newblk = (daddr_t)ffs_hashalloc(ip, dtog(fs, pref), (long)pref, len, ffs_clusteralloc)) == 0) The ffs_hashalloc function calls ffs_clusteralloc() at [line 704 in ffs_alloc.c] result = (*allocater)(ip, cg, pref, size); But ffs_clusteralloc doesn't check pref is correct or not. Why doesn't this function test pref though other functions do? I think this may clobber the file system when pref points the non-existent block in last cylinder group. ---- KATO Takenori Dept. Earth Planet. Sci. Nagoya Univ. Nagoya 464-01 Voice: +81-52-789-2529 E-mail: kato@eclogite.eps.nagoya-u.ac.jp From owner-freebsd-current Sat Dec 23 23:26:58 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09446 for current-outgoing; Sat, 23 Dec 1995 23:26:58 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA09426 for ; Sat, 23 Dec 1995 23:26:50 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (sendmail) id PAA15204 for freebsd-current@freebsd.org; Sun, 24 Dec 1995 15:26:38 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 24 Dec 1995 15:25:59 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <4biva7$epv$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199512230438.UAA00172@corbin.Root.COM>, <199512230519.WAA07542@rocky.sri.MT.net> Subject: Re: cvs fails to remove no-longer-present files Sender: owner-current@freebsd.org Precedence: bulk In freebsd.current, Nate Williams writes: >> >The new cvs apparently has a bugfeature of checking out old things from >> >the Attic when there are references to the old things in CVS/Entries >> >This is inconsistent with the old cvs, and breaks ctm, which doesn't >> >export CVS/*. >> >> Oh! I haven't switched to using the new cvs yet...that explains it. >> Peter? >The new version of cvs removes files than the older binary (which is >still used on freefall). The new version of CVS has 'death-support', >which allows you to bring stuff in-out of the Repository w/out moving >things in/out of the Attic. I'm not sure how to fix this other than to >upgrade the version of CVS on freefall to the new version, and make sure >all the developers also upgrade to it at the same time. No need for developers to update.. The older cvs has absolutely no problems with files generated by the new cvs, once freefall is updated. The basic problem is that cvs-1.6 is storing extra information in the rcs files in a backward compatable way to say when a file is deleted. When the developer's cvs-1.6 binaries reading the rcs files, they are expecting the information to be there, and are not able to tell that it is missing. >(It would probably be good for the developers to upgrade to the newer >version of rcs as well) Yes.. I'll second this. The CVS installation notes suggest using diffutils-2.7 and rcs-5.7. Both are in our src/gnu/usr.bin tree. Cheers, -Peter >Nate