From owner-freebsd-hackers Thu Jan 1 00:11:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA29335 for hackers-outgoing; Thu, 1 Jan 1998 00:11:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from core.acroal.com (firewall0.acroal.com [209.24.61.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA29325 for ; Thu, 1 Jan 1998 00:11:38 -0800 (PST) (envelope-from freebsd@core.acroal.com) Received: from localhost (freebsd@localhost) by core.acroal.com (8.8.8/8.8.8) with SMTP id AAA01282; Thu, 1 Jan 1998 00:11:32 -0800 (PST) (envelope-from freebsd@core.acroal.com) Date: Thu, 1 Jan 1998 00:11:32 -0800 (PST) From: FreeBSD Hacker To: Adam Turoff cc: Atipa , freebsd-hackers Subject: RE: Informix on FreeBSD (maybe) (fwd) In-Reply-To: <34A97B63@smginc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Can someone explain to me what would be involved in implementing a database engine specifically for FreeBSD. How much work likely, if you were to work from scratch, and what kind of support would you want to offer for other platforms (i.e. Windoze). If it were specifically Tuned to be a high performance solution on a FreeBSD box and part of the Distribution, couldn't that just possibly attract the kind of High End contributions that FreeBSD needs? In essence if you were to clone a commercial database system which one would it be? From owner-freebsd-hackers Thu Jan 1 00:39:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA00404 for hackers-outgoing; Thu, 1 Jan 1998 00:39:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA00395 for ; Thu, 1 Jan 1998 00:39:08 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xnfxp-0002Tt-00; Thu, 1 Jan 1998 00:26:49 -0800 Date: Thu, 1 Jan 1998 00:26:42 -0800 (PST) From: Tom To: FreeBSD Hacker cc: Adam Turoff , Atipa , freebsd-hackers Subject: RE: Informix on FreeBSD (maybe) (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, 1 Jan 1998, FreeBSD Hacker wrote: > Can someone explain to me what would be involved in implementing a > database engine specifically for FreeBSD. How much work likely, if you ... Have your read the prior messages in this thread? Go and read the stuff from Simon Shapiro again, because he is using the PostgreSQL core for just that. Tom From owner-freebsd-hackers Thu Jan 1 01:09:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA01641 for hackers-outgoing; Thu, 1 Jan 1998 01:09:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA01637 for ; Thu, 1 Jan 1998 01:09:24 -0800 (PST) (envelope-from pjchilds@al.imforei.apana.org.au) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (beBop) id TAA19362; Thu, 1 Jan 1998 19:39:05 +1030 (CST) Date: Thu, 1 Jan 1998 19:39:05 +1030 (CST) From: Peter Childs Message-Id: <199801010909.TAA19362@al.imforei.apana.org.au> To: billwood@intcomm.net (William Wood), freebsd-hackers@FreeBSD.ORG Subject: Re: pptp In-Reply-To: <34833C08.5B230D62@intcomm.net> User-Agent: tin/pre-1.4-971224 (UNIX) (FreeBSD/2.2-STABLE (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In article <34833C08.5B230D62@intcomm.net> you wrote: > If anyone has any suggestions or ideas the following: > I would like to set up two servers (Freebsd) that would be connected via > the internet using PPTP. How can this be done or what is involve in > setting this up? Does it specifically have to be PPTP? I have used ppp (ijppp) over tcp/ip before so that one server appeared on another's local network via the internet. Pretty interesting stuff (see the ijppp manual if you find it). I've seen a tunneling implementation over IP using the tun devices as well (without the other stuff in ijppp) that Mark Newton wrote (newton@dotat.org) Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key From owner-freebsd-hackers Thu Jan 1 03:18:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA06614 for hackers-outgoing; Thu, 1 Jan 1998 03:18:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA06605 for ; Thu, 1 Jan 1998 03:18:35 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA25143 (5.67b/IDA-1.5 for freebsd-hackers@FreeBSD.ORG); Thu, 1 Jan 1998 12:19:01 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id KAA10709; Thu, 1 Jan 1998 10:54:45 +0100 (MET) From: Wilko Bulte Message-Id: <199801010954.KAA10709@yedi.iaf.nl> Subject: Re: mounting a FreeBSD partition on NetBSD or SunOS To: bsdean@gte.net Date: Thu, 1 Jan 1998 10:54:45 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199801010219.VAA04068@corona.unx.sas.com> from "Brian Dean" at Dec 31, 97 09:19:44 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk As Brian Dean wrote... > > I have a few questions about filesystems created by one Unix variant > and being mounting by another. > [del] > Thirdly, even if one could do one of the above, would the file system > be mountable? Is the byte-ordering between processor architectures > (big/little endian) an issue here, or are the file system structures > as they reside on the disk, portable across architectures? UFS is not portable between different architectures to the best of my knowledge. _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ---------------- Support your local daemons: run [Free,Net]BSD Unix ------ From owner-freebsd-hackers Thu Jan 1 03:18:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA06629 for hackers-outgoing; Thu, 1 Jan 1998 03:18:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA06612 for ; Thu, 1 Jan 1998 03:18:41 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA25145 (5.67b/IDA-1.5 for freebsd-hackers@FreeBSD.ORG); Thu, 1 Jan 1998 12:19:07 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id LAA11125; Thu, 1 Jan 1998 11:57:54 +0100 (MET) From: Wilko Bulte Message-Id: <199801011057.LAA11125@yedi.iaf.nl> Subject: Re: BT-542B fails with 2.2.5 (urgent) To: Stefan.Bethke@Hanse.DE (Stefan Bethke) Date: Thu, 1 Jan 1998 11:57:54 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Stefan Bethke" at Dec 31, 97 07:40:26 am X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk As Stefan Bethke wrote... > Sorry to bother you, > > I'm currently trying to upgrade a machine from 1.1.5.1 to 2.2.5. > > Unfortunatly, the BT-452B, which worked fine with 1.1.5.1 (using aha), > fails with 2.2.5-RELEASE. > > The card is probed successfully as aha, but as soon as sysinstall tries to > make a root fs, the kernel panics with "panic: I/O channel check, likely > hardware failure." Then, it either hangs on "syncing disks", or produces > yet another panic. Sounds like your bt (or some other I/O card...) is pulling on the IOCHK line on the ISA bus. This line is supposedly to be used in case the expansion board hardware detects an error. Dirty hack: the IOCHK line is the _last_ pad on the ISA connector, so the one closest to the metal mounting bracket. One side of the board/connector is ground, the other one is IOCHK. You could try some adhesive tape on the BT to see if the panic goes away.. So much for a hardware fix for (maybe) a sw problem ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ---------------- Support your local daemons: run [Free,Net]BSD Unix ------ From owner-freebsd-hackers Thu Jan 1 03:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA07858 for hackers-outgoing; Thu, 1 Jan 1998 03:59:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA07851 for ; Thu, 1 Jan 1998 03:59:22 -0800 (PST) (envelope-from avalon@coombs.anu.edu.au) Message-Id: <199801011159.DAA07851@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA169995900; Thu, 1 Jan 1998 22:58:20 +1100 From: Darren Reed Subject: Re: mounting a FreeBSD partition on NetBSD or SunOS To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Thu, 1 Jan 1998 22:58:20 +1100 (EDT) Cc: bsdean@gte.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199801010954.KAA10709@yedi.iaf.nl> from "Wilko Bulte" at Jan 1, 98 10:54:45 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In some mail from Wilko Bulte, sie said: > > As Brian Dean wrote... > > > > I have a few questions about filesystems created by one Unix variant > > and being mounting by another. I missed or delete the original, but anyway: /dev/wd0a 38991 30583 5289 85% / /dev/wd0s3f 347647 132834 187002 42% /usr /dev/wd0s3g 248175 112892 115429 49% /usr/local /dev/wd0s3h 198079 66882 115351 37% /usr/src /dev/wd0s3e 63567 11121 47361 19% /var procfs 4 4 0 100% /proc kernfs 1 1 0 100% /kern /dev/wd0s1 390864 333336 57528 85% /dos/c /dev/wd2s1 205380 78704 126676 38% /dos/d /dev/wd2s2a 29263 10858 16942 39% /netbsd /dev/wd2s2e 48463 25143 20897 55% /netbsd/var /dev/wd2s2f 175663 89254 77626 53% /netbsd/usr /dev/wd2s2g 96943 2776 89320 3% /netbsd/usr/local /dev/wd2s2h 230191 109871 108811 50% /netbsd/usr/src NetBSD can only deal with 1 BSD fdisk partition per disk, whereas FreeBSD can deal with multiple BSD fdisk partitions using slices. I only mount the NetBSD partitions read-only and when running NetBSD, mount the FreeBSD ones read-only. There are some subtle differences as to how the disklabels are organised, which can result in some error messages being dumped to the console when you mount them (I think that's when), depending on which versions of both operating systems are in use. Darren From owner-freebsd-hackers Thu Jan 1 04:20:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08495 for hackers-outgoing; Thu, 1 Jan 1998 04:20:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08490 for ; Thu, 1 Jan 1998 04:20:48 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id MAA17567; Thu, 1 Jan 1998 12:20:37 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199801011220.MAA17567@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0.1 12/23/97 To: Jacob Bohn Lorensen cc: Brian Somers , Duncan Barclay , hackers@FreeBSD.ORG Subject: Re: Revamping /etc/daily, weekly, monthly In-reply-to: Your message of "01 Jan 1998 03:48:29 +0100." <87afdg3o5d.fsf@pippin.jblhome.ping.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jan 1998 12:20:37 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > Brian Somers writes: > > > [.....] > > > # do daily/weekly/monthly maintenance > > > 0 2 * * * once periodic daily 2>&1 | sendmail root > > > 30 3 * * 6 once periodic weekly 2>&1 | sendmail root > > > 30 5 1 * * once periodic monthly 2>&1 | sendmail root > > [.....] > > > I like the idea, but the syntax is bad. It looks way too much like > > /etc/crontab - except with different meanings. > > I don't think I made myself clear. [.....] You did :^P I agree with your ideas, but what I'm saying is that /etc/crontab (as distinct from /var/cron/tabs/* has an extra 6th field - `who'. This looks very like your `once' field and would be rather confusing for someone comparing the two file formats. > -- > Jacob Lorensen; Mosebuen 33, 1.; DK-2820 Gentofte, Denmark; +45-31560401 > PGP ID = E596F0B5; PGP Fingerprint = 1E8726467436DC4A 723B6678C5AD9E71 -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jan 1 05:55:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA13984 for hackers-outgoing; Thu, 1 Jan 1998 05:55:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA13980 for ; Thu, 1 Jan 1998 05:55:36 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id NAA17928; Thu, 1 Jan 1998 13:54:35 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199801011354.NAA17928@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0.1 12/23/97 To: dg@root.com cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: load averages never decrease to 0 (FreeBSD 2.1.6) In-reply-to: Your message of "Wed, 31 Dec 1997 12:02:38 PST." <199712312002.MAA26043@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jan 1998 13:54:35 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > >[.....] > >> I have my laptop running 60 ppp processes - all idle - for the last > >> couple of days. The load average tapers out at exactly 1.0. It's a > >> P120 w/ 40Mb of memory running 2.2-stable from about 3 days ago. > >[.....] > > > >I take that back. It's now running at exactly 5.0 ! Nothing else > >(except the 60 ppps) is running ????????? > > The code that calculates the load average is very simple and can be found > in /sys/vm/vm_meter.c. You should be able to take the output of 'ps' and > determine why it is that the code is getting it wrong. It's not really that simple, is it ? For example, updatepri() in kern_synch.c adjusts p_slptime based on the load average.... All of the ppp processes are ``Ss'' (sleeping session leaders), and always blocked in `select' according to ps -l. > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jan 1 05:56:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA14040 for hackers-outgoing; Thu, 1 Jan 1998 05:56:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA14035 for ; Thu, 1 Jan 1998 05:56:16 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id MAA17683; Thu, 1 Jan 1998 12:42:58 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199801011242.MAA17683@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0.1 12/23/97 To: Julian Elischer cc: Brian Somers , Joao Carlos Mendes Luis , nrice@emu.sourcee.com, mdukhan@bis.co.il, freebsd-hackers@FreeBSD.ORG, mdukhan@quasi.bis.co.il Subject: Re: load averages never decrease to 0 (FreeBSD 2.1.6) In-reply-to: Your message of "Wed, 31 Dec 1997 12:49:38 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jan 1998 12:42:58 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > don't forget to count every process that is in 'D' state. The system's unloaded (and now at 4.0 - was 7.0 this morning). I don't expect much disk activity at all. The only `guess' I'd make is that the number should be somewhere between 1.0 and 6.0 because of the clock granularity making the setitimer stuff SIGALRM at the same time. But, of course this completely fails to take into account the PPro200 (-current from a week ago) that's running 40 ppp processes (for a long time) and is now at a load average of 0.00 ! According to getloadavg(3), the number of processes in the run queue is what's being measured. Does this mean that the PPro is so fast at getting things out of the run queue that it averages at less than 0.01 ? So I up the PPro so that there's 100 ppp processes running. Now, I see a load of 0.01..... ha. The number of `running processes' just below it is somewhere between 4 and 25. The number of `running' processes according to top on the laptop is between about 1 and 10 (load average exactly 10.0 now). I'll have a look at the how this stuff is worked out a bit closer. There's definitely something weird happening - or at least something I don't understand. > On Wed, 31 Dec 1997, Brian Somers wrote: > > > [.....] > > > I have my laptop running 60 ppp processes - all idle - for the last > > > couple of days. The load average tapers out at exactly 1.0. It's a > > > P120 w/ 40Mb of memory running 2.2-stable from about 3 days ago. > > [.....] > > > > I take that back. It's now running at exactly 5.0 ! Nothing else > > (except the 60 ppps) is running ????????? -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jan 1 08:18:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA18572 for hackers-outgoing; Thu, 1 Jan 1998 08:18:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA18559 for ; Thu, 1 Jan 1998 08:18:30 -0800 (PST) (envelope-from dmlb@ragnet.demon.co.uk) Received: from ragnet.demon.co.uk ([158.152.46.40]) by post.mail.demon.net id aa2010767; 1 Jan 98 16:13 GMT Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.73 #1) id 0xnn3m-0003M9-00; Thu, 1 Jan 1998 16:01:26 +0000 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <87pvmdaal0.fsf@pippin.jblhome.ping.dk> Date: Thu, 01 Jan 1998 15:45:50 -0000 (GMT) From: Duncan Barclay To: Jacob Bohn Lorensen Subject: Re: Revamping /etc/daily, weekly, monthly Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk >Duncan Barclay writes: > >> For some while I have been unhappy with the way the daily/weekly/monthly >> scripts work. > Interesting, it seems that my orginal proposal has forked into a different realm... On 31-Dec-97 Jacob Bohn Lorensen wrote: >I have long been toying with the idea of modifying cron instead to >support non-24/7 machines. What I propose is to add an additional >field, ``catchup-on-startup'' or whatever, which, if set, would cause >cron to execute programs it would have executed if it had been on, at >startup. I.e.: > ># do daily/weekly/monthly maintenance >0 2 * * * once periodic daily 2>&1 | sendmail root >30 3 * * 6 once periodic weekly 2>&1 | sendmail root >30 5 1 * * once periodic monthly 2>&1 | sendmail root > >Would behave no differently on 24/7 machines. However, if the machine >is off for some time (be it hours, days, weeks, ...) when cron comes >up again, it will look at a time-stamp file to find out when the last >cron job was run. Then it will quickly time-travel to the current >time, executing everything it would-have executed. There should >possibly be a way to flag entries as [snip] > >What do you think of this idea? Seems good for addressing the problem of non 24/7 machines, although I think that David Kelly's version is probably better... > Rather than altering cron and the crontab format why not write some > external function(s) to perform the tasks with similar syntax to the > suggestion at the top. Lets start with a program we'll call "periodic" > and apply it like this to root's crontab: > > 0 2 * * * root periodic /etc/daily 2>&1 | sendmail > root > > When run periodic invokes the rest of the command line. And logs the > fact somewhere, perhaps /var/run/periodic. > [snip] The cron/boot time arguments are not exactly what I was addressing, though. I want to clean up the daily/weekly/monthly scripts themselves and make them more configurable. To this end I have started work on bev (named after my cleaner). bev itself is just a concatenation of the daily/weekly/monthly scripts, slightly re-ordered into sections with similar functionality. Each action has a guard configured using this file: # # $Id: bev.conf,v 1.1 1997/12/31 13:14:25 dmlb Exp $ # # Configuration for bev, the system cleaner. This file # is read into a shell script. # # Each pair of variables determines when an action is run. The # first variable can take any value, the action is executed # if the bev is invoked with that value as its first argument. # The second variable (with the _boot suffix) can be used to invoke # an action at boot time. # # Eg. # # clean_var.preserve= daily # clean_var.preserve_boot= yes # # invokes an action to clean up /var/preserve when bev is run as # /etc/bev daily. Also the clean up is run when the machine is booted. # # Typical values for when an action is to be run are: # daily weekly monthly boot none local # The first three are used by cron(1) invoked runs of bev. "boot" is # used to invoke bev from /etc/rc and "none" is used if bev is invoked # with no arguments. The _boot variables should be set to one of # yes no # clean_var.preserve= daily clean_var.preserve_boot= yes clean_var.rhwo= daily clean_var.rwho_boot= yes and the root crontab would now be # do daily/weekly/monthly maintenance 0 2 * * * bev daily 2>&1 | sendmail root 30 3 * * 6 bev weekly 2>&1 | sendmail root 30 5 1 * * bev monthly 2>&1 | sendmail root and /etc/rc would have /etc/bev boot somewhere. I think that the catchup/periodic bits for cron are orthogonal to bev, so I will not add this functionality to bev itself. Duncan PS. I read hackers via the digest but I havent seen one since 28/12 so forgive me if I am a bit late in seeing all of this. --- _______________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ From owner-freebsd-hackers Thu Jan 1 08:25:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19149 for hackers-outgoing; Thu, 1 Jan 1998 08:25:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA19145 for ; Thu, 1 Jan 1998 08:25:34 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id RAA26404 for hackers@FreeBSD.ORG; Thu, 1 Jan 1998 17:25:24 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id QAA05711; Thu, 1 Jan 1998 16:48:04 +0100 (CET) (envelope-from roberto) Message-ID: <19980101164804.30732@keltia.freenix.fr> Date: Thu, 1 Jan 1998 16:48:04 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: FreeBSD ELF status? References: <199712311722.JAA19985@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199712311722.JAA19985@austin.polstra.com>; from John Polstra on Wed, Dec 31, 1997 at 09:22:57AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3930 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk According to John Polstra: > Everybody who was working on it got very busy with paywork, so there > hasn't been much progress lately. We still have hopes of having it > ready for 3.0-RELEASE, but time will tell whether that will work out > or not. The primary obstacle remaining is The Migration Problem. After giving some thoughts on the subject, here is what I got: - we must put into the source various tools such as binutils & gcc (preferably egcs or pgcc IMO) before. That is a very big increase of the tree size. - after that, we must decide if we want to converted system to be able to generate a.out binaries or not. That's the main issue I guess. The former is much more difficult to handle because that would mean keeping two versions of too many things in the tree and it is probably a nightmare. The latter greatly simplify (:-)) the process because I see the bootstrapping as an added phase before making the world. make bootstrap would compile the libs new gcc/binutils as crosscompiling tools generating i386-unknown-freebsdelf files and installing them inside /usr/obj/.../tmp. make world then takes theses tools and compile the world the usual way, recompiling the new tools as normal ELF binaries. We'd need to generate a compat-a.out.tgz tree with the "old" tools (ld.so, all libs and so on) to let people runing old binaries (CURRENT is less of an issue here). /usr/lib/aout ? /usr/lib/i386-unknown-freebsd ? Considering the boot blocks size issue, it is more of an all or nothing thing because if we want to boot our shiny new kernel, we need the new boot blocks. If someone can do the Mithical 3-Stage Bootblock, it would be easier (no I'm not volunteering :-)). - next phase is getting rid of the old tools' sources from the tree (my modem has started sweating at the CTM delta size :-). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #21: Sat Dec 27 06:10:06 CET 1997 From owner-freebsd-hackers Thu Jan 1 08:36:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19606 for hackers-outgoing; Thu, 1 Jan 1998 08:36:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA19602; Thu, 1 Jan 1998 08:36:37 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id NAA17803; Thu, 1 Jan 1998 13:25:33 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199801011325.NAA17803@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0.1 12/23/97 To: John-Mark Gurney cc: freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG, joerg@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point In-reply-to: Your message of "Wed, 31 Dec 1997 17:30:01 PST." <199801010130.RAA10049@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jan 1998 13:25:32 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk [cc'd to joerg and freebsd-hackers] > The following reply was made to PR kern/5404; it has been noted by GNATS. > > From: John-Mark Gurney > To: Matthew Dillon > Cc: FreeBSD-gnats-submit@FreeBSD.ORG > Subject: Re: kern/5404: slXX slip interfaces always point to point > Date: Wed, 31 Dec 1997 17:23:58 +875200 > [.....] > or are you wanting to do something like: > > +-------------+ +-------------+ > | machine a |-------| machine b |---- rest of 192.168.3.x > | 192.168.3.2 | | 192.168.3.1 | > +-------------+ +-------------+ > > and trying to get machine a on the same network as machine b? > > if your going for the second one, you need proxyarp on machine b... > I've actually done something similar to this before... actually my > terminal server is setup like that... the ethernet is 192.168.0.x.. and > the ip's for the dialin's are 192.168.40-60 or so... [.....] This ties in with a recent discussion on -hackers: > Brian Somers wrote: > > > I agree, and I'll implement the change unless someone has a good > > reason not to..... any takers ? > > I think it's really best to just not display the netmask in the output > of ifconfig iff IFF_POINTOPOINT is set. > > Routes to the remote end apart from the implied host route seem to be > dangerous to me, and they break the current behaviour (i.e. could > cause surprises for people who are used to how it's done now). It's > not always that the IP address of the remote end is indeed identical > with the remote network address. > > -- > cheers, J"org I intended to remove the possibility of netmasks and broadcast addresses for pointopoint links, but retrospectively, this will break the ability to attach to a peer that proxy arps for you (well, it's already broken). I would suggest (and I'm willing to do it) adding the ability to use SIOCSIFPOINTOPOINT and SIOCGIFPOINTOPOINT on sl* ppp* and tun*. The default is that these interfaces are pointopoint, but you can change that by issuing the `S' ioctl. Additionally, I'd change ifconfig so that it doesn't display a netmask & broadcast address when the POINTOPOINT flag is set. I can then implement the ability to make these interfaces non-pointopoint in their respective programs - if configured that way. None of the existing code would break as the defaults are the same. Comments ? -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jan 1 08:46:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA20173 for hackers-outgoing; Thu, 1 Jan 1998 08:46:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from androcles.com (dhh@androcles.com [204.57.240.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA20169 for ; Thu, 1 Jan 1998 08:46:23 -0800 (PST) (envelope-from alex@androcles.com) Received: (from dhh@localhost) by androcles.com (8.8.7/8.8.7) id IAA08247; Thu, 1 Jan 1998 08:46:11 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <87afdg3o5d.fsf@pippin.jblhome.ping.dk> Date: Thu, 01 Jan 1998 08:31:29 -0800 (PST) From: "Duane H. Hesser" To: Jacob Bohn Lorensen Subject: Re: Revamping /etc/daily, weekly, monthly Cc: hackers@FreeBSD.ORG, Duncan Barclay , Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk The Vixie cron, as distributed with FreeBSD, already has a syntax for periodic command execution. Although the syntax is not described in the Freebsd manual pages for cron, I've check the sources, and...it's in there. Specifically, you get @reboot @hourly @daily @weekly @monthly @yearly @reboot runs commands at restart of cron, which is not precisely the same as system reboot, but is close enough. I've used this for some years, and it's manageable. All of these specs (except "@reboot") run their commands at midnight (Vixie's comments indicate a strong desire to avoid a "cron.conf" file, which seems a reasonable goal). This may not appeal to some (although I like it), but it would not be difficult to alter the source to stagger them a bit. You can check this out in /usr/src/usr.sbin/cron/lib/entry.c to see if this does what you want to do. -------------- Duane H. Hesser dhh@androcles.com From owner-freebsd-hackers Thu Jan 1 09:19:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21917 for hackers-outgoing; Thu, 1 Jan 1998 09:19:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21896 for ; Thu, 1 Jan 1998 09:18:58 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id SAA24583; Thu, 1 Jan 1998 18:18:25 +0100 (MET) (envelope-from sos) Message-Id: <199801011718.SAA24583@sos.freebsd.dk> Subject: Re: FreeBSD ELF status? In-Reply-To: <19980101164804.30732@keltia.freenix.fr> from Ollivier Robert at "Jan 1, 98 04:48:04 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Thu, 1 Jan 1998 18:18:25 +0100 (MET) Cc: hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In reply to Ollivier Robert who wrote: > According to John Polstra: > > Everybody who was working on it got very busy with paywork, so there > > hasn't been much progress lately. We still have hopes of having it > > ready for 3.0-RELEASE, but time will tell whether that will work out > > or not. The primary obstacle remaining is The Migration Problem. > > After giving some thoughts on the subject, here is what I got: > > - we must put into the source various tools such as binutils & gcc > (preferably egcs or pgcc IMO) before. That is a very big increase of the > tree size. We don't need a new compiler, the gcc in the tree allready has all it needs to make ELF bins. Binutils is needed for the assembler, linker and misc utils. > - after that, we must decide if we want to converted system to be able to > generate a.out binaries or not. Hmm, the way I have had it working here, is that you set an environment var to tell the compilersystem & utils what bin type you want, ELF being the default. > That's the main issue I guess. The former is much more difficult to > handle because that would mean keeping two versions of too many things in > the tree and it is probably a nightmare. No not really, its only binutils that gets pulled in (and only parts of it is really needed. Since the GNU shi^H^Htuff is kept in its own part of the tree no real probelms arise from that. > The latter greatly simplify (:-)) the process because I see the > bootstrapping as an added phase before making the world. Hold your horses :), its not completely that easy, but a special target could do the transition one and for all. > We'd need to generate a compat-a.out.tgz tree with the "old" tools > (ld.so, all libs and so on) to let people runing old binaries (CURRENT is > less of an issue here). /usr/lib/aout ? /usr/lib/i386-unknown-freebsd ? /usr/lib/aout for the libs, or jump the major# to signify a new format... /usr/libexec/aout for the old aout utils still needed, if any at all... > - next phase is getting rid of the old tools' sources from the tree (my > modem has started sweating at the CTM delta size :-). Well, its not much we can get rid off (strip, nm, ranlib and stuff), the compiler is the same (No I dont think we should switch to a new compiler just now, and especially not when doing this kind of "workout"), we still need the old rtld, to run older bins etc, and some might want then around just in case... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Jan 1 09:52:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA25217 for hackers-outgoing; Thu, 1 Jan 1998 09:52:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA25185; Thu, 1 Jan 1998 09:51:51 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id SAA26371; Thu, 1 Jan 1998 18:51:39 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id SAA17185; Thu, 1 Jan 1998 18:50:08 +0100 (MET) Message-ID: <19980101185007.59283@uriah.heep.sax.de> Date: Thu, 1 Jan 1998 18:50:07 +0100 From: J Wunsch To: Brian Somers Cc: John-Mark Gurney , freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point Reply-To: Joerg Wunsch References: <199801010130.RAA10049@hub.freebsd.org> <199801011325.NAA17803@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199801011325.NAA17803@awfulhak.demon.co.uk>; from Brian Somers on Thu, Jan 01, 1998 at 01:25:32PM +0000 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk As Brian Somers wrote: > I intended to remove the possibility of netmasks and broadcast > addresses for pointopoint links, but retrospectively, this will break > the ability to attach to a peer that proxy arps for you (well, it's > already broken). Why? Proxyarping is done on the Ethernet interface, and this one still has a netmask. > I would suggest (and I'm willing to do it) adding the ability to use > SIOCSIFPOINTOPOINT and SIOCGIFPOINTOPOINT on sl* ppp* and tun*. The > default is that these interfaces are pointopoint, but you can change > that by issuing the `S' ioctl. Nope, you can't. `p2p' is an unchangeable attribute of an interface, see IFF_CANTCHANGE in /sys/net/if.h. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 1 10:15:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27101 for hackers-outgoing; Thu, 1 Jan 1998 10:15:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27096 for ; Thu, 1 Jan 1998 10:15:06 -0800 (PST) (envelope-from witr@spooky.rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id NAA24691 for ; Thu, 1 Jan 1998 13:15:08 -0500 (EST) (envelope-from witr@spooky.rwwa.com) Message-Id: <199801011815.NAA24691@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@FreeBSD.ORG Subject: Linux rvplayer and not-implemented ioctl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jan 1998 13:15:08 -0500 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Trying to run the 5.0 version of thelinux rvplayer causes: LINUX: 'ioctl' fd=7, typ=0x450(P), num=0xf not implemented Is this a problem with FreeBSD or the Sound driver, or what? --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM From owner-freebsd-hackers Thu Jan 1 10:22:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27570 for hackers-outgoing; Thu, 1 Jan 1998 10:22:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27559; Thu, 1 Jan 1998 10:21:45 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id SAA19774; Thu, 1 Jan 1998 18:19:50 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199801011819.SAA19774@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0.1 12/23/97 To: Joerg Wunsch cc: Brian Somers , John-Mark Gurney , freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point In-reply-to: Your message of "Thu, 01 Jan 1998 18:50:07 +0100." <19980101185007.59283@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jan 1998 18:19:50 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > As Brian Somers wrote: > > > I intended to remove the possibility of netmasks and broadcast > > addresses for pointopoint links, but retrospectively, this will break > > the ability to attach to a peer that proxy arps for you (well, it's > > already broken). > > Why? Proxyarping is done on the Ethernet interface, and this one > still has a netmask. I mean in the sense that the client cannot broadcast on the network at the other end of the pointopoint link, or can it ? I guess you could set up a static route for the broadcast address. That should work. I haven't tried. > > I would suggest (and I'm willing to do it) adding the ability to use > > SIOCSIFPOINTOPOINT and SIOCGIFPOINTOPOINT on sl* ppp* and tun*. The > > default is that these interfaces are pointopoint, but you can change > > that by issuing the `S' ioctl. > > Nope, you can't. `p2p' is an unchangeable attribute of an interface, > see IFF_CANTCHANGE in /sys/net/if.h. Perhaps IFF_POINTOPOINT should be settable while the interface is down only. In the `tun' case (I'm not sure about pppX & slX) it could be done at the ioctl(TUNSIFINFO) stage - the `dummy' part of the struct tuninfo could be changed to specify the interface flags. But this would break existing code that never initialises `dummy' to zero (which, it really should, although ppp doesn't :-(). OpenBSD already has this requirement. The `dummy' part is replaced by `flags' and those flags must specify IFF_POINTOPOINT if you want that. I'm not actually sure what happens there if you don't specify IFF_POINTOPOINT. > -- > 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. ;-) -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jan 1 11:51:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03827 for hackers-outgoing; Thu, 1 Jan 1998 11:51:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03802; Thu, 1 Jan 1998 11:51:14 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA27805; Thu, 1 Jan 1998 20:51:01 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id UAA17876; Thu, 1 Jan 1998 20:30:25 +0100 (MET) Message-ID: <19980101203024.48956@uriah.heep.sax.de> Date: Thu, 1 Jan 1998 20:30:24 +0100 From: J Wunsch To: Brian Somers Cc: John-Mark Gurney , freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point Reply-To: Joerg Wunsch References: <19980101185007.59283@uriah.heep.sax.de> <199801011819.SAA19774@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199801011819.SAA19774@awfulhak.demon.co.uk>; from Brian Somers on Thu, Jan 01, 1998 at 06:19:50PM +0000 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk As Brian Somers wrote: > > Why? Proxyarping is done on the Ethernet interface, and this one > > still has a netmask. > > I mean in the sense that the client cannot broadcast on the network > at the other end of the pointopoint link, or can it ? Broadcast relaying is IMHO not supported. > could set up a static route for the broadcast address. That should > work. I haven't tried. Hmm, maybe this would work. > > Nope, you can't. `p2p' is an unchangeable attribute of an interface, > > see IFF_CANTCHANGE in /sys/net/if.h. > > Perhaps IFF_POINTOPOINT should be settable while the interface is > down only. Why? After all, this interface _is_ point-to-point. Allowing to change this from userland is stupid. Maybe allowing it for tunX would make sense under some circumstances, but running PPP over it really mandates it to have IFF_POINTOPOINT set. ProxyARP itself is already a big hack i would discourage except of a few cases. Don't give the people the feeling they could solve all their problems by proxyarping half of the Internet. :) We should rather encourage people in setting up a clean routing than in setting up hack^2's. (Btw., the worst i've seen so far is HP's internal network. This is just one big hack, at least the part i've seen.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Jan 1 12:20:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA05370 for hackers-outgoing; Thu, 1 Jan 1998 12:20:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd1.cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA05057 for ; Thu, 1 Jan 1998 12:14:58 -0800 (PST) (envelope-from jb@freebsd1.cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.8.7/8.8.7) id HAA00256 for hackers@freebsd.org; Fri, 2 Jan 1998 07:20:18 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199801012020.HAA00256@freebsd1.cimlogic.com.au> Subject: Sendmail on 2.2.5R To: hackers@FreeBSD.ORG Date: Fri, 2 Jan 1998 07:20:17 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk G'day, Since upgrading a system the other day from 2.2.2 to 2.2.5 I'm seeing sendmail dropping incoming messages from one particular mail relay. I don't think that the relay configuration has changed, so I'm guessing that there is something wrong at my end (of course 8-). Sendmail writes a "from=" message to the mail log with size=0, class=0, pri=0, nrcpts=0, proto=SMTP. The sendmail.cf I am using is the one from the 2.2.5R CD with the DM entry changed to my domain. The FreeBSD mail messages come with proto=ESMTP and they work OK. Anyone (a) having a problem like this; or (b) know what to do about it? Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 From owner-freebsd-hackers Thu Jan 1 12:36:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06130 for hackers-outgoing; Thu, 1 Jan 1998 12:36:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (slip-33.acadiau.ca [131.162.2.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA05856 for ; Thu, 1 Jan 1998 12:31:34 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id QAA23111; Thu, 1 Jan 1998 16:31:02 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 1 Jan 1998 16:31:02 -0400 (AST) From: The Hermit Hacker To: FreeBSD Hacker cc: Adam Turoff , Atipa , freebsd-hackers Subject: RE: Informix on FreeBSD (maybe) (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, 1 Jan 1998, FreeBSD Hacker wrote: > > > Can someone explain to me what would be involved in implementing a > database engine specifically for FreeBSD. How much work likely, if you > were to work from scratch, and what kind of support would you want to > offer for other platforms (i.e. Windoze). If it were specifically Tuned > to be a high performance solution on a FreeBSD box and part of the > Distribution, Why would you want to start from scratch? There are at least two out there that are already built, and just recently Redhat has begun including PostgreSQL as part of its standard distribution *shrug* Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-hackers Thu Jan 1 13:37:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA10492 for hackers-outgoing; Thu, 1 Jan 1998 13:37:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ginseng.indigo.ie (ts01-13.waterford.indigo.ie [194.125.139.44]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA10479 for ; Thu, 1 Jan 1998 13:36:57 -0800 (PST) (envelope-from rotel@indigo.ie) Received: (qmail 497 invoked by uid 1000); 1 Jan 1998 21:40:59 -0000 Message-ID: <19980101214059.496.qmail@ginseng.indigo.ie> From: "Niall Smart" Date: Thu, 1 Jan 1998 21:40:58 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-hackers@FreeBSD.ORG Subject: Installing -current and -stable on the same disk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Hi, I'm interested in installing -current and -stable on the same disk. But around lines 901 of release/sysinstall/label.c: if ((flags & CHUNK_IS_ROOT)) { if (!(label_chunk_info[here].c->flags & CHUNK_BSD_COMPAT)) { msgConfirm("This region cannot be used for your root partition as the\n" "FreeBSD boot code cannot deal with a root partition created\n" "in that location. Please choose another location or smaller\n" "size for your root partition and try again!"); I understand that the BSD_COMPAT flag is set for the first FreeBSD fdisk partition. Is that correct? Is there anyway to install -current and -stable on the same disk, apart from using fdisk to hide one from the other in between reboots? Thanks Niall From owner-freebsd-hackers Thu Jan 1 14:00:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12122 for hackers-outgoing; Thu, 1 Jan 1998 14:00:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA12109 for ; Thu, 1 Jan 1998 14:00:45 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id WAA04378; Thu, 1 Jan 1998 22:58:44 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199801012158.WAA04378@ocean.campus.luth.se> Subject: Re: Sendmail on 2.2.5R In-Reply-To: <199801012020.HAA00256@freebsd1.cimlogic.com.au> from John Birrell at "Jan 2, 98 07:20:17 am" To: jb@freebsd1.cimlogic.com.au (John Birrell) Date: Thu, 1 Jan 1998 22:58:44 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk According to John Birrell: > G'day, > > Since upgrading a system the other day from 2.2.2 to 2.2.5 I'm seeing > sendmail dropping incoming messages from one particular mail relay. > I don't think that the relay configuration has changed, so I'm guessing > that there is something wrong at my end (of course 8-). > > Sendmail writes a "from=" message to the mail log with > size=0, class=0, pri=0, nrcpts=0, proto=SMTP. The sendmail.cf I am > using is the one from the 2.2.5R CD with the DM entry changed to > my domain. The FreeBSD mail messages come with proto=ESMTP and they > work OK. > > Anyone (a) having a problem like this; or (b) know what to do about it? I really have no idea, but just so you get a quick answer for a _possible_ error: Might it have something to do with the new anti-spam rules? They reject mail that comes from non existing domains, I believe. /Mikael From owner-freebsd-hackers Thu Jan 1 14:51:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA15379 for hackers-outgoing; Thu, 1 Jan 1998 14:51:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA15370 for ; Thu, 1 Jan 1998 14:51:31 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id OAA05583; Thu, 1 Jan 1998 14:51:37 -0800 (PST) To: "Niall Smart" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Installing -current and -stable on the same disk In-reply-to: Your message of "Thu, 01 Jan 1998 21:40:58 GMT." <19980101214059.496.qmail@ginseng.indigo.ie> Date: Thu, 01 Jan 1998 14:51:37 -0800 Message-ID: <5580.883695097@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > I understand that the BSD_COMPAT flag is set for the first FreeBSD fdisk > partition. Is that correct? Is there anyway to install -current and > -stable on the same disk, apart from using fdisk to hide one from the > other in between reboots? Nope. The boot code will find and boot from the first 0xa5 type partition found. Jordan From owner-freebsd-hackers Thu Jan 1 14:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA15752 for hackers-outgoing; Thu, 1 Jan 1998 14:54:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA15694 for ; Thu, 1 Jan 1998 14:54:40 -0800 (PST) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 6057 invoked by uid 1000); 1 Jan 1998 22:53:00 -0000 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 01 Jan 1998 14:52:59 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: FreeBSD Hacker Subject: RE: Informix on FreeBSD (maybe) (fwd) Cc: freebsd-hackers , Atipa , Adam Turoff Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On 01-Jan-98 FreeBSD Hacker wrote: > > > Can someone explain to me what would be involved in implementing a > database engine specifically for FreeBSD. How much work likely, if you > were to work from scratch, and what kind of support would you want to > offer for other platforms (i.e. Windoze). If it were specifically Tuned > to be a high performance solution on a FreeBSD box and part of the > Distribution, couldn't that just possibly attract the kind of High End > contributions that FreeBSD needs? > > In essence if you were to clone a commercial database system which one > would it be? IMJO, enormous amount of work. In my work, we just add some clearly defined subsystems to an existing product and it represents several engineering years of effort. There is really no need to do all that, I think; There is a pretty good engine out there that is lacking in specific areas which we are already addressing. There may be others. Were there enough interest in our work, we could generalize it so other RDBMS engines could enjoy the benefits too. Doing the reverse is very tricky; O/S specific changes are inherently non-portable (TerrY?). But we are trying to be as clean as we can. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-hackers Thu Jan 1 15:10:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17270 for hackers-outgoing; Thu, 1 Jan 1998 15:10:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ginseng.indigo.ie (ts02-05.waterford.indigo.ie [194.125.139.52]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA17258 for ; Thu, 1 Jan 1998 15:10:34 -0800 (PST) (envelope-from rotel@indigo.ie) Received: (qmail 1119 invoked by uid 1000); 1 Jan 1998 23:13:13 -0000 Message-ID: <19980101231313.1118.qmail@ginseng.indigo.ie> From: "Niall Smart" Date: Thu, 1 Jan 1998 23:13:12 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-hackers@FreeBSD.ORG Subject: getopt(3) and numeric arguments Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Hi, The getopt(3) man page says: It is also possible to handle digits as option letters. This allows getopt() to be used with programs that expect a number (``-3'') as an op- tion. This practice is wrong, and should not be used in any current de- velopment. It is provided for backward compatibility only. Is this correct? Whats so bad about it? Niall From owner-freebsd-hackers Thu Jan 1 15:18:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17939 for hackers-outgoing; Thu, 1 Jan 1998 15:18:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ginseng.indigo.ie (ts02-05.waterford.indigo.ie [194.125.139.52]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA17935 for ; Thu, 1 Jan 1998 15:18:26 -0800 (PST) (envelope-from rotel@indigo.ie) Received: (qmail 1367 invoked by uid 1000); 1 Jan 1998 23:22:40 -0000 Message-ID: <19980101232240.1366.qmail@ginseng.indigo.ie> From: "Niall Smart" Date: Thu, 1 Jan 1998 23:22:40 +0000 In-Reply-To: "Jordan K. Hubbard" "Re: Installing -current and -stable on the same disk" (Jan 1, 2:51pm) X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: "Jordan K. Hubbard" Subject: Re: Installing -current and -stable on the same disk Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Jan 1, 2:51pm, "Jordan K. Hubbard" wrote: } Subject: Re: Installing -current and -stable on the same disk > > I understand that the BSD_COMPAT flag is set for the first FreeBSD fdisk > > partition. Is that correct? Is there anyway to install -current and > > -stable on the same disk, apart from using fdisk to hide one from the > > other in between reboots? > > Nope. The boot code will find and boot from the first 0xa5 type > partition found. Crap :( Is this (silly) limitation restricted to the boot code only or do you know if it has been made in many places? Niall From owner-freebsd-hackers Thu Jan 1 15:27:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18487 for hackers-outgoing; Thu, 1 Jan 1998 15:27:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18234 for ; Thu, 1 Jan 1998 15:21:52 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id JAA03317; Fri, 2 Jan 1998 09:44:37 +1030 (CST) Message-Id: <199801012314.JAA03317@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Robert Withrow cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Linux rvplayer and not-implemented ioctl In-reply-to: Your message of "Thu, 01 Jan 1998 13:15:08 CDT." <199801011815.NAA24691@spooky.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Jan 1998 09:44:35 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > Trying to run the 5.0 version of thelinux rvplayer causes: > > LINUX: 'ioctl' fd=7, typ=0x450(P), num=0xf not implemented > > Is this a problem with FreeBSD or the Sound driver, or what? FreeBSD 1.1 doesn't support Linux sound ioctls. Or are you running a later release? (HINT) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ From owner-freebsd-hackers Thu Jan 1 16:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22234 for hackers-outgoing; Thu, 1 Jan 1998 16:27:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22194; Thu, 1 Jan 1998 16:25:54 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id KAA16092; Fri, 2 Jan 1998 10:55:06 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA27236; Fri, 2 Jan 1998 10:55:05 +1030 (CST) (envelope-from grog) Message-ID: <19980102105504.61189@lemis.com> Date: Fri, 2 Jan 1998 10:55:04 +1030 From: Greg Lehey To: Brian Somers Cc: John-Mark Gurney , freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG, joerg@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point References: <199801010130.RAA10049@hub.freebsd.org> <199801011325.NAA17803@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.84e In-Reply-To: <199801011325.NAA17803@awfulhak.demon.co.uk>; from Brian Somers on Thu, Jan 01, 1998 at 01:25:32PM +0000 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, Jan 01, 1998 at 01:25:32PM +0000, Brian Somers wrote: > [cc'd to joerg and freebsd-hackers] > >> From: John-Mark Gurney (according to the >> message, but the signature looks more like Jörg Wunsch. > >> Brian Somers wrote: >> >>> I agree, and I'll implement the change unless someone has a good >>> reason not to..... any takers ? >> >> I think it's really best to just not display the netmask in the output >> of ifconfig iff IFF_POINTOPOINT is set. While I agree that the net mask makes no sense on a point-to-point link, many people don't. My ISP (Telstra) asks me to set a net mask of 0xffffffc0 on my link. I wonder why. If the ifconfig command doesn't show the net mask, it can cause a lot of confusion (even more than exists currently). >> Routes to the remote end apart from the implied host route seem to be >> dangerous to me, and they break the current behaviour (i.e. could >> cause surprises for people who are used to how it's done now). I don't know what you mean here (I didn't see the original message). In almost every case, you have a route to the remote end, usually a default route. I'm guessing that you mean something else. >> It's not always that the IP address of the remote end is indeed >> identical with the remote network address. Ah. You're thinking about implied routes to the rest of the address space in which the remote end is located? Indeed. Telstra insists that I use one of their addresses at this end of the link. There's no other Telstra address here. Presumably *they* don't use an 0xffffffc0 net mask on this link :-) Greg From owner-freebsd-hackers Thu Jan 1 16:47:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA23917 for hackers-outgoing; Thu, 1 Jan 1998 16:47:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.ic.dk (qmailr@mail.ic.dk [194.255.107.174] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA23898 for ; Thu, 1 Jan 1998 16:47:06 -0800 (PST) (envelope-from jacob@jblhome.ping.dk) Received: (qmail 11938 invoked from network); 2 Jan 1998 00:35:48 -0000 Received: from unknown (HELO ic1.ic.dk) (192.168.65.12) by 192.168.65.14 with SMTP; 2 Jan 1998 00:35:48 -0000 Received: from jblhome by ic1.ic.dk with UUCP id AA18621 (5.65c8/IDA-1.4.4j); Fri, 2 Jan 1998 01:45:11 +0100 Received: (from jacob@localhost) by pippin.jblhome.ping.dk (8.8.8/8.7.3) id BAA22359; Fri, 2 Jan 1998 01:13:54 +0100 (CET) To: Brian Somers Cc: Duncan Barclay , hackers@FreeBSD.ORG Subject: Re: Revamping /etc/daily, weekly, monthly References: <199801011220.MAA17567@awfulhak.demon.co.uk> From: Jacob Bohn Lorensen Date: 02 Jan 1998 01:13:50 +0100 In-Reply-To: Brian Somers's message of Thu, 01 Jan 1998 12:20:37 +0000 Message-Id: <871zyru400.fsf@pippin.jblhome.ping.dk> Lines: 34 X-Mailer: Gnus v5.3/Emacs 19.34 X-Charset: ISO_8859-1 X-Char-Esc: 29 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Brian Somers writes: > > Brian Somers writes: > > > [.....] > > > > # do daily/weekly/monthly maintenance > > > > 0 2 * * * once periodic daily 2>&1 | sendmail root > > > > 30 3 * * 6 once periodic weekly 2>&1 | sendmail root > > > > 30 5 1 * * once periodic monthly 2>&1 | sendmail root > > > [.....] > > > I like the idea, but the syntax is bad. It looks way too much like > > > /etc/crontab - except with different meanings. > > I don't think I made myself clear. > You did :^P > I agree with your ideas, but what I'm saying is that /etc/crontab (as > distinct from /var/cron/tabs/* has an extra 6th field - `who'. This I had forgotten all about /etc/crontab (hmmm - what's it for? I don't think my /usr/bin/crontab understands the ``who'' column....? > looks very like your `once' field and would be rather confusing for > someone comparing the two file formats. Then there should be a 7th field in /etc/crontab (corresponding to the 6th field in /var/cron/tabs/*). -- Jacob Lorensen; Mosebuen 33, 1.; DK-2820 Gentofte, Denmark; +45-31560401 PGP ID = E596F0B5; PGP Fingerprint = 1E8726467436DC4A 723B6678C5AD9E71 From owner-freebsd-hackers Thu Jan 1 16:58:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA24489 for hackers-outgoing; Thu, 1 Jan 1998 16:58:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA24481 for ; Thu, 1 Jan 1998 16:57:36 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA00322; Fri, 2 Jan 1998 11:21:08 +1030 (CST) Message-Id: <199801020051.LAA00322@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Niall Smart" cc: "Jordan K. Hubbard" , freebsd-hackers@FreeBSD.ORG Subject: Re: Installing -current and -stable on the same disk In-reply-to: Your message of "Thu, 01 Jan 1998 23:22:40 -0000." <19980101232240.1366.qmail@ginseng.indigo.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Jan 1998 11:21:07 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > On Jan 1, 2:51pm, "Jordan K. Hubbard" wrote: > } Subject: Re: Installing -current and -stable on the same disk > > > I understand that the BSD_COMPAT flag is set for the first FreeBSD fdisk > > > partition. Is that correct? Is there anyway to install -current and > > > -stable on the same disk, apart from using fdisk to hide one from the > > > other in between reboots? > > > > Nope. The boot code will find and boot from the first 0xa5 type > > partition found. > > Crap :( Is this (silly) limitation restricted to the boot code only > or do you know if it has been made in many places? How else would you propose to get around it? Note that this limitation applies to most operating systems on the PC. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ From owner-freebsd-hackers Thu Jan 1 18:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29653 for hackers-outgoing; Thu, 1 Jan 1998 18:44:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ginseng.indigo.ie (ts01-06.waterford.indigo.ie [194.125.139.37]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA29637 for ; Thu, 1 Jan 1998 18:44:19 -0800 (PST) (envelope-from rotel@indigo.ie) Received: (qmail 18746 invoked by uid 1000); 2 Jan 1998 02:40:02 -0000 Message-ID: <19980102024002.18745.qmail@ginseng.indigo.ie> From: "Niall Smart" Date: Fri, 2 Jan 1998 02:40:02 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) Subject: Re: Installing -current and -stable on the same disk To: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Jan 2, 11:21am, Mike Smith wrote: } Subject: Re: Installing -current and -stable on the same disk > > Crap :( Is this (silly) limitation restricted to the boot code only > > or do you know if it has been made in many places? > > How else would you propose to get around it? Note that this limitation > applies to most operating systems on the PC. Modify the internal console thingy so that you can specify the fdisk partition to boot from, so if you had current on fdisk partition 1 and stable on fdisk partition 2: 0:wd(0,1,a) => boots current 0:wd(0,2,a) => boots stable Isn't this possible? I'm pretty sure Linux can do it. Niall From owner-freebsd-hackers Thu Jan 1 19:55:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA03203 for hackers-outgoing; Thu, 1 Jan 1998 19:55:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA03158 for ; Thu, 1 Jan 1998 19:54:56 -0800 (PST) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.8/8.8.7) with SMTP id WAA21905; Thu, 1 Jan 1998 22:54:47 -0500 (EST) (envelope-from dec@phoenix.its.rpi.edu) Date: Thu, 1 Jan 1998 22:54:47 -0500 (EST) From: "David E. Cross" To: Niall Smart cc: freebsd-hackers@FreeBSD.ORG Subject: Re: getopt(3) and numeric arguments In-Reply-To: <19980101231313.1118.qmail@ginseng.indigo.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, 1 Jan 1998, Niall Smart wrote: > Hi, > > The getopt(3) man page says: > > It is also possible to handle digits as option letters. This allows > getopt() to be used with programs that expect a number (``-3'') as an op- > tion. This practice is wrong, and should not be used in any current de- > velopment. It is provided for backward compatibility only. > > Is this correct? Whats so bad about it? Mostly for sake of clarity... is -3 'negative 3' or 'option 3'. I still get confused with nice... is 'nice -20' going oto run at nice level 20, or nice level -20? -- David Cross ACS Consultant From owner-freebsd-hackers Thu Jan 1 20:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA05067 for hackers-outgoing; Thu, 1 Jan 1998 20:22:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA05018 for ; Thu, 1 Jan 1998 20:21:27 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xnyPv-0002so-00; Thu, 1 Jan 1998 20:09:03 -0800 Date: Thu, 1 Jan 1998 20:09:01 -0800 (PST) From: Tom To: John Birrell cc: hackers@FreeBSD.ORG Subject: Re: Sendmail on 2.2.5R In-Reply-To: <199801012020.HAA00256@freebsd1.cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Fri, 2 Jan 1998, John Birrell wrote: > sendmail dropping incoming messages from one particular mail relay. What do you mean "drop"? Do the message disappear? Or are they being rejected? Tom From owner-freebsd-hackers Thu Jan 1 22:29:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA12310 for hackers-outgoing; Thu, 1 Jan 1998 22:29:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA12285 for ; Thu, 1 Jan 1998 22:28:36 -0800 (PST) (envelope-from perlsta@sunyit.edu) Received: from ppp.ios.com (ppp-32.ts-10.nyc.idt.net [169.132.99.104]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with ESMTP id CAA14647 for ; Fri, 2 Jan 1998 02:29:52 GMT Message-Id: <199801020229.CAA14647@fang.cs.sunyit.edu> From: "Alfred Perlstein" To: Subject: SMP-able chips? Date: Thu, 1 Jan 1998 20:50:20 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Does anyone know if any other x86 chip will work in a 2 processor enviornment? like the AMD K6 or the Cyrix M2 also, someone said something on the list about a Slot 1 to Scoket 8 converter, to put pentium Pro chips on a PII mother board... anyone have a pointer to this information? thank you, -Alfred From owner-freebsd-hackers Thu Jan 1 23:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA13979 for hackers-outgoing; Thu, 1 Jan 1998 23:01:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd1.cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA13960 for ; Thu, 1 Jan 1998 23:00:56 -0800 (PST) (envelope-from jb@freebsd1.cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.8.7/8.8.7) id SAA01509; Fri, 2 Jan 1998 18:05:58 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199801020705.SAA01509@freebsd1.cimlogic.com.au> Subject: Re: Sendmail on 2.2.5R In-Reply-To: from Tom at "Jan 1, 98 08:09:01 pm" To: tom@sdf.com (Tom) Date: Fri, 2 Jan 1998 18:05:58 +1100 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Tom wrote: > > On Fri, 2 Jan 1998, John Birrell wrote: > > > sendmail dropping incoming messages from one particular mail relay. > > What do you mean "drop"? Do the message disappear? Or are they being > rejected? By "drop" I mean that I see sendmail log a message in maillog, but nothing gets sent on to my user account. That message is logged as zero size. While writing this reply I noticed the `tail -f /var/log/maillog' (that I have running in another window) scroll and I just saw this: Jan 2 17:32:27 freebsd1 sendmail[1460]: RAA01460: lost input channel from misery.sdf.com [204.244.210.193] Jan 2 17:32:27 freebsd1 sendmail[1460]: RAA01460: from=, size=0, class=0, pri=0, nrcpts=0, proto=SMTP, relay=misery.sdf.com [204.244.210.193] which displays the same symptoms as the problem from the other relay, except for the "lost input channel" message. So what did you do to cause that? Was it a re-transmit from earlier in the day/night? FWIW, the relay I have problems with is homeworld.cygnus.com which handles both CVS and mailing lists for NetBSD. Chuckle. I _know_ that it's configuration hasn't changed because I have an account on the machine. NetBSD use qmail. I have a .qmail in my home directory that forwards mail to the same address that FreeBSD sends to. If I send mail from here to my account on that machine, it should be forwarded back like it used to. Instead I see: Jan 2 17:28:15 freebsd1 sendmail[1429]: RAA01429: from=, size=0,class=0, pri=0, nrcpts=0, proto=SMTP, relay=homeworld.cygnus.com [205.180.83.70] which has been trying since yesterday. So I tried subscribing to one of the same NetBSD lists from that machine, after deleting the .qmail so that the mail would be saved. Here is the header from a message saved on homeworld.cygnus.com, that I should have received as jb@cimlogic.com.au: > From port-i386-owner-jb=NetBSD.ORG@NetBSD.ORG Fri Jan 02 03:10:16 1998 > Return-Path: > Delivered-To: jb@NetBSD.ORG > Received: (qmail 3613 invoked by uid 605); 2 Jan 1998 03:10:12 -0000 > Received: (qmail 3533 invoked from network); 2 Jan 1998 03:10:04 -0000 > Received: from myall.awadi.com.au (150.207.2.65) > by homeworld.cygnus.com with SMTP; 2 Jan 1998 03:10:04 -0000 > Received: from bunya.awadi ([150.207.31.63]) by myall.awadi.com.au (8.7.5/8.7.3) > with SMTP id NAA21592 for ; Fri, 2 Jan 1998 13:38:51 +1030 (CST) > Received: from mallee.awadi by bunya.awadi (SMI-8.6/SMI-SVR4) > id NAA08511; Fri, 2 Jan 1998 13:38:50 +1030 > Received: by mallee.awadi (SMI-8.6/SMI-SVR4) > id NAA15023; Fri, 2 Jan 1998 13:38:50 +1030 > From: blymn@baea.com.au (Brett Lymn) > Message-Id: <199801020308.NAA15023@mallee.awadi> > Subject: Doom available. > To: port-i386@netbsd.org > Date: Fri, 2 Jan 1998 13:38:50 +1030 (CST) > X-Mailer: ELM [version 2.4 PL23] > MIME-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > Sender: port-i386-owner@NetBSD.ORG > Precedence: list > Delivered-To: port-i386@NetBSD.ORG > Now if I set .qmail to redirect mail to jb@freebsd.org and use the FreeBSD forwarding (only for a short while 8-) and I send a message to myself on that machine, I receive the mail OK: Jan 2 17:57:13 freebsd1 sendmail[1494]: RAA01494: from=, size=770, class=0, pri=30770, nrcpts=1, msgid=<19980102065147.20258.qmail@mail.NetBSD.ORG>, proto=ESMTP, relay=y.physics.usyd.edu.au [129.78.129.110] Jan 2 17:57:13 freebsd1 sendmail[1494]: RAA01494: to=, delay=00:00:02, xdelay=00:00:00, mailer=local, stat=Sent but the *exact* same mail message sent direct to this machine fails with: Jan 2 18:00:16 freebsd1 sendmail[1504]: SAA01504: from=, size=0, class=0, pri=0, nrcpts=0, proto=SMTP, relay=homeworld.cygnus.com [205.180.83.70] So must be something wrong with the configuration. But the rewriting rules haven't changed since 2.2.2 which worked! I think I'll grab another disk and put 2.2.2 on that and see if it still works. I'm not sure what else to do. Sigh. > > Tom > > Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 From owner-freebsd-hackers Thu Jan 1 23:54:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA16560 for hackers-outgoing; Thu, 1 Jan 1998 23:54:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from revolution.3-cities.com (root@revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA16554 for ; Thu, 1 Jan 1998 23:54:32 -0800 (PST) (envelope-from msmith@3-cities.com) Received: from mark (bigtca114.3-cities.com [204.203.228.47]) by revolution.3-cities.com (8.8.5/8.7.3) with SMTP id XAA06742 for ; Thu, 1 Jan 1998 23:50:08 -0800 (PST) Message-ID: <34AC9D15.6E2A@3-cities.com> Date: Thu, 01 Jan 1998 23:53:57 -0800 From: Mark Smith Reply-To: freebsd-hackers@FreeBSD.ORG Organization: Organization? What's that?!? X-Mailer: Mozilla 3.03Gold (Win95; U) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: make kernel warnings/errors Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Greetings, Sorry if this isn't the right place for this, if it isn't, please kindly direct me where it would be. I tried freebsd-questions and got zilch. OK, I just did a new install of FreeBSD 2.2.5R (walnut creek CDROM). I then wanted to get the ppp device going so I copied GENEERIC to CUSTOM and uncommented the ppp device at the bottom. I then did a config CUSTOM, cd /sys/compile/CUSTOM, make depend, make world. The resulting make gives the following warnings/errors. The GENERIC config file does the same thing. ../../pci/ncr.c:1486: warning: initialization discards `volatile' from pointer target type ../../pci/ncr.c:1486: warning: initialization discards `volatile' from pointer target type ../../i386/isa/seagate.c: In function `sea_data_output': ../../i386/isa/seagate.c:1111: warning: assignment discards `volatile' from pointer target type ../../i386/isa/seagate.c: In function `sea_data_input': ../../i386/isa/seagate.c:1181: warning: assignment discards `volatile' from pointer target type OK, I then got the CVSup going and bring this up to RELENG_2_2 (2.2.5 Stable), and then edit CUSTOM and comment a bunch of uneeded crap out, config CUSTOM, cd /sys/compile/CUSTOM, make depend, make. The CUSTOM config file and machine description is at the end of this message. The actual buld gives the following warnings/errors, oh, GENERIC does the same thing but with more warnings about the seagate scsi code: ../../pci/ncr.c:1486: warning: initialization discards `volatile' from pointer target type ../../pci/ncr.c:1486: warning: initialization discards `volatile' from pointer target type ../../i386/i386/machdep.c:1372: warning: initialization from incompatible pointer type ../../i386/i386/machdep.c: In function `f00f_hack': ../../i386/i386/machdep.c:1386: warning: assignment makes pointer from integer without a cast ../../i386/i386/machdep.c:1397: warning: passing arg 2 of `vm_map_protect' makes integer from pointer without a cast ../../i386/i386/machdep.c:1397: warning: passing arg 3 of `vm_map_protect' makes integer from pointer without a cast NOW, I'm starting to worry! I went ahead and installed this kernel and it seems to run, BUT I now get the following when I reboot! Dec 30 01:18:48 mark /kernel: ncr0 rev 17 int a irq 9 on pci0:11 Dec 30 01:18:48 mark /kernel: ncr0 waiting for scsi devices to settle Dec 30 01:18:48 mark /kernel: (ncr0:1:0): "ARCHIVE Python 25588-XXX 2.96" type 1 removable SCSI 2 Dec 30 01:18:48 mark /kernel: st0(ncr0:1:0): Sequential-Access Dec 30 01:18:48 mark /kernel: st0(ncr0:1:0): asynchronous. Dec 30 01:18:49 mark /kernel: ncr0:1: ERROR (88:0) (6-a7-e007) (e0/3) @ (script 1b4:980c0002). Dec 30 01:18:49 mark /kernel: ncr0: script cmd = 7c094800 Dec 30 01:18:49 mark /kernel: ncr0: regdump: da 10 80 03 47 e0 01 1d 01 06 01 a7 80 00 0f 00. Dec 30 01:18:49 mark /kernel: Dec 30 01:18:49 mark /kernel: st0(ncr0:1:0): M_REJECT received (1:8). Dec 30 01:18:49 mark /kernel: density code 0x0, variable blocks, write-enabled CUSTOM config: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: CUSTOM,v 1.77.2.12 1997/10/18 11:03:10 joerg Exp $ machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident CUSTOM maxusers 10 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] 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 options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 #controller eisa0 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 #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 #IDE CD-ROM # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 #controller amd0 #controller ahb0 controller ahc0 #controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device sd0 device od0 #See LINT for possible `od' options. device st0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # 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 XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? disable # Advanced Power Management #options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS # PCCARD (PCMCIA) support #controller crd0 #device pcic0 at crd? #device pcic1 at crd? 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 sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr #device psm0 at isa? disable port "IO_KBD" conflicts tty irq 12 vector psmintr # 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 #device fxp0 #device vx0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ie1 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr 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 vn 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM SYSTEM! ASUS P55T2P4S motherboard with HX chipset 64MB RAM (soon to be 128MB) Adaptec AIC-7880 UWSCSI chip on MB Symbios 810/ASUS SC-200 scsi card Diamond Stealth 3D 2000 4MB Plextor 12X SCSI CDROM on 810 ARCHIVE Python 25588-XXX 2.96 DAT DDS1 tape on 810 Conner 2G wide SCSI on 7880 Any ideas? Mark From owner-freebsd-hackers Fri Jan 2 01:21:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19695 for hackers-outgoing; Fri, 2 Jan 1998 01:21:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19677; Fri, 2 Jan 1998 01:21:25 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id KAA04932; Fri, 2 Jan 1998 10:21:13 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id KAA20816; Fri, 2 Jan 1998 10:20:27 +0100 (MET) Message-ID: <19980102102027.41384@uriah.heep.sax.de> Date: Fri, 2 Jan 1998 10:20:27 +0100 From: J Wunsch To: Greg Lehey Cc: Brian Somers , John-Mark Gurney , freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point Reply-To: Joerg Wunsch References: <199801010130.RAA10049@hub.freebsd.org> <199801011325.NAA17803@awfulhak.demon.co.uk> <19980102105504.61189@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980102105504.61189@lemis.com>; from Greg Lehey on Fri, Jan 02, 1998 at 10:55:04AM +1030 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk As Greg Lehey wrote: > While I agree that the net mask makes no sense on a point-to-point > link, many people don't. My ISP (Telstra) asks me to set a net mask > of 0xffffffc0 on my link. I wonder why. Because they (or their routers) are stupid, and they don't know it better. You'll be surprised to find how many router vendors don't understand the very basics of IP routing. > >> Routes to the remote end apart from the implied host route seem to be > >> dangerous to me, and they break the current behaviour (i.e. could > >> cause surprises for people who are used to how it's done now). > > I don't know what you mean here (I didn't see the original message). > In almost every case, you have a route to the remote end, usually a > default route. I'm guessing that you mean something else. It's too much out of context that i remember myself. I think my remark was about other _automatically_ installed routes (at ifconfig time). There's nothing wrong with `route add ...' later on, but the admin should always be required to do this manually. (In Linux, you even gotta install the interface route yourself.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 2 02:20:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA23118 for hackers-outgoing; Fri, 2 Jan 1998 02:20:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA23110 for ; Fri, 2 Jan 1998 02:20:28 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA15463 for hackers@freebsd.org; Fri, 2 Jan 1998 09:56:58 +0100 From: Luigi Rizzo Message-Id: <199801020856.JAA15463@labinfo.iet.unipi.it> Subject: ATAPI again To: hackers@FreeBSD.ORG Date: Fri, 2 Jan 1998 09:56:58 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Hi, I did some work on the atapi driver (atapi.c and wcd.c) aimed at reading audio data from the disk. I am encountering a few problems which I'll try to summarize. 1) timeout in MODE_SENSE at boot time. First thing I tried was to make the boot message a bit more verbose by dumping the various capability bits from the capability page. I realized (at least on my SONY CDU-55E, but I have seen the same behaviour on different drives in the last years) that frequently (not sure about the exact cause, but more often after a warm boot or when the tray is closed) the initial MODE_SENSE to get the capabilities of the drive fails. I thought it was a problem of the drive, but now I think it is some problem in the driver. In any case I managed to see that my drive (at least from the capabilities) is able to extract audio data and other info via the READ_CD command -- which is mandatory anyways for most formats except CD-DA). 2) timeout in READ_CD Second thing I tried was to replace the ATAPI_READ_BIG command with ATAPI_READ_CD (with the proper changes in parameters). Unfortunately, with this change, the first interrupt returns a length of 0 which prevents the actual data transfer to complete. I tried to fake the length to 2048 (for CDROM) but no success. Maybe both things are related ? The (minimal) diff for READ_CD is the following (wcd.c), plus you need to add the following line to atapi.h atapi.h:#define ATAPI_READ_CD 0xbe /* universal read command */ Cheers Luigi --- wcd.c.orig Sun Sep 8 12:28:23 1996 +++ wcd.c Fri Jan 2 11:11:40 1998 @@ -323,6 +323,10 @@ if (t->flags & F_DEBUG) wcd_dump (t->lun, "cap", &t->cap, sizeof t->cap); } + else { + printf("wcd: result code %d\n", result.code); + wcd_describe (t); + } #ifdef DEVFS @@ -402,6 +406,35 @@ if (t->cap.prevent) printf (", lock protected"); printf ("\n"); + + printf ("wcd%d: ", t->lun); + if (t->cap.composite) + printf(", composite A/V"); + if (t->cap.dport1) + printf(", dig.audio 1"); + if (t->cap.dport2) + printf(", dig.audio 2"); + if (t->cap.mode2_form1) + printf(", mode 2 form 1(XA)"); + if (t->cap.mode2_form2) + printf(", mode 2 form 2"); + if (t->cap.multisession) + printf(", multisession"); + if (t->cap.cd_da) + printf(", CD-DA read"); + if (t->cap.cd_da_stream) + printf(", CD-DA stream"); + if (t->cap.rw) + printf(", combined rw"); + if (t->cap.rw_corr) + printf(", rw correct."); + if (t->cap.c2) + printf(", C2 ptrs"); + if (t->cap.isrc) + printf(", ISRC"); + if (t->cap.upc) + printf(", UPC"); + printf("\n"); } static int @@ -547,11 +580,25 @@ * What if something asks for 512 bytes not on a 2k boundary? */ blkno = bp->b_blkno / (SECSIZE / 512); nblk = (bp->b_bcount + (SECSIZE - 1)) / SECSIZE; - +#if 1 /* XXX luigi */ + /* byte 1 bit 4..2 indicate the expected sector type. + 0=any + 4=CDDA + 8=yellow book (2k, data) + byte 9 should indicate the type of data to return. + 0x10 or 0x00 returns a LEN=0 to the DATAIN phase, + thus causing a deadlock... + */ + atapi_request_callback (t->ata, t->unit, ATAPI_READ_CD, 0, + blkno>>24, blkno>>16, blkno>>8, blkno, 0, nblk>>8, nblk,0x10, 0, + 0, 0, 0, 0, 0, (u_char*) bp->b_un.b_addr, bp->b_bcount, + wcd_done, t, bp); +#else atapi_request_callback (t->ata, t->unit, ATAPI_READ_BIG, 0, blkno>>24, blkno>>16, blkno>>8, blkno, 0, nblk>>8, nblk, 0, 0, 0, 0, 0, 0, 0, (u_char*) bp->b_un.b_addr, bp->b_bcount, wcd_done, t, bp); +#endif } static void wcd_done (struct wcd *t, struct buf *bp, int resid, From owner-freebsd-hackers Fri Jan 2 02:26:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA23400 for hackers-outgoing; Fri, 2 Jan 1998 02:26:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA23390 for ; Fri, 2 Jan 1998 02:26:18 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id KAA10705; Fri, 2 Jan 1998 10:14:56 GMT Date: Fri, 2 Jan 1998 10:14:56 +0000 (GMT) From: Doug Rabson To: John Polstra cc: troyc@sandy.merix.com, hackers@FreeBSD.ORG Subject: Re: FreeBSD ELF status? In-Reply-To: <199712311722.JAA19985@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Wed, 31 Dec 1997, John Polstra wrote: > In article , > Troy Curtiss wrote: > > > It seems to percolate up every now & again in this list on how the > > all-ELF FreeBSD is going... Anybody (jdp, sos?) care to comment on > > the progress made so-far? > > Everybody who was working on it got very busy with paywork, so there > hasn't been much progress lately. We still have hopes of having it > ready for 3.0-RELEASE, but time will tell whether that will work out > or not. The primary obstacle remaining is The Migration Problem. I think that a big help in migration would be a runtime linker which could load both a.out and elf shared libs. You would also need a tweak to ld to allow you to link and ELF program to an a.out lib but that shouldn't be too hard. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-hackers Fri Jan 2 03:35:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA26954 for hackers-outgoing; Fri, 2 Jan 1998 03:35:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA26947 for ; Fri, 2 Jan 1998 03:35:37 -0800 (PST) (envelope-from perlsta@sunyit.edu) Received: from ppp.ios.com (brightmn@ppp-32.ts-10.nyc.idt.net [169.132.99.104]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with ESMTP id HAA15366; Fri, 2 Jan 1998 07:36:01 GMT Message-Id: <199801020736.HAA15366@fang.cs.sunyit.edu> From: "Alfred Perlstein" To: Cc: Subject: interested in working on windows port (sorry for cross post) Date: Fri, 2 Jan 1998 06:31:20 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk (please excuse the cross post, i'm really looking for help and this is a strange multiplatform subject...) I'm interested in making a windows 95/NT port of Xfree86, i plan on using DirectX to support fast accesses to the graphical hardware. if anyone has the time to answer a couple of questions it would be greatly appreciated. 1) can anyone recommend a free c/cpp compiler/enviornment for this? i've looked at DJGPP,RSXNT, and the cygnus thingy and so far: DJGPP doesn't support win32. RSXNT hardly is docmented and doesn't seem to be useful as a UNIX to WIN32 porting tool things like sockets don't seem to be implemented. cygnus doesn't appeal to me because of hardcore GPL license they have. i do NOT mind giving credit where credit is due... but i'm not too keen on releasing my source, i DO however, plan on the product being free. 2) if i use direct-X does anyone know if it will work on NT? i think mircosoft doesn't support DirectX on NT, or at least not past version 3... 3) what books can i get on the low level details of X? anything on how the X11 source tree is set up? anyone have any pointers to good FAQs/tutorials? thank you, -Alfred From owner-freebsd-hackers Fri Jan 2 04:40:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA29709 for hackers-outgoing; Fri, 2 Jan 1998 04:40:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA29687 for ; Fri, 2 Jan 1998 04:40:30 -0800 (PST) (envelope-from pjchilds@al.imforei.apana.org.au) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (beBop) id XAA22902; Fri, 2 Jan 1998 23:10:02 +1030 (CST) Date: Fri, 2 Jan 1998 23:10:02 +1030 (CST) From: Peter Childs Message-Id: <199801021240.XAA22902@al.imforei.apana.org.au> To: grog@lemis.com (Greg Lehey), freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.5 problems In-Reply-To: <199712020023.QAA21293@bubba.whistle.com> <19971202150522.15474@lemis.com> User-Agent: tin/pre-1.4-971224 (UNIX) (FreeBSD/2.2-STABLE (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In article <19971202150522.15474@lemis.com> you wrote: >> Erm, not really - better to leave it in -questions until you're sure >> it's a bug. :) FWIW there was something in the freebsd-stable list that sounded somewhat similar... I'll include it here for reference. However it refered to switching some of the syscons stuff back to 2.2.5-RELEASE, which I believe was one of the machines you were having problems with.. Path: al.imforei.apana.org.au!chuckie.apana.org.au!news.apana.org.au!gateway From: rewt@i-Plus.net (Troy Settle) Newsgroups: apana.lists.os.freebsd.stable Subject: syscons bug Date: 1 Jan 1998 18:33:12 +1100 Organization: APANA mail-news gateway Lines: 18 Approved: news@apana.org.au Message-ID: <00d601bd1683$d0f9ca80$3a4318d0@b.nu> NNTP-Posting-Host: core.apana.org.au Xref: al.imforei.apana.org.au apana.lists.os.freebsd.stable:1143 A few weeks ago, I posted a request for help with a 2.2.5-STABLE (mid to late Nov) problem involving a bug in the syscons driver that caused a reboot when switching vtys. Someone (one of the developers?) from Japan, I belive, asked me to apply a couple patches to revert syscons.c and syscons.h back to 2.2.5-RELEASE to see where the bug appeared. It took a while, but I finally found the time to try those patches, and it took both of them before I got a stable syscons driver. Just wanted to let the person know (I lost your email, sorry). Thanks for the fix, I hope this info helps you out. --Troy From owner-freebsd-hackers Fri Jan 2 06:18:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA03832 for hackers-outgoing; Fri, 2 Jan 1998 06:18:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA03827 for ; Fri, 2 Jan 1998 06:18:02 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.8/8.8.7) id OAA26278; Fri, 2 Jan 1998 14:17:01 GMT Message-ID: <19980102141701.05705@pavilion.net> Date: Fri, 2 Jan 1998 14:17:01 +0000 From: Josef Karthauser To: Peter Childs Cc: William Wood , freebsd-hackers@FreeBSD.ORG Subject: Re: pptp References: <34833C08.5B230D62@intcomm.net> <199801010909.TAA19362@al.imforei.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199801010909.TAA19362@al.imforei.apana.org.au>; from Peter Childs on Thu, Jan 01, 1998 at 07:39:05PM +1030 X-NCC-RegID: uk.pavilion Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, Jan 01, 1998 at 07:39:05PM +1030, Peter Childs wrote: > In article <34833C08.5B230D62@intcomm.net> you wrote: > > If anyone has any suggestions or ideas the following: > > > I would like to set up two servers (Freebsd) that would be connected via > > the internet using PPTP. How can this be done or what is involve in > > setting this up? > You could always do it with 'ssh'. It's in the ports collection. Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Fri Jan 2 09:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA14554 for hackers-outgoing; Fri, 2 Jan 1998 09:07:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA14435 for ; Fri, 2 Jan 1998 09:06:54 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id MAA07072; Fri, 2 Jan 1998 12:05:48 -0500 (EST) Date: Fri, 2 Jan 1998 12:05:48 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: SMP-able chips? In-Reply-To: <199801020229.CAA14647@fang.cs.sunyit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, 1 Jan 1998, Alfred Perlstein wrote: > Does anyone know if any other x86 chip will work in a 2 processor > enviornment? > like the AMD K6 or the Cyrix M2 I can't answer the second question, but as to the first, all motherboards available today use the Intel Apic design, not the OpenApic design that the cpus other than Intel implement. The meaning to that is, if it's not an Intel CPU, you're not going to run SMP with it. > > also, someone said something on the list about a Slot 1 to Scoket 8 > converter, to put pentium Pro chips on a PII mother board... anyone have a > pointer to this information? > > thank you, > -Alfred > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Fri Jan 2 09:24:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16615 for hackers-outgoing; Fri, 2 Jan 1998 09:24:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA16566 for ; Fri, 2 Jan 1998 09:23:53 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id SAA09931 for freebsd-hackers@freebsd.org; Fri, 2 Jan 1998 18:23:51 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id SAA22316; Fri, 2 Jan 1998 18:17:23 +0100 (MET) Date: Fri, 2 Jan 1998 18:17:23 +0100 (MET) Message-Id: <199801021717.SAA22316@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199801011220.MAA17567@awfulhak.demon.co.uk> <871zyru400.fsf@pippin.jblhome.ping.dk> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Revamping /etc/daily, weekly, monthly X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Jacob Bohn Lorensen wrote: > I had forgotten all about /etc/crontab (hmmm - what's it for? For those who are used to the old BSD cron... i don't like it much myself, and typically delete it immediately. > Then there should be a 7th field in /etc/crontab (corresponding to the > 6th field in /var/cron/tabs/*). Nope. This will cause a large incompatibility (with major upgrade hassles for the users). If at all, encode the `once' (or `boot-time') somewhere into the time specification, where it logically belongs to. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Jan 2 09:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16634 for hackers-outgoing; Fri, 2 Jan 1998 09:24:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA16599 for ; Fri, 2 Jan 1998 09:24:09 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id SAA09933 for freebsd-hackers@freebsd.org; Fri, 2 Jan 1998 18:24:02 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id SAA22323; Fri, 2 Jan 1998 18:17:58 +0100 (MET) Date: Fri, 2 Jan 1998 18:17:58 +0100 (MET) Message-Id: <199801021717.SAA22323@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199801020705.SAA01509@freebsd1.cimlogic.com.au> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Sendmail on 2.2.5R X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk John Birrell wrote: > By "drop" I mean that I see sendmail log a message in maillog, but nothing > gets sent on to my user account. That message is logged as zero size. Could you tcpdump the connections? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 3 05:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA12381 for hackers-outgoing; Sat, 3 Jan 1998 05:58:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA12374 for ; Sat, 3 Jan 1998 05:58:43 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA16694; Sat, 3 Jan 1998 13:35:39 +0100 From: Luigi Rizzo Message-Id: <199801031235.NAA16694@labinfo.iet.unipi.it> Subject: read audio from atapi cd: success! To: hackers@FreeBSD.ORG Date: Sat, 3 Jan 1998 13:35:39 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Well, I managed to put together some code to read audio data from ATAPI CDs :) The code is very primitive and inefficient (e.g. it uses ioctl() and cannot currently read more than one block at a time, meaning it is far slower than real time at least on my 2x drive) but it is there as a hint to somebody with more knowledge than I have to make it work well. I DO NOT recommend to commit the as it is now, but I do hope that some committer with sufficient knowledge has the time to work on it and improve it according to the suggestion which follow. Diffs (more or less against 2.2.1R) are at ttp://www.iet.unipi.it/~luigi/cdda.diffs They include changes to 3 files: atapi.c, wcd.c and cdio.h, and a simple program to test the ioctl and read audio data. The patch also includes a more verbose attach to reveal the capabilities of the drive, and an attempt to make the initial MODE_SENSE not timeout. However the latter seems to be very unreliable on my drive (Sony CDU-55E), which often returns a CHECK code. BRIEF DESCRIPTION OF THE CODE My initial goal was to support reading audio data through the read() interface. However, I was having some trouble and unexpected behaviours in replacing the READ_BIG with READ_CD command (maybe due to interactions with other commands), so I decided to go along another way and introduce a new ioctl() to be able to play with the parameters in the atapi command. The way I have implemented it, the ioctl issues a wcd_request_wait for ATAPI_READ_CD, copying each block into a kernel buffer and from there into user space using copyout. This is highly inefficient since you cannot read more than 1 sector/revolution. It ought to be made more efficient by using a larger block of storage and allowing for more than one sector at a time. I am not sure of how much work is necessary to make the ioctl() copy directly into the user-supplied buffer, it is probably necessary to lock the buffer in memory and map it into the kernel space around the transfer -- more or less what is done in function physio() in file /sys/kern/kern_physio.c. There might be more efficient ways, and I'd hate duplicating lot of code which is already there... Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Sat Jan 3 07:30:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15730 for hackers-outgoing; Sat, 3 Jan 1998 07:30:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA15726 for ; Sat, 3 Jan 1998 07:30:37 -0800 (PST) (envelope-from taob@tor-adm1.nbc.netcom.ca) Received: (from taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) id KAA28293; Sat, 3 Jan 1998 10:30:35 -0500 (EST) Date: Sat, 3 Jan 1998 10:30:35 -0500 (EST) From: Brian Tao X-Sender: taob@tor-adm1 To: FREEBSD-HACKERS Subject: Creating bootable Syjet install disk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk I want to create a bootable Syjet disk with an install kernel that sets up root in MFS, goes straight into /stand/sysinstall, etc., etc. There is enough room on a disk to fit several snapshots of FreeBSD, the entire packages collection, all ports, XFree86 installation tarballs, and a boot kernel. Copying boot.flp's kernel to the Syjet and booting it doesn't work. It hangs at the "rootfs is 1440 Kbyte compiled in MFS", just before /stand/sysinstall runs. I looked through /usr/src/release/Makefile and couldn't figure out how to make it build a kernel that would work from, say, /dev/sd0 or /dev/sd0 (if it is in fact possible for it to dynamically determine which device to use). Is the Makefile for rolling a CD image available somewhere? I assume that uses a slightly different kernel than the one on floppy. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sat Jan 3 13:28:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04417 for hackers-outgoing; Sat, 3 Jan 1998 13:28:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critic.cynic.net (critic.cynic.net [198.73.220.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04413 for ; Sat, 3 Jan 1998 13:28:14 -0800 (PST) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by critic.cynic.net (8.8.8/8.8.8) with SMTP id NAA15054; Sat, 3 Jan 1998 13:26:10 -0800 (PST) X-Authentication-Warning: critic.cynic.net: cjs owned process doing -bs Date: Sat, 3 Jan 1998 13:26:09 -0800 (PST) From: Curt Sampson X-Sender: cjs@critic.cynic.net To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD ELF status? In-Reply-To: <19980101164804.30732@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, 1 Jan 1998, Ollivier Robert wrote: > Considering the boot blocks size issue, it is more of an all or nothing > thing because if we want to boot our shiny new kernel, we need the new > boot blocks. If someone can do the Mithical 3-Stage Bootblock, it would > be easier (no I'm not volunteering :-)). Actually, the easiest solution to this sort of thing is to follow what many other systems (sun, alpha, etc.) do and have your basic boot blocks load in a file containing the second-stage bootstrap from the root filesystem. (Usually you have a utility called "installboot" which programs the block numbers of this file into the first-stage bootstrap.) Then you can have a boot program that's essentially as long and complex as you need. (NetBSD/i386 recently changed to doing things this way.) cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite mist, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Sat Jan 3 13:33:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04638 for hackers-outgoing; Sat, 3 Jan 1998 13:33:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p66.tfs.net [139.146.210.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04632 for ; Sat, 3 Jan 1998 13:33:41 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id PAA04268; Sat, 3 Jan 1998 15:33:14 -0600 (CST) From: Jim Bryant Message-Id: <199801032133.PAA04268@unix.tfs.net> Subject: Re: Creating bootable Syjet install disk In-Reply-To: from Brian Tao at "Jan 3, 98 10:30:35 am" To: taob@nbc.netcom.ca (Brian Tao) Date: Sat, 3 Jan 1998 15:33:13 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 3.0-CURRENT #0: Thu Jan 1 19:03:58 CST 1998 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In reply: > I want to create a bootable Syjet disk with an install kernel that > sets up root in MFS, goes straight into /stand/sysinstall, etc., etc. > There is enough room on a disk to fit several snapshots of FreeBSD, > the entire packages collection, all ports, XFree86 installation > tarballs, and a boot kernel. > > Copying boot.flp's kernel to the Syjet and booting it doesn't > work. It hangs at the "rootfs is 1440 Kbyte compiled in MFS", just > before /stand/sysinstall runs. wrong approach. you are treating the syjet as if it were a floppy disk. the syjet is a hard disk just like any other, but with one additional feature, it is removable. do a regular install. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Sat Jan 3 13:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04760 for hackers-outgoing; Sat, 3 Jan 1998 13:34:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critic.cynic.net (critic.cynic.net [198.73.220.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04741 for ; Sat, 3 Jan 1998 13:34:24 -0800 (PST) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by critic.cynic.net (8.8.8/8.8.8) with SMTP id NAA15097; Sat, 3 Jan 1998 13:34:11 -0800 (PST) X-Authentication-Warning: critic.cynic.net: cjs owned process doing -bs Date: Sat, 3 Jan 1998 13:34:11 -0800 (PST) From: Curt Sampson X-Sender: cjs@critic.cynic.net To: bsdean@gte.net cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mounting a FreeBSD partition on NetBSD or SunOS In-Reply-To: <199801010219.VAA04068@corona.unx.sas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Wed, 31 Dec 1997, Brian Dean wrote: > I have an Iomega Jaz drive (removable > media) and would like to be able to create a Unix filesystem that is > mountable by both systems that I can transport between machines. Well, there are several problems here. 1. The systems have different endianness. Thus FFS isn't compatable between the two. 2. The systems have disklabels in different places. This can sometimes be gotten around by writing multiple, identical disklabels on the disk, assuming you can get around the endian problems as well. I was looking at doing the disklabel work around the middle of last year, but I never really found a satisfactory solution, and finally lost access to the Jaz drive I had, so the point is now fairly moot for me. But I may borrow a couple of ZIP drives and have another go at this one day. Unfortunately it's fallen too low on my priority list to happen any time soon. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite mist, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Sat Jan 3 13:46:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA05631 for hackers-outgoing; Sat, 3 Jan 1998 13:46:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.hanse.de (ns.hanse.de [193.174.9.9]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA05551 for ; Sat, 3 Jan 1998 13:45:45 -0800 (PST) (envelope-from Hanse.DE!Stefan.Bethke@mail.hanse.de) Received: from Hanse.DE by mail.hanse.de with UUCP for freebsd-hackers@FreeBSD.ORG id ; Sat, 3 Jan 98 22:45 MET Received: from [193.141.161.123] (monster.pong.ppp.de [193.141.161.123]) by transit.hanse.de (8.7.5/8.6.12) with ESMTP id SAA20407; Sat, 3 Jan 1998 18:20:27 +0100 (MET) X-Sender: stefan@transit.hanse.de Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 3 Jan 1998 18:20:46 +0100 To: Brian Tao , FREEBSD-HACKERS From: Stefan Bethke Subject: Re: Creating bootable Syjet install disk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk At 10:30 Uhr -0500 03.01.1998, Brian Tao wrote: > Copying boot.flp's kernel to the Syjet and booting it doesn't >work. It hangs at the "rootfs is 1440 Kbyte compiled in MFS", just >before /stand/sysinstall runs. Have you tried a plain kernel? Maybe it stops booting due to some other problem. > I looked through /usr/src/release/Makefile and couldn't figure out >how to make it build a kernel that would work from, say, /dev/sd0 or >/dev/sd0 (if it is in fact possible for it to dynamically determine >which device to use). Is the Makefile for rolling a CD image >available somewhere? I assume that uses a slightly different kernel >than the one on floppy. Its just that src/release/Makefile, with some additional scripts also found in that dir. It takes GENERIC, adds the mfs stuff, and builds the kernel as BOOTMFS. It then copies all the neccessary files from the release staging area into the boot filesystem's staging area, copies it onto a vn filesystem, and copies the vn-file into the kernel image. Then the kernel is put on a vn-filesystem to create the final floppy image. For a laptop, I had to make a custom kernel (to have a non-standard Ethernet driver included). It took be about 4 hours to figure out how to just build a new boot floppy (without doing a complete make release, which I don't have the disk space for). Unfortunatly, the current Makefile does not allow for building a new boot floppy, although it would be quite convenient to be able to do that. It probably would need some work to untangle the boot floppy build from the release build. Another idea would be to have the mfs image saved (and put on the cd), so one only had to build one's custom kernel and copy that image into this kernel. Btw, is there a way to retroactively copy the mfs image out of the kernel? It seemed to me that this isn't possible. [If you don't know what I'm talking about, take a look at the Makefile, Jordan has put a very nice drawing there :-) ] Stefan -- Stefan Bethke Hamburg, Germany From owner-freebsd-hackers Sat Jan 3 14:21:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA07573 for hackers-outgoing; Sat, 3 Jan 1998 14:21:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA07555 for ; Sat, 3 Jan 1998 14:21:03 -0800 (PST) (envelope-from taob@tor-adm1.nbc.netcom.ca) Received: (from taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) id RAA14444; Sat, 3 Jan 1998 17:21:00 -0500 (EST) Date: Sat, 3 Jan 1998 17:21:00 -0500 (EST) From: Brian Tao X-Sender: taob@tor-adm1 To: Jim Bryant cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Creating bootable Syjet install disk In-Reply-To: <199801032133.PAA04268@unix.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sat, 3 Jan 1998, Jim Bryant wrote: > > do a regular install. I don't want to install FreeBSD on the Syjet, I've done that already (and it works rather nicely as the boot device). I want to turn a cartridge into an installation disk. I'd rather not have to install even a minimal filesystem on it, if I can get away with a single 1.4MB kernel. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sat Jan 3 14:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA09400 for hackers-outgoing; Sat, 3 Jan 1998 14:53:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA09391 for ; Sat, 3 Jan 1998 14:53:08 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id OAA02718; Sat, 3 Jan 1998 14:52:52 -0800 (PST) To: Stefan Bethke cc: Brian Tao , FREEBSD-HACKERS Subject: Re: Creating bootable Syjet install disk In-reply-to: Your message of "Sat, 03 Jan 1998 18:20:46 +0100." Date: Sat, 03 Jan 1998 14:52:52 -0800 Message-ID: <2714.883867972@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > Unfortunatly, the current Makefile does not allow for building a new boot > floppy, although it would be quite convenient to be able to do that. It > probably would need some work to untangle the boot floppy build from the > release build. Which Julian tried to do at one point, but I could never make it work for myself so I guess it just rotted. > Another idea would be to have the mfs image saved (and put on the cd), so > one only had to build one's custom kernel and copy that image into this > kernel. Btw, is there a way to retroactively copy the mfs image out of the > kernel? It seemed to me that this isn't possible. [If you don't know what I think you could, actually. Take a look at write_mfs_in_kernel.c - I see no reason why you couldn't take a boot.flp, mount it, copy out /kernel, unzip it, then run a customized version of write_mfs_in_kernel.c which just read it out instead. > I'm talking about, take a look at the Makefile, Jordan has put a very nice > drawing there :-) ] Actually, Poul-Henning gets credit for that picture. He designed and implemented the whole MFSKERNEL idea in the first place! ;) Jordan From owner-freebsd-hackers Sat Jan 3 15:58:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA12515 for hackers-outgoing; Sat, 3 Jan 1998 15:58:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA12502; Sat, 3 Jan 1998 15:58:05 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id KAA20602; Sun, 4 Jan 1998 10:28:00 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA07265; Sun, 4 Jan 1998 10:27:59 +1030 (CST) (envelope-from grog) Message-ID: <19980104102759.11459@lemis.com> Date: Sun, 4 Jan 1998 10:27:59 +1030 From: Greg Lehey To: Hans Petter Bieker Cc: questions@FreeBSD.ORG, FreeBSD Hackers Subject: Re: Why dump to /var?? Reply-To: FreeBSD Hackers References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from Hans Petter Bieker on Sat, Jan 03, 1998 at 08:24:39PM +0100 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sat, Jan 03, 1998 at 08:24:39PM +0100, Hans Petter Bieker wrote: > I got this message after a recent system crash: > checking for core dump...savecore: reboot after panic: page fault > savecore: system went down at Sat Jan 3 18:35:32 1998 > savecore: no dump, not enough free space on device > > not enough free space? On which device? in my /var/crash directory? Presumably, unless you've changed /etc/rc. > How much space does actually this dump need? Equal to the size of my > swap partition? Equal to the size of your memory. It's a memory dump. > If so.. why dump to /var by default. Most people don't have hundreds > of mb's free in var? Maybe a comment in /etc/rc.conf about this? I suppose there's some value in this. Why don't you enter a PR suggesting it? I suspect, however, that a number of core team members would like to keep it short. I'm copying -hackers on this message. Please follow up there. > Maybe savecore should say something like this: > > savecore: /var: no dump, not enough free space on device Well, one reason not to do this change is the possible symbolic link, which makes it possible to put /var/crash on some other file system. The other thing is that savecore almost invariably saves to /var/crash, so it doesn't add much value. > Anyone? Any why not send this error msg to syslogd? It's not running at this point. > (This is a good thing if you don't have a serial console.) Yes, there is some merit in the idea of starting syslogd earlier and logging *all* the startup messages. I did it once for a commercial vendor, and it made looking for errors a lot easier. If I have time on my hands, I may have another go. > Filesystems: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0a 31775 18954 10279 65% / > /dev/wd0s1f 377238 240884 106175 69% /usr > /dev/wd0s1e 29727 3249 24100 12% /var > /dev/wd1s1e 808223 494311 249255 66% /home > procfs 4 4 0 100% /proc > > Swap: > Device 1K-blocks Used Avail Capacity Type > /dev/wd0s1b 174048 0 173984 0% Interleaved > > I have 80 MB ram. Looking at this configuration, I'd suggest creating a directory /home/crash and a symlink /var/crash pointing to it. One thing you should be aware of is that the dump doesn't go away immediately when you start the system. It's at the end of the swap partition, so you can almost invariably manually do a savecore when the system is up and running and (in your case) not using more than half the available swap space. Greg From owner-freebsd-hackers Sat Jan 3 16:24:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA13980 for hackers-outgoing; Sat, 3 Jan 1998 16:24:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA13965 for ; Sat, 3 Jan 1998 16:23:53 -0800 (PST) (envelope-from taob@tor-adm1.nbc.netcom.ca) Received: (from taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) id TAA19053; Sat, 3 Jan 1998 19:23:46 -0500 (EST) Date: Sat, 3 Jan 1998 19:23:46 -0500 (EST) From: Brian Tao X-Sender: taob@tor-adm1 To: Stefan Bethke cc: FREEBSD-HACKERS Subject: Re: Creating bootable Syjet install disk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sat, 3 Jan 1998, Stefan Bethke wrote: > > Have you tried a plain kernel? Maybe it stops booting due to some > other problem. Yep... I made a minimal filesystem from my /, /var and /usr filesystems off my main drive. It boots into multiuser mode just fine. > Unfortunatly, the current Makefile does not allow for building a new > boot floppy, although it would be quite convenient to be able to do > that. It probably would need some work to untangle the boot floppy > build from the release build. The Makefile seems to have some floppy-specific lines in it, although if the bootable CD-ROM is made from the same image, why won't it work on other types of devices? I mean, if you were to take the boot.flp kernel file and copy it to your hard drive, would you expect to be able to boot off of it? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sat Jan 3 17:03:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA16275 for hackers-outgoing; Sat, 3 Jan 1998 17:03:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zerium.newmedia.no (root@[194.198.117.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA16236; Sat, 3 Jan 1998 17:03:15 -0800 (PST) (envelope-from hanspb@persbraten.vgs.no) Received: from localhost (hanspbie@localhost [127.0.0.1]) by zerium.newmedia.no (8.8.8/8.8.7) with SMTP id CAA01433; Sun, 4 Jan 1998 02:02:52 +0100 (CET) Date: Sun, 4 Jan 1998 02:02:51 +0100 (CET) From: Hans Petter Bieker X-Sender: hanspbie@zerium.newmedia.no To: FreeBSD Hackers cc: questions@FreeBSD.ORG Subject: Re: Why dump to /var?? In-Reply-To: <19980104102759.11459@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sun, 4 Jan 1998, Greg Lehey wrote: > > not enough free space? On which device? in my /var/crash directory? > Presumably, unless you've changed /etc/rc. Doesn't savecore know which partition it should dump to? if not -- how does it can it find out if the partition is full without trying to write? $ mkdir /tmp/c /: write failed, file system is full mkdir: c: No space left on device is it possible to do something similar here? Or is this msg generated by the kernel? -bieker From owner-freebsd-hackers Sat Jan 3 17:18:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA17144 for hackers-outgoing; Sat, 3 Jan 1998 17:18:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA17139 for ; Sat, 3 Jan 1998 17:18:45 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id RAA00399; Sat, 3 Jan 1998 17:18:33 -0800 (PST) To: Brian Tao cc: Stefan Bethke , FREEBSD-HACKERS Subject: Re: Creating bootable Syjet install disk In-reply-to: Your message of "Sat, 03 Jan 1998 19:23:46 EST." Date: Sat, 03 Jan 1998 17:18:33 -0800 Message-ID: <395.883876713@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > The Makefile seems to have some floppy-specific lines in it, > although if the bootable CD-ROM is made from the same image, why won't > it work on other types of devices? I mean, if you were to take the > boot.flp kernel file and copy it to your hard drive, would you expect > to be able to boot off of it? You would indeed. I just tried it. :-) If sysinstall ever evolves into something more general, I could even see some value to copying a /kernel.mfs into the new rootfs on installation. Then if you wanted to repair something later and your root fs was still kosher enough to boot the /kernel.mfs, you could do that instead of messing with a boot floppy. Sysinstall is so close to being an effective repair tool *without* the fixit.flp that it's always struck me as a shame that we didn't put in the remaining work to make it so. Then we could eliminate the fixit.flp image entirely and just have the option of booting either the standard boot floppy or CD #1 as the "standard first-aid kit", the 2nd live filesystem CD providing a more complete kit for the serious trauma cases. Most people probably haven't even noticed that then 2nd CD is bootable in 2.2.5 - you can just boot off of it and go straight into the Fixit menu without swapping anything now. Jordan From owner-freebsd-hackers Sat Jan 3 17:43:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA18802 for hackers-outgoing; Sat, 3 Jan 1998 17:43:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sms.quake.org (qmailr@sms.quake.org [206.245.241.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA18796 for ; Sat, 3 Jan 1998 17:43:13 -0800 (PST) (envelope-from warpy@sms.quake.org) Received: (qmail 10439 invoked by uid 1001); 3 Jan 1998 14:09:18 -0000 Date: Sat, 3 Jan 1998 06:09:18 -0800 (PST) From: Warpy X-Sender: warpy@sms.quake.org To: FreeBSD Hackers Subject: Re: Why dump to /var?? In-Reply-To: <19980104102759.11459@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On a similar note, how/where do i specify where coredump files go as opposed to the current directory. -Warpy From owner-freebsd-hackers Sat Jan 3 17:47:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19051 for hackers-outgoing; Sat, 3 Jan 1998 17:47:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA18997 for ; Sat, 3 Jan 1998 17:46:49 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id CAA23994; Sun, 4 Jan 1998 02:46:30 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id CAA02920; Sun, 4 Jan 1998 02:23:47 +0100 (CET) (envelope-from roberto) Message-ID: <19980104022346.05846@keltia.freenix.fr> Date: Sun, 4 Jan 1998 02:23:46 +0100 From: Ollivier Robert To: Curt Sampson Cc: "FreeBSD Hackers' list" Subject: Re: FreeBSD ELF status? References: <19980101164804.30732@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Curt Sampson on Sat, Jan 03, 1998 at 01:26:09PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3945 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk According to Curt Sampson: > what many other systems (sun, alpha, etc.) do and have your basic > boot blocks load in a file containing the second-stage bootstrap > from the root filesystem. (Usually you have a utility called That's what I called the Mythical 3-stage Boot Program[tm] :-) Nonetheless, it is good to know NetBSD already went this way. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Usenet Canal Historique From owner-freebsd-hackers Sat Jan 3 19:38:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA25268 for hackers-outgoing; Sat, 3 Jan 1998 19:38:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA25240 for ; Sat, 3 Jan 1998 19:37:44 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id OAA20782; Sun, 4 Jan 1998 14:07:25 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id OAA07710; Sun, 4 Jan 1998 14:07:24 +1030 (CST) (envelope-from grog) Message-ID: <19980104140724.46961@lemis.com> Date: Sun, 4 Jan 1998 14:07:24 +1030 From: Greg Lehey To: Warpy Cc: FreeBSD Hackers Subject: Re: Why dump to /var?? References: <19980104102759.11459@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from Warpy on Sat, Jan 03, 1998 at 06:09:18AM -0800 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sat, Jan 03, 1998 at 06:09:18AM -0800, Warpy wrote: > On a similar note, Hmm. It's not clear whether this is a followup to my message or not, but since it's sent to -hackers, I'd think it was. My message contains the answer: > how By specifying the name of the directory. savecore looks for (and creates if it doesn't find it) a file called bounds, which contains the number of the next dump. It copies the dump to a file dump., and the current /kernel to kernel. > /where In /etc/rc > do i specify where coredump files go as opposed to the current > directory. Greg From owner-freebsd-hackers Sat Jan 3 19:59:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26323 for hackers-outgoing; Sat, 3 Jan 1998 19:59:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26317 for ; Sat, 3 Jan 1998 19:58:56 -0800 (PST) (envelope-from taob@tor-adm1.nbc.netcom.ca) Received: (from taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) id WAA26484; Sat, 3 Jan 1998 22:58:46 -0500 (EST) Date: Sat, 3 Jan 1998 22:58:46 -0500 (EST) From: Brian Tao X-Sender: taob@tor-adm1 To: "Jordan K. Hubbard" cc: FREEBSD-HACKERS Subject: Re: Creating bootable Syjet install disk In-Reply-To: <395.883876713@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sat, 3 Jan 1998, Jordan K. Hubbard wrote: > > You would indeed. I just tried it. :-) After going back and forth for a bit in IRC ;-), it seems that the kernel from the 2.2.5-RELEASE boot.flp *does* in fact work as one would expect: copy /kernel off the floppy to the fixed drive or a removeable drive like the Syjet, and you can boot off that device as the installation media. The kernel from 3.0-980101 does *not* work, however. It hangs as I described before, at the "rootfs is 1440 Kbyte compiled in MFS" boot message, just before it runs sysinstall. I suspect this may be a problem for a bootable 3.0 CD-ROM as well. > If sysinstall ever evolves into something more general, I could even > see some value to copying a /kernel.mfs into the new rootfs on > installation. Then if you wanted to repair something later and your > root fs was still kosher enough to boot the /kernel.mfs, you could > do that instead of messing with a boot floppy. I have /kernel.MFS files all over the place now from my experimentation, and I think I'll just leave them there for this purpose. :) I hate having to scrounge around for a 3.5" disk to make a boot floppy (assuming I even have a machine around to dd the image). -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sat Jan 3 20:23:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA27769 for hackers-outgoing; Sat, 3 Jan 1998 20:23:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA27744 for ; Sat, 3 Jan 1998 20:23:16 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA19808; Sat, 3 Jan 1998 20:13:27 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd019806; Sat Jan 3 20:13:21 1998 Date: Sat, 3 Jan 1998 20:10:16 -0800 (PST) From: Julian Elischer To: "Jordan K. Hubbard" cc: Stefan Bethke , Brian Tao , FREEBSD-HACKERS Subject: Re: Creating bootable Syjet install disk In-Reply-To: <2714.883867972@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk you never told me more than "it doesn't work for me" It was strange because serveral other people used it successfully I have 'sync'd it up' several times. My guess is that you were making some assumption due to your knowledge of the usual system, which other people (including me) were not making.. I guess it's time to do so again as I saw several relevant changes recently (e.g. libgzip) On Sat, 3 Jan 1998, Jordan K. Hubbard wrote: > > Unfortunatly, the current Makefile does not allow for building a new boot > > floppy, although it would be quite convenient to be able to do that. It > > probably would need some work to untangle the boot floppy build from the > > release build. > > Which Julian tried to do at one point, but I could never make it work > for myself so I guess it just rotted. > > > Jordan > From owner-freebsd-hackers Sat Jan 3 21:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA01988 for hackers-outgoing; Sat, 3 Jan 1998 21:28:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sms.quake.org (qmailr@sms.quake.org [206.245.241.96]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA01982 for ; Sat, 3 Jan 1998 21:28:44 -0800 (PST) (envelope-from warpy@sms.quake.org) Received: (qmail 11238 invoked by uid 1001); 3 Jan 1998 17:54:50 -0000 Date: Sat, 3 Jan 1998 09:54:50 -0800 (PST) From: Warpy X-Sender: warpy@sms.quake.org To: freebsd-hackers@FreeBSD.ORG Subject: Re: Creating bootable Syjet install disk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sat, 3 Jan 1998, Brian Tao wrote: > The kernel from 3.0-980101 does *not* work, however. It hangs as > I described before, at the "rootfs is 1440 Kbyte compiled in MFS" boot > message, just before it runs sysinstall. I suspect this may be a > problem for a bootable 3.0 CD-ROM as well. > I received a similar problem when i recently tried to upgrade my 2.2.5 system to a 3.0-SNAP. The specific release was 3.0-*230-SNAP from memory. I thought it was a hardware fault at my end, and forgot about upgrading for the time being. Which 3.0-SNAP doesn't have this problem? -Warpy From owner-freebsd-hackers Sat Jan 3 22:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA06135 for hackers-outgoing; Sat, 3 Jan 1998 22:46:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA06131 for ; Sat, 3 Jan 1998 22:46:05 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id WAA01318; Sat, 3 Jan 1998 22:45:52 -0800 (PST) To: Julian Elischer cc: Stefan Bethke , Brian Tao , FREEBSD-HACKERS Subject: Re: Creating bootable Syjet install disk In-reply-to: Your message of "Sat, 03 Jan 1998 20:10:16 PST." Date: Sat, 03 Jan 1998 22:45:52 -0800 Message-ID: <1314.883896352@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > you never told me more than "it doesn't work for me" Hmmm. I thought I also sent you the failure output. > It was strange because serveral other people used it successfully > > I have 'sync'd it up' several times. > > My guess is that you were making some assumption due to your > knowledge of the usual system, which other people (including me) > were not making.. Hmmm. As I recall, I was just typing "make" and sort of expecting it to work in the obvious way. If you're saying that this is the case now, I'm more than willing to try it again. :) If it depends on prerequisite steps being taken, like bits in /usr/obj being in place, then it should also definitely do all such things for you. Jordan From owner-freebsd-hackers Sat Jan 3 22:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA06186 for hackers-outgoing; Sat, 3 Jan 1998 22:47:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA05960 for ; Sat, 3 Jan 1998 22:42:03 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id RAA00409 for ; Sun, 4 Jan 1998 17:06:01 +1030 (CST) Message-Id: <199801040636.RAA00409@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@FreeBSD.ORG Subject: Process wedge in 'inode' Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Jan 1998 17:06:00 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Just simultaneously checking out two copies of the kernel source using 'cvs co sys', I have an interesting situation: kingsford:~>ps axlwww UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 1000 1359 1348 1 -14 0 1356 864 inode D+ v1 0:06.84 cvs co sys 1000 1366 160 4 -14 0 1356 812 inode D+ v2 0:06.77 cvs co sys Neither process is responding to signals, and neither can be killed. The rest of the system is running as normal... This is -current as of 971220. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ From owner-freebsd-hackers Sat Jan 3 23:22:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08164 for hackers-outgoing; Sat, 3 Jan 1998 23:22:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA08145; Sat, 3 Jan 1998 23:21:47 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id RAA21123; Sun, 4 Jan 1998 17:48:40 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id RAA08173; Sun, 4 Jan 1998 17:48:39 +1030 (CST) (envelope-from grog) Message-ID: <19980104174838.41538@lemis.com> Date: Sun, 4 Jan 1998 17:48:38 +1030 From: Greg Lehey To: Joerg Wunsch Cc: Brian Somers , John-Mark Gurney , freebsd-bugs@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: kern/5404: slXX slip (tun & ppp) interfaces always point to point References: <199801010130.RAA10049@hub.freebsd.org> <199801011325.NAA17803@awfulhak.demon.co.uk> <19980102105504.61189@lemis.com> <19980102102027.41384@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <19980102102027.41384@uriah.heep.sax.de>; from J Wunsch on Fri, Jan 02, 1998 at 10:20:27AM +0100 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Fri, Jan 02, 1998 at 10:20:27AM +0100, J Wunsch wrote: > As Greg Lehey wrote: > >> While I agree that the net mask makes no sense on a point-to-point >> link, many people don't. My ISP (Telstra) asks me to set a net mask >> of 0xffffffc0 on my link. I wonder why. > > Because they (or their routers) are stupid, and they don't know it > better. You'll be surprised to find how many router vendors don't > understand the very basics of IP routing. It would have to be them. Their routers can't see how I've set my net mask. I had a discussion about this with a bloke here in Adelaide a couple of months ago. He runs a large ISP, and he came up with some plausible reason, but unfortunately I've forgotten the details. It had to do with Microslop: they use broadcasts a lot, and this would seem to indicate that they expected broadcasts on a /26 subnet, or at least were prepared to respond to them. >>>> Routes to the remote end apart from the implied host route seem to be >>>> dangerous to me, and they break the current behaviour (i.e. could >>>> cause surprises for people who are used to how it's done now). >> >> I don't know what you mean here (I didn't see the original message). >> In almost every case, you have a route to the remote end, usually a >> default route. I'm guessing that you mean something else. > > It's too much out of context that i remember myself. I think my > remark was about other _automatically_ installed routes (at ifconfig > time). There's nothing wrong with `route add ...' later on, but the > admin should always be required to do this manually. (In Linux, you > even gotta install the interface route yourself.) It sounds like you're saying that PPP shouldn't be allowed to set the default route automatically when the link comes up. Say that's not what you mean. Greg From owner-freebsd-hackers Sat Jan 3 23:31:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08586 for hackers-outgoing; Sat, 3 Jan 1998 23:31:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA08579 for ; Sat, 3 Jan 1998 23:30:47 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id IAA08800 for freebsd-hackers@FreeBSD.ORG; Sun, 4 Jan 1998 08:30:45 +0100 (CET) (envelope-from olli) Date: Sun, 4 Jan 1998 08:30:45 +0100 (CET) From: Oliver Fromme Message-Id: <199801040730.IAA08800@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: read audio from atapi cd: success! Newsgroups: list.freebsd-hackers Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In list.freebsd-hackers you wrote (3 Jan 1998 15:02:07 +0100): > Well, I managed to put together some code to read audio data from > ATAPI CDs :) Ok. In order to add ATAPI support to tosha, I'll have to buy an ATAPI CD-ROM drive, I fear... Which of them do support reading of digital audio? I'd preferably like to hear about modern drives that can actually be bought. Knowing that some old doublespeed drive supports it doesn't help, since I won't be able to buy it anywhere, unfortunately... ;-) Regards Oliver PS: If someone wants to reply by private mail, please use the address "olli@incogni.to". PPS: I wouldn't mind if someone wants to donate a CD-ROM drive (used or new) for free. ;-) -- Oliver Fromme, Leibnizstr. 18-61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)