From owner-freebsd-stable Sun Jan 9 3:31:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id D39E114D7B for ; Sun, 9 Jan 2000 03:31:12 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id DAA18738; Sun, 9 Jan 2000 03:31:04 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001091131.DAA18738@gndrsh.dnsmgr.net> Subject: Re: CPU voltage (was Re: load spike strangeness) In-Reply-To: <20000108223540.A58762@Bushong.NET> from David Bushong at "Jan 8, 2000 10:35:40 pm" To: david@bushong.net (David Bushong) Date: Sun, 9 Jan 2000 03:31:04 -0800 (PST) Cc: rjoseph@nwlink.com (R Joseph Wright), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Jan 08, 2000 at 10:03:44PM -0800, R Joseph Wright wrote: > > Awhile back I was having trouble getting through kernel compiles, the > > machine would reboot during the compile. Someone on some newsgroup said > > "are you overclocking?". I checked my settings. No, I wasn't > > overclocking. But my voltage setting looked wrong. It was set at 2.2 > > volts or whatever and I thought it was supposed to be at 2.4. So I > > changed it to 2.4. My problem was solved. I was flying through the > > compiles. Then I was looking through my motherboard manual and realized > > that it was supposed to be set at 2.2 after all. I prefer it the way it > > is though. Do you think there is anything wrong with that? > > > Hmm. lmmon -i produces some scary results: > > Voltages > > Vcore1: +2.781V > Vcore2: +1.469V > + 3.3V: +3.312V > + 5.0V: +4.932V > +12.0V: +12.250V <-- Spec is +/- 5%, so 12 +5% is 13.2, your well within spec > -12.0V: -13.125V <-- Again spec is +-5%, so -12 -5% is -13.2, your in spec, a bit high, but see below about light loaded power supplies, this is also one. > - 5.0V: -5.532V <-- Spec is +-5%, -5 -5% is -5.5v, your technically slightly out of spec, but -5V is natorious for being out of spec, and about the only thing that uses it any more in a PC is some of the RS-232 drivers. The reason it is often above spec is that there is no load on it any more and most power supplies have a minimum load requirement of 100mA to regulate correctly (most low current outputs on PC power supplies are down with low cost linear regulators that need a minium 10% of rated current load placed on them before they well regulate correctly). -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 7:13:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail6.svr.pol.co.uk (mail6.svr.pol.co.uk [195.92.193.212]) by hub.freebsd.org (Postfix) with ESMTP id 9A3A815009 for ; Sun, 9 Jan 2000 07:13:34 -0800 (PST) (envelope-from ianjhart@freeloader.freeserve.co.uk) Received: from modem-74.vaqta.dialup.pol.co.uk ([62.136.91.202] helo=freeloader.freeserve.co.uk) by mail6.svr.pol.co.uk with esmtp (Exim 3.12 #0) id 127K25-0003PB-00; Sun, 09 Jan 2000 15:13:30 +0000 Message-ID: <3878A3D7.39664AEC@freeloader.freeserve.co.uk> Date: Sun, 09 Jan 2000 15:05:59 +0000 From: Ian J Hart X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: R Joseph Wright Cc: "stable@freebsd.org" Subject: Re: CPU voltage (was Re: load spike strangeness) References: <200001090555.GAA88547@dorifer.heim3.tu-clausthal.de> <387824C0.F56ACAE4@nwlink.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG R Joseph Wright wrote: > Awhile back I was having trouble getting through kernel compiles, the > machine would reboot during the compile. Someone on some newsgroup said > "are you overclocking?". I checked my settings. No, I wasn't > overclocking. But my voltage setting looked wrong. It was set at 2.2 > volts or whatever and I thought it was supposed to be at 2.4. So I > changed it to 2.4. My problem was solved. I was flying through the > compiles. Then I was looking through my motherboard manual and realized > that it was supposed to be set at 2.2 after all. I prefer it the way it > is though. Do you think there is anything wrong with that? > > -- > Best Regards, Joseph > > You will do foolish things, > but do them with enthusiasm. Colette. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message You don't say what CPU you have. Is it an AMD K6II 400+ by any chance? On all the motherbords I've seen lately the CPU PNP for these chips is broken. They auto detect as 2.4v but have 2.2v stamped on them. Presumably AMD changed the spec after the BIOS code was written. The important question is why would they change the core voltage? Temperature? In fact only this week I had a motherboard which refused to boot when set correctly, but which was fine on auto. This was a _cheap_ PC Chips board though :). If anyone is is _really_ interested I can supply voltage and temperature readings, but not until monday. Maybe I should try 2.3v too. Please post if you want the data. ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 7:42: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id E68DB15123 for ; Sun, 9 Jan 2000 07:41:57 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id KAA13635 for ; Sun, 9 Jan 2000 10:41:51 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id KAA74870 for stable@freebsd.org; Sun, 9 Jan 2000 10:41:51 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001091541.KAA74870@rtfm.newton> Subject: PPP: a big disappointment of 3.4 To: stable@freebsd.org Date: Sun, 9 Jan 2000 10:41:51 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" 5) several times and proceeds to redialing. The /etc/ppp/ppp.conf is the same as before. The ISP is Ziplink. He says, there were occasional problems getting online before, but last night we were unable to do it at all. Sorry, I typed the message by memory and do not have the log here -- his machine is off-line... I'm going to bring an older ppp to him (from 3.2-STABLE) to see if it will work better. Any clues? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 8:43:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lyra.ci.uc.pt (lyra.ci.uc.pt [193.136.200.58]) by hub.freebsd.org (Postfix) with ESMTP id 8B86E14F8A; Sun, 9 Jan 2000 08:43:25 -0800 (PST) (envelope-from pedro@qui.uc.pt) Received: from godfather.mafia.net (pm1-11.uc.pt [193.137.211.139]) by lyra.ci.uc.pt (8.9.3/8.9.3) with ESMTP id QAA06380; Sun, 9 Jan 2000 16:43:10 GMT Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 09 Jan 2000 16:44:31 -0000 (GMT) Reply-To: pedro@qui.uc.pt Organization: Webvolution Networks From: Pedro Almeida To: freebsd-stable@FreeBSD.ORG, misc@openbsd.org, freebsd-isdn@FreeBSD.ORG Subject: Serial + ISDN + Ethernet port Router! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I was contacted to project the link of a medium business office to an other independent office and to the InterNet. The options that I know to exist in the market are based on Cisco routers. I need a Serial(syncronous) link to the other office (this link is permanent), and the link to the Internet is based on dial-on-demand ISDN link. This two links must have independent trafic. The other office must not connect to the Net using the "our side" ISDN link I think this is "simple" using the apropriate rules of routing/firewalling! The question is? Is this possible using a *BSD router? If so, what hardware do I need? Can I use ipf as my firewall software? The serial link is my problem since I don't have this type of link at home! Thanks in advance, Pedro ========================================================== Pedro Almeida (A.K.A. GoDfAThEr) Departamento de Física Universidade de Coimbra 3000 Coimbra Portugal Tel: +351-239-852080 Fax: +351-239-827703 TM: +351-91-4039968 E-Mail: Pedro Almeida Sent on 09-Jan-2000 at 15:22:20 ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 8:45:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5012B14F27 for ; Sun, 9 Jan 2000 08:45:08 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 127LQA-0007dF-00; Sun, 09 Jan 2000 16:42:26 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #1) id 127LQA-0000Xz-00; Sun, 09 Jan 2000 16:42:26 +0000 Date: Sun, 9 Jan 2000 16:42:26 +0000 From: Ben Smithurst To: "Rodney W. Grimes" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CPU voltage (was Re: load spike strangeness) Message-ID: <20000109164226.B2019@strontium.scientia.demon.co.uk> References: <20000108223540.A58762@Bushong.NET> <200001091131.DAA18738@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001091131.DAA18738@gndrsh.dnsmgr.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rodney W. Grimes wrote: > Spec is +/- 5%, so 12 +5% is 13.2, your well within spec > > Again spec is +-5%, so -12 -5% is -13.2, your in spec, a bit high, > > Spec is +-5%, -5 -5% is -5.5v, your technically slightly out of spec, You've added *10* percent to all of these, not 5. 12+5% is 12.6, similar for -12, and 5+5% is 5.25. Am I misunderstanding something? I suspect so. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 9:48: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 5B86714BED for ; Sun, 9 Jan 2000 09:48:05 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA19344; Sun, 9 Jan 2000 09:47:50 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001091747.JAA19344@gndrsh.dnsmgr.net> Subject: Re: CPU voltage (was Re: load spike strangeness) In-Reply-To: <3878A3D7.39664AEC@freeloader.freeserve.co.uk> from Ian J Hart at "Jan 9, 2000 03:05:59 pm" To: ianjhart@freeloader.freeserve.co.uk (Ian J Hart) Date: Sun, 9 Jan 2000 09:47:50 -0800 (PST) Cc: rjoseph@nwlink.com (R Joseph Wright), stable@FreeBSD.ORG (stable@freebsd.org) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > R Joseph Wright wrote: > > > Awhile back I was having trouble getting through kernel compiles, the > > machine would reboot during the compile. Someone on some newsgroup said > > "are you overclocking?". I checked my settings. No, I wasn't > > overclocking. But my voltage setting looked wrong. It was set at 2.2 > > volts or whatever and I thought it was supposed to be at 2.4. So I > > changed it to 2.4. My problem was solved. I was flying through the > > compiles. Then I was looking through my motherboard manual and realized > > that it was supposed to be set at 2.2 after all. I prefer it the way it > > is though. Do you think there is anything wrong with that? > > > > -- > > Best Regards, Joseph > > > > You will do foolish things, > > but do them with enthusiasm. Colette. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > You don't say what CPU you have. Is it an AMD K6II 400+ by any chance? > > On all the motherbords I've seen lately the CPU PNP for these chips is > broken. They auto detect as 2.4v but have 2.2v stamped on them. > Presumably AMD changed the spec after the BIOS code was written. The > important question is why would they change the core voltage? Temperature? When the K6-2 at 400MHz was first put into production it used the same exact process as the 350Mhz parts and ran at 2.4V. AMD found that the chips where not reliable (so did we, with a close to 30% failure rate) and tweaked the process, this tweaking of the process required a voltage change to 2.2V in the core. I feel sorry for anyone who has a K6-2 400 MHz 2.4V part, they run very hot and often have problems running continuous make worlds for more than a day or so even with a monster heat sink and lots of air flow. > > If anyone is is _really_ interested I can supply voltage and temperature > readings, but not until monday. Maybe I should try 2.3v too. Please post > if you want the data. As another datapoint we recently found, many cooling fans do not seat squarly against the chip due to poor mounting clip design. They often end up with a <50% contact area on the top of the chip, and it is off to the side, away from the die area :-(. The easy way to check for this is to apply light pressure to each of the 4 sides of the heatsink and see if it moves ever so slightly, if it does take it off and look very closely at the pattern in the heat sink compound (if you don't have any of that on there get some unless it has a graphite pad.) I pulled one off a customer had installed the other day and the compound was very thin on one side, very think on the other side, and slightly browned in the thich area. Obvios indication of poor heat transfer. If your fan has a graphite pad on it you can still use the ``wobble'' test to check for this. The problem can often be fixed by simply rotating the fan 180 degrees so that the clip goes on the other way (The poorly designed mounting clips put the pressure point in the center of the clip which is not the center of the chip due to the offset in the socket 7 design. And those clips with the offset in them put on backwards compound the problem by putting the pressure even further from the center of the chip :-()). -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 10:17:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 16E9E14D90 for ; Sun, 9 Jan 2000 10:17:52 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA19418; Sun, 9 Jan 2000 10:15:05 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001091815.KAA19418@gndrsh.dnsmgr.net> Subject: Re: CPU voltage (was Re: load spike strangeness) In-Reply-To: <20000109164226.B2019@strontium.scientia.demon.co.uk> from Ben Smithurst at "Jan 9, 2000 04:42:26 pm" To: ben@scientia.demon.co.uk (Ben Smithurst) Date: Sun, 9 Jan 2000 10:15:04 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Rodney W. Grimes wrote: > > > Spec is +/- 5%, so 12 +5% is 13.2, your well within spec > > > > Again spec is +-5%, so -12 -5% is -13.2, your in spec, a bit high, > > > > Spec is +-5%, -5 -5% is -5.5v, your technically slightly out of spec, > > You've added *10* percent to all of these, not 5. 12+5% is 12.6, similar > for -12, and 5+5% is 5.25. Am I misunderstanding something? I suspect > so. Yea, your missing this: <|:-) Thats me with one of them orange traffic cones on my head. I applied the military spec operating ranges to a commercial piece of gear. Even so the critical operating voltages for the board are the +5 (logic) and +12 supplies (disk drive motors). All of the negative supplies are effectively no connects in modern systems causing the 10% load rule to be violated, causing absolutely horrible regulation. Ohh... and for ATX the 3.3V spec is +/-1%, not 5%. (3.27 to 3.33) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 10:32:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from netcom.com (netcom5.netcom.com [199.183.9.105]) by hub.freebsd.org (Postfix) with ESMTP id 0AC1214D06 for ; Sun, 9 Jan 2000 10:32:52 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id KAA13213 for freebsd-stable@freebsd.org; Sun, 9 Jan 2000 10:32:49 -0800 (PST) From: Stan Brown Message-Id: <200001091832.KAA13213@netcom.com> Subject: Help _please_ "make world" faila To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Sun, 9 Jan 2000 13:32:49 -0500 (EST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I reported this yesterday, and the only reply I got asked for more details. Here they are. I cvsuped STABLE yesterday mornign, and again this mornng, and "make world" fails. here is the log: Script started on Sun Jan 9 11:51:38 2000 # make world -------------------------------------------------------------- >>> elf make world started on Sun Jan 9 11:51:43 EST 2000 -------------------------------------------------------------- -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp ===> games/hangman cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/endgame.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/extern.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/getguess.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/getword.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/main.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/playgame.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/prdata.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/prman.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/prword.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/hangman/setup.c cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -o hangman endgame.o extern.o getguess.o getword.o main.o playgame.o prdata.o prman.o prword.o setup.o -lcurses -ltermcap -lcompat gzip -cn /usr/src/games/hangman/hangman.6 > hangman.6.gz ===> games/larn cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE -fwritable-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/larn/main.c cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE -fwritable-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/larn/object.c cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE -fwritable-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/larn/create.c cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE -fwritable-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/larn/tok.c cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE -fwritable-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/larn/display.c cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE -fwritable-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/larn/global.c cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE -fwritable-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/larn/data.c /usr/src/games/larn/data.c:660: unterminated string or character constant /usr/src/games/larn/data.c:660: possible real start of unterminated constant /usr/src/games/larn/data.c:661: Unterminated string constant /usr/src/games/larn/data.c:661: parse error at end of input *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # ^D Script done on Sun Jan 9 13:18:04 2000 As I reported yesterday, it is failing in building the game larn, specifically in the data.c file. Is this a roblem specific to my system? I am reluctant to try it on another machien. Any helpfule sugestiosn as to how to fix this, or at least wrokaround it? Thanks. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 11:42:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 3355414E27 for ; Sun, 9 Jan 2000 11:42:32 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from nwlink.com (ip96.r10.d.bel.nwlink.com [207.202.174.96]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id LAA11615 for ; Sun, 9 Jan 2000 11:42:29 -0800 (PST) Message-ID: <3878E3DE.CF176B3E@nwlink.com> Date: Sun, 09 Jan 2000 11:39:10 -0800 From: R Joseph Wright X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: "stable@freebsd.org" Subject: Re: CPU voltage (was Re: load spike strangeness) References: <200001090555.GAA88547@dorifer.heim3.tu-clausthal.de> <387824C0.F56ACAE4@nwlink.com> <3878A3D7.39664AEC@freeloader.freeserve.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You don't say what CPU you have. Is it an AMD K6II 400+ by any chance? Yes, it's 450 -- Best Regards, Joseph You will do foolish things, but do them with enthusiasm. Colette. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 12:18:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web116.yahoomail.com (web116.yahoomail.com [205.180.60.89]) by hub.freebsd.org (Postfix) with SMTP id 43DA315245 for ; Sun, 9 Jan 2000 12:18:30 -0800 (PST) (envelope-from holtor@yahoo.com) Received: (qmail 20221 invoked by uid 60001); 9 Jan 2000 20:18:29 -0000 Message-ID: <20000109201829.20220.qmail@web116.yahoomail.com> Received: from [209.191.60.54] by web116.yahoomail.com; Sun, 09 Jan 2000 12:18:29 PST Date: Sun, 9 Jan 2000 12:18:29 -0800 (PST) From: Holtor Subject: Kernel Option: TCP_DROP_SYNFIN To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've found this looking threw LINT: # The following options add sysctl variables for controlling how certain # TCP packets are handled. # # TCP_DROP_SYNFIN adds support for ignoring TCP packets with SYN+FIN. This # prevents nmap et al. from identifying the TCP/IP stack, but breaks support # for RFC1644 extensions and is not recommended for web servers. # options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN Would this help stop SYN floods from breaking my freebsd computer? if anyones tried it, please speak up with any results or how it works. Thanks! Holtor __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 12:30:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id C2CFF1530D for ; Sun, 9 Jan 2000 12:30:24 -0800 (PST) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id VAA25676; Sun, 9 Jan 2000 21:30:34 +0100 (MET) Received: by petra.hos.u-szeged.hu (Linux Smail3.2.0.92 #1) id m127P1x-000pArC; Sun, 9 Jan 2000 20:33:41 +0000 () Date: Sun, 9 Jan 2000 21:33:40 +0100 From: Szilveszter Adam To: freebsd-stable@freebsd.org Subject: Re: Help _please_ "make world" faila Message-ID: <20000109213340.A24196@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-stable@freebsd.org References: <200001091832.KAA13213@netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001091832.KAA13213@netcom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 09, 2000 at 01:32:49PM -0500, Stan Brown wrote: > I reported this yesterday, and the only reply I got asked for more > details. Here they are. > > I cvsuped STABLE yesterday mornign, and again this mornng, and "make > world" fails. here is the log: > Hi! Is the enclosed output all that you get? If so, am I right in assuming that you do not delete /usr/obj/* before each build? IMHO it is pretty much compulsory, esp if you also cvsup in the meantime, that is /usr/src changes. As the Handbook says, even with great care, leaving it can cause creepy dependency problems which stem from the fact that FreeBSD is a monolithic system, you either upgrade all of it in one go or you can be in for some surprise...it takes much longer but is worth it. I always do it this way and have never had problems save for the occasions when the code itself was broken, although I do buildworlds often to test-drive the new code, and to make sure it builds. Also, I would suggest blowing /usr/src/games/larn altogether and checking it out again, just in case. Hope this helps. Regards: Szilveszter ADAM -- ------------------------------------------------------------------------------- * Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu * * Homepage : none * alternate email: cc@flanker.itl.net.ua * * Finger sziszi@petra.hos.u-szeged.hu for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 12:56: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pollux.or.signature.nl (pollux.or.signature.nl [194.229.138.194]) by hub.freebsd.org (Postfix) with ESMTP id 609E714BEC; Sun, 9 Jan 2000 12:55:57 -0800 (PST) (envelope-from bit@signature.nl) Received: from localhost (bit@localhost) by pollux.or.signature.nl (8.9.1/8.9.1) with SMTP id VAA15539; Sun, 9 Jan 2000 21:55:38 +0100 (MET) Date: Sun, 9 Jan 2000 21:55:38 +0100 (MET) From: Bart Smit X-Sender: bit@pollux.or.signature.nl To: Pedro Almeida Cc: freebsd-stable@FreeBSD.ORG, misc@openbsd.org, freebsd-isdn@FreeBSD.ORG Subject: Re: Serial + ISDN + Ethernet port Router! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Jan 2000, Pedro Almeida wrote: > I need a Serial(syncronous) link to the other office (this link is permanent), > and the link to the Internet is based on dial-on-demand ISDN link. > This two links must have independent trafic. > The other office must not connect to the Net using the "our side" ISDN link > I think this is "simple" using the apropriate rules of routing/firewalling! This is rather basic indeed. You already indicate your actual question: > The serial link is my problem since I don't have this type of link at home! Have a look at www.etinc.com for synchronous serial interface cards that will work under FreeBSD. I've heard good things about them but I have no experience with them myself. While I'm at it: your question doesn't really belong on -stable (nor on -isdn I think). -- Bart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 12:58:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flophouse.com (flophouse.com [206.169.156.66]) by hub.freebsd.org (Postfix) with ESMTP id CFD8314D66 for ; Sun, 9 Jan 2000 12:58:46 -0800 (PST) (envelope-from dpassage@flophouse.com) Received: from flophouse.com (localhost [127.0.0.1]) by flophouse.com (8.9.3/8.9.3) with ESMTP id NAA05341 for ; Sun, 9 Jan 2000 13:05:48 -0800 (PST) (envelope-from dpassage@flophouse.com) Message-Id: <200001092105.NAA05341@flophouse.com> To: freebsd-stable@freebsd.org Subject: Trouble loading installing on my Aptiva Date: Sun, 09 Jan 2000 13:05:47 -0800 From: "David G. Paschich" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So I just got me a shiny new IBM Aptiva with one of them wacky Athlon processors in it, and FreeBSD 3.x won't load on it. Booting from the floppies in the Jan 9 -STABLE snapshot, the kern and mfsroot floppies load fine, and the kernel configures all the devices, then just after the "changing root device to fd0c" message, I get the following: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc021aef4 stack pointer = 0x10:0xc197ce90 frame pointer = 0x10:0xc197cea4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1 (sysinstall) interrupt mask = net tty bio cam trap number = 12 panic: page fault I have also tried this with floppies made from the 3.3-RELEASE and 3.4-RELEASE CD's and got similiar messages (may even have been exactly the same but I didn't take the trouble to copy them down directly.) Machine is a 500Mhz Athlon with 128M ram, a big honkin IDE disk and an Intel (fxp) ethernet board stuck in it. Anyone have ideas? I may play with earlier releases to try and narrow down if this ever woulda worked. I'll also be happy to try out boot floppies for someone. -------- David G. Paschich dpassage@flophouse.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 13:41: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id BA10515240 for ; Sun, 9 Jan 2000 13:40:59 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca4b-172.ix.netcom.com [209.110.245.172]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id QAA22646 for ; Sun, 9 Jan 2000 16:40:55 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 7913BA54DB; Sun, 9 Jan 2000 13:40:46 -0800 (PST) From: Mike Harding To: freebsd-stable@freebsd.org Subject: When does the 4.x branch go stable? Message-Id: <20000109214046.7913BA54DB@netcom1.netcom.com> Date: Sun, 9 Jan 2000 13:40:46 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm interested in picking up the new gcc, but I was just curious as to when the 4.x branch becomes -STABLE, since the release is just around the corner. Also, that would be 4.x -STABLE, right? Thanks, Mike Harding To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 13:56:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1F4EF15A64 for ; Sun, 9 Jan 2000 13:56:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA52332; Sun, 9 Jan 2000 13:55:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Harding Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? In-reply-to: Your message of "Sun, 09 Jan 2000 13:40:46 PST." <20000109214046.7913BA54DB@netcom1.netcom.com> Date: Sun, 09 Jan 2000 13:55:50 -0800 Message-ID: <52330.947454950@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm interested in picking up the new gcc, but I was just curious as to > when the 4.x branch becomes -STABLE, since the release is just around > the corner. Also, that would be 4.x -STABLE, right? The branch tag will go down when the code freeze has been declared, sometime around the end of this month or (in extremis) the beginning of the next. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 13:56:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1D610152F9; Sun, 9 Jan 2000 13:56:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0BA571CD7F6; Sun, 9 Jan 2000 13:56:28 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 9 Jan 2000 13:56:28 -0800 (PST) From: Kris Kennaway To: Mike Harding Cc: freebsd-stable@freebsd.org Subject: Re: When does the 4.x branch go stable? In-Reply-To: <20000109214046.7913BA54DB@netcom1.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Jan 2000, Mike Harding wrote: > I'm interested in picking up the new gcc, but I was just curious as to > when the 4.x branch becomes -STABLE, since the release is just around > the corner. Also, that would be 4.x -STABLE, right? Probably not until at least 4.1 depending on how stable it actually is. It would be a great disservice to immediately label 4.0 stable the day after release since it's so much new technology and there are bound to be problems for the first little while. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 14: 6:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1946414BED; Sun, 9 Jan 2000 14:06:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA52398; Sun, 9 Jan 2000 14:05:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Mike Harding , freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? In-reply-to: Your message of "Sun, 09 Jan 2000 13:56:28 PST." Date: Sun, 09 Jan 2000 14:05:58 -0800 Message-ID: <52396.947455558@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Probably not until at least 4.1 depending on how stable it actually is. It > would be a great disservice to immediately label 4.0 stable the day after > release since it's so much new technology and there are bound to be > problems for the first little while. If but only life was that simple. :) The code has to branch off the mainline sooner rather than later or quite a bit of re-engineering work planned for -current will stack up behind 4.1-RELEASE. I also predict that unless we put such road blocks in people's way, and I think that would be a bad thing, -current is about to become a lot more interesting again over the next 90 days. That means that for 4.1 to ever have a chance *be* stable, it has to get off the express -current track. People may get confused over the resulting nomenclature, I do understand that, but that's a minor downside by comparison. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 14: 9:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id CD8F814CC7 for ; Sun, 9 Jan 2000 14:09:17 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 5104 invoked by uid 1000); 9 Jan 2000 22:10:16 -0000 Date: Sun, 9 Jan 2000 23:10:16 +0100 From: Andreas Braukmann To: freebsd-stable@FreeBSD.ORG Subject: Re: Trouble loading installing on my Aptiva Message-ID: <20000109231016.G86925@cage.tse-online.de> References: <200001092105.NAA05341@flophouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001092105.NAA05341@flophouse.com>; from dpassage@flophouse.com on Sun, Jan 09, 2000 at 01:05:47PM -0800 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sun, Jan 09, 2000 at 01:05:47PM -0800, David G. Paschich wrote: > So I just got me a shiny new IBM Aptiva with one of them wacky Athlon > processors in it, and FreeBSD 3.x won't load on it. ... hmm. I'm running a 'built-by-myself' Athlon machine (K7-700, Gigabyte-Mainboard, SymbiosLogic SCSI hostadaptor, fxp network) under -current and -stable without any problems. Really without any problems? No, .. of course not. I had to _really_carefully_ select the memory. Athlon-boards are more then picky about memory. Just adjust the BIOS-settings concerning the memory-timing to some conservative values and try again. If this doesn't help -> swap the memory. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x24 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc021aef4 > stack pointer = 0x10:0xc197ce90 > frame pointer = 0x10:0xc197cea4 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1 (sysinstall) > interrupt mask = net tty bio cam > trap number = 12 > panic: page fault -andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 14:16:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id A61C814D3A for ; Sun, 9 Jan 2000 14:16:10 -0800 (PST) (envelope-from computerdeity@geocities.com) Received: from neo.dominion.org ([209.138.148.90]) by smtp6.mindspring.com (8.9.3/8.8.5) with SMTP id RAA14187 for ; Sun, 9 Jan 2000 17:16:08 -0500 (EST) From: General Domino To: FreeBSD-stable@FreeBSD.ORG Date: Sun, 9 Jan 2000 17:21:24 -0500 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00010917222000.35937@neo.dominion.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 14:19: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 9605F14D3F; Sun, 9 Jan 2000 14:18:58 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.19.252] (dialup252.brussels.skynet.be [195.238.19.252]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA09573; Sun, 9 Jan 2000 23:18:53 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <20000109201829.20220.qmail@web116.yahoomail.com> References: <20000109201829.20220.qmail@web116.yahoomail.com> Date: Sun, 9 Jan 2000 23:03:20 +0100 To: Holtor , freebsd-questions@FreeBSD.ORG From: Brad Knowles Subject: Re: Kernel Option: TCP_DROP_SYNFIN Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:18 PM -0800 2000/1/9, Holtor wrote: > Would this help stop SYN floods from breaking my > freebsd computer? if anyones tried it, please speak > up with any results or how it works. Thanks! I've used it and haven't seen it do any harm to the systems I was using it on, although I can't speak for how well it might have helped them survive a SYN flood. Unless you're using TTCP (TCP for Transactions), you should probably be safe in enabling it. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 15:49: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jason01.u.washington.edu (jason01.u.washington.edu [140.142.70.24]) by hub.freebsd.org (Postfix) with ESMTP id 9BC8F14CB3 for ; Sun, 9 Jan 2000 15:48:56 -0800 (PST) (envelope-from eroubinc@u.washington.edu) Received: from dante24.u.washington.edu (eroubinc@dante24.u.washington.edu [140.142.15.74]) by jason01.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA29794; Sun, 9 Jan 2000 15:48:49 -0800 Received: from localhost (eroubinc@localhost) by dante24.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA27638; Sun, 9 Jan 2000 15:48:48 -0800 Date: Sun, 9 Jan 2000 15:48:48 -0800 (PST) From: Evgeny Roubinchtein To: Mike Harding Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? In-Reply-To: <20000109214046.7913BA54DB@netcom1.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Jan 2000, Mike Harding wrote: > >I'm interested in picking up the new gcc, but I was just curious as to >when the 4.x branch becomes -STABLE, since the release is just around >the corner. Also, that would be 4.x -STABLE, right? This is perhaps tangential, but if you wish to use gcc-2.95.2 for your projects, why not install the "egcs" port (it's actually gcc-2.95.2)? -- Evgeny The computing field is always in need of new cliches. - Alan Perlis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 15:58:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 80C2014C86 for ; Sun, 9 Jan 2000 15:58:01 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca3c-23.ix.netcom.com [209.110.242.23]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA26009; Sun, 9 Jan 2000 18:57:50 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 01C49A54EE; Sun, 9 Jan 2000 15:57:44 -0800 (PST) From: Mike Harding To: eroubinc@u.washington.edu Cc: freebsd-stable@FreeBSD.ORG In-reply-to: (message from Evgeny Roubinchtein on Sun, 9 Jan 2000 15:48:48 -0800 (PST)) Subject: Re: When does the 4.x branch go stable? References: Message-Id: <20000109235744.01C49A54EE@netcom1.netcom.com> Date: Sun, 9 Jan 2000 15:57:44 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mmm - I guess I am ready to go to 4.x in general, just wondering when it would be 'safe'. This is for my home system and I would prefer to do a source code update in place... I suppose this will be OK once the branch is tagged and a few people _haven't_ complained that the upgrade melted down their systems. I guess 4.0 will be a major change but I don't have anywhere to back up... - Mike H. Date: Sun, 9 Jan 2000 15:48:48 -0800 (PST) From: Evgeny Roubinchtein Cc: freebsd-stable@FreeBSD.ORG Content-Type: TEXT/PLAIN; charset=US-ASCII X-RULES: lists On Sun, 9 Jan 2000, Mike Harding wrote: > >I'm interested in picking up the new gcc, but I was just curious as to >when the 4.x branch becomes -STABLE, since the release is just around >the corner. Also, that would be 4.x -STABLE, right? This is perhaps tangential, but if you wish to use gcc-2.95.2 for your projects, why not install the "egcs" port (it's actually gcc-2.95.2)? -- Evgeny The computing field is always in need of new cliches. - Alan Perlis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 21: 4:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from atlantis.corbe.net (surf15.pompano.net [24.129.28.15]) by hub.freebsd.org (Postfix) with ESMTP id 74E4E14FE7 for ; Sun, 9 Jan 2000 21:03:50 -0800 (PST) (envelope-from corbe@corbe.net) Received: from localhost (corbe@localhost) by atlantis.corbe.net (8.9.3/8.9.3) with ESMTP id AAA32937 for ; Mon, 10 Jan 2000 00:03:28 -0500 (EST) (envelope-from corbe@corbe.net) Date: Mon, 10 Jan 2000 00:03:27 -0500 (EST) From: Daniel Corbe To: freebsd-stable@freebsd.org Subject: 3.4 compile problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -static -o uudecode uudecode.o /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 1 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 10 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 16 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 24 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 35 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 1 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 10 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 16 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 24 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 35 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 42 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 47 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 53 >= 1 for section `.strtab' /usr/libexec/elf/ld: /usr/obj/usr/src/tmp/usr/lib/crt1.o: invalid string offset 60 >= 1 for section `.strtab' /usr/obj/usr/src/tmp/usr/lib/crt1.o: In function `shstrtab': /usr/obj/usr/src/tmp/usr/lib/crt1.o(.text+0x0): multiple definition of `shstrtab' /usr/obj/usr/src/tmp/usr/lib/crt1.o(.data+0x0): first defined here /usr/libexec/elf/ld: Warning: size of symbol `' changed from 4 to 116 in /usr/obj/usr/src/tmp/usr/lib/crt1.o /usr/libexec/elf/ld: Warning: type of symbol `' changed from 1 to 2 in /usr/obj/usr/src/tmp/usr/lib/crt1.o /usr/libexec/elf/ld: warning: cannot find entry symbol _start; defaulting to 0804807c /usr/obj/usr/src/tmp/usr/lib/libc.a(getopt.o): In function `getopt': getopt.o(.text+0xde): undefined reference to `__progname' getopt.o(.text+0x15a): undefined reference to `__progname' /usr/obj/usr/src/tmp/usr/lib/libc.a(err.o): In function `verrc': err.o(.text+0xa0): undefined reference to `__progname' /usr/obj/usr/src/tmp/usr/lib/libc.a(err.o): In function `verrx': err.o(.text+0x148): undefined reference to `__progname' /usr/obj/usr/src/tmp/usr/lib/libc.a(err.o): In function `vwarnc': err.o(.text+0x204): undefined reference to `__progname' /usr/obj/usr/src/tmp/usr/lib/libc.a(err.o)(.text+0x290): more undefined references to `__progname' follow /usr/obj/usr/src/tmp/usr/lib/libc.a(getenv.o): In function `__findenv': getenv.o(.text+0x11): undefined reference to `environ' getenv.o(.text+0x20): undefined reference to `environ' getenv.o(.text+0x4b): undefined reference to `environ' /usr/obj/usr/src/tmp/usr/lib/libc.a(getenv.o): In function `getenv': getenv.o(.text+0xa1): undefined reference to `environ' getenv.o(.text+0xb0): undefined reference to `environ' /usr/obj/usr/src/tmp/usr/lib/libc.a(getenv.o)(.text+0xdb): more undefined references to `environ' follow /usr/obj/usr/src/tmp/usr/lib/libc.a(collate.o): In function `__collate_err': collate.o(.text+0x368): undefined reference to `__progname' /usr/obj/usr/src/tmp/usr/lib/libc.a(syslog.o): In function `vsyslog': syslog.o(.text+0x14a): undefined reference to `__progname' *** Error code 1 Stop. *** Error code 1 -- Daniel Corbe -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/CC/IT dpu s+:+ !a C++++ UBL++++ P+ L++@ E--- W+ N++(--) o? K- w(++++)$ O- M-- V PS(+) !PE !Y PGP- t@ 5-- X- R(+) tv b+ DI+ D+ G++ e h! r-- !y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 21: 5:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id F090715218 for ; Sun, 9 Jan 2000 21:05:46 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id AAA17746 for ; Mon, 10 Jan 2000 00:05:27 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id AAA86278 for stable@freebsd.org; Mon, 10 Jan 2000 00:05:27 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001100505.AAA86278@rtfm.newton> Subject: isprint(3) and LANG/LOCALE To: stable@freebsd.org Date: Mon, 10 Jan 2000 00:05:27 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" #include main(int argc, char *argv[]) { char *c; for(c = argv[argc-1]; *c; *c++) printf("for %c isprint() returns %d\n", *c, isprint(*c)); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 21:14:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 25B0B151F9 for ; Sun, 9 Jan 2000 21:14:48 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id AAA16940; Mon, 10 Jan 2000 00:12:52 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id AAA00461; Mon, 10 Jan 2000 00:13:03 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id AAA34272; Mon, 10 Jan 2000 00:12:50 -0500 (EST) Date: Mon, 10 Jan 2000 00:12:50 -0500 (EST) From: Thomas David Rivers Message-Id: <200001100512.AAA34272@lakes.dignus.com> To: mi@kot.ne.mediaone.net, stable@FreeBSD.ORG Subject: Re: isprint(3) and LANG/LOCALE In-Reply-To: <200001100505.AAA86278@rtfm.newton> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is the subject supposed to consider the LANG setting? I'd think so, but > it does not :( Send-pr? I have a bunch of jpeg-images with comments in > Russian. rdjpeg(1) reads them, but because isprint(3) says 0, prints > every character's octal value :(. Thanks! > > -mi > > #include > #include > > main(int argc, char *argv[]) { > char *c; > for(c = argv[argc-1]; *c; *c++) > printf("for %c isprint() returns %d\n", *c, isprint(*c)); > } > As you point out, the isprint(3) man page seems to suggest it does not check lang - isprint simply looks at the byte and decides if it's printable in the ASCII char set. The man page basically quotes the C ANSI standard and says isprint() tests for any printing character. The ANSI standard doesn't appear to go beyond that. Perhaps the best thing to do would be to remove the test in rdjpeg??? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 21:18:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id E247614D05 for ; Sun, 9 Jan 2000 21:18:54 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id AAA17978; Mon, 10 Jan 2000 00:17:13 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id AAA86381; Mon, 10 Jan 2000 00:17:13 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001100517.AAA86381@rtfm.newton> Subject: Re: isprint(3) and LANG/LOCALE In-Reply-To: <200001100512.AAA34272@lakes.dignus.com> from Thomas David Rivers at "Jan 10, 2000 00:12:50 am" To: Thomas David Rivers Date: Mon, 10 Jan 2000 00:17:13 -0500 (EST) Cc: stable@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Is the subject supposed to consider the LANG setting? I'd think so, => but it does not :( Send-pr? I have a bunch of jpeg-images with => comments in Russian. rdjpeg(1) reads them, but because isprint(3) => says 0, prints every character's octal value :(. Thanks! = As you point out, the isprint(3) man page seems to suggest it does not = check lang - isprint simply looks at the byte and decides if it's = printable in the ASCII char set. Well, the man page gives the list, of what the is considered printable in the ASCII charset, thus implying, there may be other lists under other charsets. That's my impression. Somehow vi(1), for example, does pay attention to the LANG when displaying characters. =Perhaps the best thing to do would be to remove the test in rdjpeg??? There may indeed be junk there. I'd love to get rdjpeg whatever vi is smoking... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 21:38:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-7-179.adsl.one.net [216.23.15.179]) by hub.freebsd.org (Postfix) with ESMTP id 15B37151FF for ; Sun, 9 Jan 2000 21:38:14 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id AAA01203; Mon, 10 Jan 2000 00:40:55 -0500 (EST) (envelope-from cokane) Date: Mon, 10 Jan 2000 00:40:54 -0500 From: Coleman Kane To: Evgeny Roubinchtein , freebsd-stable@freebsd.org Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110004054.A1181@evil.2y.net> References: <20000109214046.7913BA54DB@netcom1.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from eroubinc@u.washington.edu on Sun, Jan 09, 2000 at 06:50:22PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Obviously, you have never tried to make world with the new egcs, it is almost impossible since there are many violations of ANSI C and C++ in the code right now. The kernel does, however, properly compile (minus some ext2fs crap). --cokane Evgeny Roubinchtein had the audacity to say: > On Sun, 9 Jan 2000, Mike Harding wrote: > > > > >I'm interested in picking up the new gcc, but I was just curious as to > >when the 4.x branch becomes -STABLE, since the release is just around > >the corner. Also, that would be 4.x -STABLE, right? > > This is perhaps tangential, but if you wish to use gcc-2.95.2 for your > projects, why not install the "egcs" port (it's actually gcc-2.95.2)? > > > -- > Evgeny > > The computing field is always in need of new cliches. - Alan Perlis > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 21:56: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 23D13152D7 for ; Sun, 9 Jan 2000 21:56:05 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id VAA17840; Sun, 9 Jan 2000 21:55:46 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 09 Jan 2000 21:55:46 -0800 Date: Sun, 9 Jan 2000 21:55:46 -0800 (PST) From: Kip Macy To: David Bushong Cc: R Joseph Wright , freebsd-stable@FreeBSD.ORG Subject: Re: CPU voltage (was Re: load spike strangeness) In-Reply-To: <20000108223540.A58762@Bushong.NET> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna.lyris.com X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: david@bushong.net,rjoseph@nwlink.com,freebsd-stable@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My machine is not overclocked and I get similar results Motherboard Temp Voltages 26C / 78F / 299K Vcore1: +1.953V Vcore2: +1.953V Fan Speeds + 3.3V: +3.375V + 5.0V: +4.906V 1: 3013 rpm +12.0V: +12.625V 2: 3708 rpm -12.0V: -13.562V 3: 0 rpm - 5.0V: -5.584V On Sat, 8 Jan 2000, David Bushong wrote: > On Sat, Jan 08, 2000 at 10:03:44PM -0800, R Joseph Wright wrote: > > Awhile back I was having trouble getting through kernel compiles, the > > machine would reboot during the compile. Someone on some newsgroup said > > "are you overclocking?". I checked my settings. No, I wasn't > > overclocking. But my voltage setting looked wrong. It was set at 2.2 > > volts or whatever and I thought it was supposed to be at 2.4. So I > > changed it to 2.4. My problem was solved. I was flying through the > > compiles. Then I was looking through my motherboard manual and realized > > that it was supposed to be set at 2.2 after all. I prefer it the way it > > is though. Do you think there is anything wrong with that? > > > Hmm. lmmon -i produces some scary results: > > Voltages > > Vcore1: +2.781V > Vcore2: +1.469V > + 3.3V: +3.312V > + 5.0V: +4.932V > +12.0V: +12.250V <-- > -12.0V: -13.125V <-- > - 5.0V: -5.532V <-- > > Those look disturbingly off.. maybe this much drift is common, I don't know. > However, I never have any problem with the machine, other than this benign > occurance.. and I do tend to tax it every now and again (couple ports > building, world building, mp3 encodes, the usual). Ack, can't believe I > forgot to mention I'm running with soft updates enabled on both drives > (and root). While I was reading this thread btw, I got another spike, and > by measuring pixel widths in xload, came up with 30 pixels @ 10 seconds per > pixel, or 300 seconds, or exactly 5 minutes, which seems awfully round. > > Re: overclocking thing: ok, people, I know it's my machine. Take a chill > pill. I have a very stable CPU, a well ventilated machine, and a jumperless > motherboard that makes it very easy to switch settings. However, as I have > said, this machine has been rock solid (except for during a few of those > sketchy 3.1 release ;) I'll go ahead and try turning off the overclocking > and see if > a) it affects the voltage (which does worry me a bit) > b) I continue to see this load strangeness (I suspect I will) > > --David Bushong > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 9 22:52:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flophouse.com (flophouse.com [206.169.156.66]) by hub.freebsd.org (Postfix) with ESMTP id B370A15229 for ; Sun, 9 Jan 2000 22:52:07 -0800 (PST) (envelope-from dpassage@flophouse.com) Received: from flophouse.com (localhost [127.0.0.1]) by flophouse.com (8.9.3/8.9.3) with ESMTP id WAA07033; Sun, 9 Jan 2000 22:57:33 -0800 (PST) (envelope-from dpassage@flophouse.com) Message-Id: <200001100657.WAA07033@flophouse.com> To: Andreas Braukmann Cc: freebsd-stable@freebsd.org Subject: Re: Trouble loading installing on my Aptiva In-reply-to: Your message of "Sun, 09 Jan 2000 23:10:16 +0100." Date: Sun, 09 Jan 2000 22:57:33 -0800 From: "David G. Paschich" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > On Sun, Jan 09, 2000 at 01:05:47PM -0800, David G. Paschich wrote: > > So I just got me a shiny new IBM Aptiva with one of them wacky Athlon > > processors in it, and FreeBSD 3.x won't load on it. > ... hmm. I'm running a 'built-by-myself' Athlon machine (K7-700, > Gigabyte-Mainboard, SymbiosLogic SCSI hostadaptor, fxp network) > under -current and -stable without any problems. > > Really without any problems? No, .. of course not. > I had to _really_carefully_ select the memory. > > Athlon-boards are more then picky about memory. > Just adjust the BIOS-settings concerning the memory-timing to > some conservative values and try again. > If this doesn't help -> swap the memory. I'll try that, thanks. As an aside, the -current shapshot from Sunday booted up just fine, but I'd rather be on the -stable branch than the -current one for this machine's eventual use. Of course, I could always just wait a month for 4.0 to _become_ -stable :) -------- David G. Paschich dpassage@flophouse.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 0:12:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from exchange.prism.co.za (exchange.prism.co.za [196.34.63.66]) by hub.freebsd.org (Postfix) with ESMTP id 60EE114D1C; Mon, 10 Jan 2000 00:12:39 -0800 (PST) (envelope-from alwyns@littlecruncher.prizm.dhs.org) Received: from littlecruncher.prizm.dhs.org (196.34.63.201 [196.34.63.201]) by exchange.prism.co.za with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id CKVJLPYD; Mon, 10 Jan 2000 10:14:59 +0200 Received: by littlecruncher.prizm.dhs.org (Postfix, from userid 1001) id 55725B9; Mon, 10 Jan 2000 10:14:20 +0200 (SAST) Date: Mon, 10 Jan 2000 10:14:19 +0200 From: Alwyn Schoeman To: FreeBSD Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, "freebsd-security@FreeBSD. ORG" Subject: Re: load spike strangeness Message-ID: <20000110101419.D7053@littlecruncher.prizm.dhs.org> References: <200001090206.DAA75669@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from freebsd@gtonet.net on Sat, Jan 08, 2000 at 06:31:19PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Since when does an E-mail address require a "realname"? Only a imbecile > (IMHO) would use their real name on an e-mail that goes out to a public > list. I don't want people to know my real name or SSN or any other personal > info for that matter, NOR is it required, as far as I know. If it were to > become required, I'd prefer to "unsubscribe" than to give that info out, as > would any other intelligent person. I suggest you check your e-mail security > information again before babbling nonsense. My e-mail addy is a REAL addy > not one that goes through an anonymous re-mailer and I use it so IF I start > getting Spam I can easily rmuser it and create another to resubscribe. Do > you also use you real full name on IRC? To quote "Mr. T": "I pity da f00!" I think he was talking about the text that accompanies your e-mail address. E.g. Bill Gates and Bill Gates is the same user for human processing, but 2 completely different people when it comes to spam. Sometimes I long for the days when people on The Internet were just a few and netiquette ruled the day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 2: 7:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 287D21510D for ; Mon, 10 Jan 2000 02:07:48 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id LAA20277; Mon, 10 Jan 2000 11:07:43 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <20000109235744.01C49A54EE@netcom1.netcom.com> References: <20000109235744.01C49A54EE@netcom1.netcom.com> Date: Mon, 10 Jan 2000 10:48:07 +0100 To: Mike Harding , eroubinc@u.washington.edu From: Brad Knowles Subject: Re: When does the 4.x branch go stable? Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:57 PM -0800 on 2000/1/9, Mike Harding wrote: > mmm - I guess I am ready to go to 4.x in general, just wondering when > it would be 'safe'. This is for my home system and I would prefer to > do a source code update in place... I've been watching the -current mailing list for a while now, and what I currently see is that -CURRENT has a few niggling outstanding problems (especially on older hardware), and a few pretty major outstanding problems. My guess is that it won't be "stable" enough for what I consider to be production use until it hits 4.2 or perhaps even 4.3. Until then, I'll be glad to use the latest "stable" version of 3.x. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 2:23:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cip12.melaten.rwth-aachen.de (cip12.melaten.RWTH-Aachen.DE [134.130.92.12]) by hub.freebsd.org (Postfix) with ESMTP id 07D0C151D2 for ; Mon, 10 Jan 2000 02:23:49 -0800 (PST) (envelope-from tg@melaten.rwth-aachen.de) Received: (from tg@localhost) by cip12.melaten.rwth-aachen.de (8.9.3/8.9.3) id LAA36656; Mon, 10 Jan 2000 11:28:53 +0100 (CET) (envelope-from tg@melaten.rwth-aachen.de) X-Authentication-Warning: cip12.melaten.rwth-aachen.de: tg set sender to tg@melaten.rwth-aachen.de using -f To: freebsd-stable@freebsd.org Subject: Re: cvs commit: src/lib/libc_r/uthread uthread_detach.c uthread_fork.c uthread_gc.c uthread_poll.c uthread_priority_queue.c uthread_setschedparam.c uthread_sig.c uthread_socketpair.c uthread_spec.c References: <200001101014.CAA85841@freefall.freebsd.org> From: Thomas Gellekum In-Reply-To: Thomas Gellekum's message of "Mon, 10 Jan 2000 02:14:43 -0800 (PST)" Date: 10 Jan 2000 11:28:52 +0100 Message-ID: Lines: 18 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Gellekum writes: > tg 2000/01/10 02:14:43 PST > > Modified files: (Branch: RELENG_3) > lib/libc_r/uthread uthread_detach.c uthread_fork.c > uthread_gc.c uthread_poll.c > uthread_priority_queue.c > uthread_setschedparam.c uthread_sig.c > uthread_socketpair.c uthread_spec.c > Log: > MFC: -Wall and style(9) cleanup. Ok, that was the last part for now. libc_r in -current and -stable are now identical except for the sigset_t changes and the POSIX socket cleanup. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 2:52:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [212.84.196.35]) by hub.freebsd.org (Postfix) with ESMTP id C53AA14CB9 for ; Mon, 10 Jan 2000 02:52:43 -0800 (PST) (envelope-from news-list.freebsd.stable@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with ESMTP id LAA17016 for ; Mon, 10 Jan 2000 11:52:41 +0100 Received: by mate.bln.innominate.de (Postfix, from userid 9) id D84D72CA6E; Mon, 10 Jan 2000 11:35:46 +0100 (CET) From: news-list.freebsd.stable@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.stable Subject: vinum problem Date: 10 Jan 2000 10:35:45 GMT Organization: innominate AG, Berlin, Germany Lines: 16 Message-ID: Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 947500545 25618 10.0.0.13 (10 Jan 2000 10:35:45 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/pre-1.4-19990805 ("Preacher Man") (UNIX) (FreeBSD/4.0-CURRENT (i386)) To: stable@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have discovered some problems with vinum under 3.3-RELEASE - i wanted to create a vinum stripe over two disks - everything i got set up fine - but after setting "start_vinum" to YES - it started on bootup but somehow trashed my whole /dev directory resulting in things like fsck saying the the devices are not the correct block/char type etc. - anyone else seen anything similar ? btw. i am using soft updates - maybe a problem of the two together ? t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 3:45:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from carlton.innotts.co.uk (carlton.innotts.co.uk [212.56.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 9280D14C2F for ; Mon, 10 Jan 2000 03:45:44 -0800 (PST) (envelope-from robmel@innotts.co.uk) Received: (from uucp@localhost) by carlton.innotts.co.uk (8.9.3/8.9.3) with UUCP id LAA30208 for freebsd-stable@freebsd.org; Mon, 10 Jan 2000 11:45:40 GMT Received: from [172.16.99.111] (robslap.nadt.org.uk [172.16.99.111]) by charlie.nadt.org.uk (8.9.3/8.6.12) with ESMTP id LAA26774; Mon, 10 Jan 2000 11:40:19 GMT Mime-Version: 1.0 X-Sender: robmel@wrcmail (Unverified) Message-Id: Date: Mon, 10 Jan 2000 11:40:19 +0000 To: freebsd-stable@freebsd.org From: Robin Melville Subject: Network errors Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Should I be worried about the number of Ierrs? This has started to appear on only one host since I installed 3.3. Network interface status: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll fxp0 1500 00.a0.c9.96.9c.db 17076265 223942 8108206 2 0 fxp0 1500 wrcnet/24 tigger 17076265 223942 8108206 2 0 Our other servers on the same 100 Mbit switch also have fxp, but with only the odd one or two errors. They are K6 300/350 MHz machines, this is a P233. The man page is not too helpful -- man netstat : "The notion of errors is ill-defined." Thanks, Robin. Dmesg follows: FreeBSD 3.3-STABLE #0: Tue Dec 28 13:24:50 GMT 1999 root@nadia.nadt.org.uk:/usr/src/sys/compile/TIGGER Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233031230 Hz CPU: Pentium/P55C (233.03-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 133169152 (130048K bytes) avail memory = 126705664 (123736K bytes) Preloaded elf kernel "kernel" at 0xc028c000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ide_pci0: rev 0xd0 int a irq 11 on pci0.1.1 ahc0: rev 0x00 int a irq 10 on pci0.10.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x04 int a irq 11 on pci0.12.0 fxp0: Ethernet address 00:a0:c9:96:9c:db vga0: rev 0x65 on pci0.19.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 504MB (1032192 sectors), 1024 cyls, 16 heads, 63 S/T, 512 B/S vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) da0 at ahc0 bus 0 target 12 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 4:47:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 1AF8A1502C for ; Mon, 10 Jan 2000 04:47:03 -0800 (PST) (envelope-from jon@phoenix.welearn.com.au) Received: (from jon@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id XAA22005; Mon, 10 Jan 2000 23:46:39 +1100 (EST) (envelope-from jon) Date: Mon, 10 Jan 2000 23:46:37 +1100 From: Jonathan Michaels To: Brad Knowles Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110234635.A21865@phoenix.welearn.com.au> Mail-Followup-To: Brad Knowles , freebsd-stable@FreeBSD.ORG References: <20000109235744.01C49A54EE@netcom1.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brad Knowles on Mon, Jan 10, 2000 at 10:48:07AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG all, please excuse my slightly longish post, i'm looking at two issues here. i've finally come to terms with what "tracking -stable" actually is and what it means for me. i'm almost ready to cutover to springing for the cvsup version of kernel updating as opposed to the get the new -release cdrom and copy the new stuff over ... grin. On Mon, Jan 10, 2000 at 10:48:07AM +0100, Brad Knowles wrote: > At 3:57 PM -0800 on 2000/1/9, Mike Harding wrote: > > > mmm - I guess I am ready to go to 4.x in general, just wondering when > > it would be 'safe'. This is for my home system and I would prefer to > > do a source code update in place... how safe would a -release 'upgrade' be ? then a migration to a -stable track a bit further down the line ? i've found the best way to upgrade was to take the hot backup server, clean off the hard disk media do a fresh install of the newer operating system, reconfigure the various bits, add the required packages and then let it sit freewheeling for a few days or about a week. after no hiccups i cut over the services one at a time, till i have it all cutover and working .. then i take a dump onto tape and restore this to the former 'hot' server, which now becomes the new hot backup server. i'm lucky in that i only need one a pair of hosts to take my entire workload. just to digress a little, after i take on the tracking of -stable, this hot baackup server could serve as an installation server and the 'official' -stable tracker from which i could roll my as required freebsd editions. or am i needlessly complicating my working environemnt so that i could just track -stable .. i'm only wanting to track the kernal sources and some of the base systems toolkits as supplied with the basic 'kernel builders' installation option from the sysinstall menu. > I've been watching the -current mailing list for a while now, and > what I currently see is that -CURRENT has a few niggling outstanding > problems (especially on older hardware), and a few pretty major > outstanding problems. what sort of hardware problems, please ? not architectural, or as regards old i386dx style, or i486dx style motherboards and thier atendant isa buss structures. my couple are running very well with 2.2.7-release, but sooner or latter i wll need to get on board a more recent freebsd, if for no other reason than for teh inherant security weakness that have been fixed over the last year or so. also, i have a few adaptec aha1542b's that are running very well, some of teh newer stuff is .... those small and fragile pci buss cards tend to get damaged quickly if not handled correctly, my hands are not a agile as they used to be is what i'm getting at here. anway cheers warm regards jonathan -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 5:27:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id C2842159D9 for ; Mon, 10 Jan 2000 05:22:49 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id OAA08402; Mon, 10 Jan 2000 14:22:36 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <20000110234635.A21865@phoenix.welearn.com.au> References: <20000109235744.01C49A54EE@netcom1.netcom.com> <20000110234635.A21865@phoenix.welearn.com.au> Date: Mon, 10 Jan 2000 14:19:10 +0100 To: Jonathan Michaels From: Brad Knowles Subject: Re: When does the 4.x branch go stable? Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:46 PM +1100 2000/1/10, Jonathan Michaels wrote: > what sort of hardware problems, please ? Issues with some older Pentium motherboards apparently losing their minds (and their timing interrupts) with the new ATA driver (replaces the old wd driver). There are also some issues with laptops and PC Cards, especially CardBus cards. > not architectural, or as regards old i386dx style, or i486dx > style motherboards and thier atendant isa buss structures. > > my couple are running very well with 2.2.7-release, but sooner > or latter i wll need to get on board a more recent freebsd, if > for no other reason than for teh inherant security weakness > that have been fixed over the last year or so. also, i have a > few adaptec aha1542b's that are running very well, some of teh > newer stuff is .... those small and fragile pci buss cards tend > to get damaged quickly if not handled correctly, my hands are > not a agile as they used to be is what i'm getting at here. Watch the older cards. I think that AHA152x series support was just recently added back into 3.x-STABLE, specifically with 3.4-RELEASE (at least, I recall seeing that when last I read the RELEASE_NOTES). I don't recall whether or not they're supported under 4.x-CURRENT. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 6:13:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 3F5E014E4A for ; Mon, 10 Jan 2000 06:13:44 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id JAA25427; Mon, 10 Jan 2000 09:13:35 -0500 (EST) From: "Allen Pulsifer" To: "freebsd-stable@FreeBSD. ORG" Cc: Subject: RE: Next release should be called 5.0 (was:4.4 BSD forever?) Date: Mon, 10 Jan 2000 09:13:35 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000109042111.D0285A80F@kendra.ne.mediaone.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to agree with this poster. The next release should be called FreeBSD 5.0. "BSD 4.4" is a desciptive term still used to describe a whole family of OS's. People outside the FreeBSD circle are going to be confused between BSD 4.4 and FreeBSD 4.4. This can easily be avoided, at no cost, by calling the next release FreeBSD 5.0. Allen > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Snuffles on Sonata > Sent: Saturday, January 08, 2000 11:21 PM > To: stable@FreeBSD.ORG > Subject: Re: 4.4 BSD forever? > > > Some of us remember 4.1 and 4.2 as well. :-) > > From a pragmatic standpoint, going to release FreeBSD 5.0 and > skipping all 4.x versions avoids confusion and honors the Source. > With this, the sequence remains linear and obvious, and has a > specific reason. > > -ahd- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 6:16:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by hub.freebsd.org (Postfix) with ESMTP id A5A2A14BD8 for ; Mon, 10 Jan 2000 06:16:18 -0800 (PST) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (localhost [127.0.0.1]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id JAA87248 for ; Mon, 10 Jan 2000 09:16:17 -0500 (EST) (envelope-from jim@thehousleys.net) Message-ID: <3879E9B1.E11EC8D8@thehousleys.net> Date: Mon, 10 Jan 2000 09:16:17 -0500 From: "James E. Housley" X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Allen Pulsifer wrote: > > "BSD 4.4" is a desciptive term still used to describe a whole > family of OS's. People outside the FreeBSD circle are going to be > confused between BSD 4.4 and FreeBSD 4.4. This can easily be avoided, > at no cost, by calling the next release FreeBSD 5.0. > I agree too. -- James E. Housley "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 7:11:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 4743E14D46 for ; Mon, 10 Jan 2000 07:11:35 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id PAA03025; Mon, 10 Jan 2000 15:11:25 GMT (envelope-from joe) Date: Mon, 10 Jan 2000 15:11:25 +0000 From: Josef Karthauser To: "James E. Housley" Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) Message-ID: <20000110151125.J25193@florence.pavilion.net> References: <3879E9B1.E11EC8D8@thehousleys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <3879E9B1.E11EC8D8@thehousleys.net> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 09:16:17AM -0500, James E. Housley wrote: > Allen Pulsifer wrote: > > > > "BSD 4.4" is a desciptive term still used to describe a whole > > family of OS's. People outside the FreeBSD circle are going to be > > confused between BSD 4.4 and FreeBSD 4.4. This can easily be avoided, > > at no cost, by calling the next release FreeBSD 5.0. > > > I agree too. I don't... FreeBSD is FreeBSD, and BSD is BSD - IMHO it doesn't matter that the people who don't know the difference get confused, if they're interested they'll find out. The versioning model of FreeBSD is good at the moment and I don't think that it matters that we have a version 4.4 or 4.5. If you use 5.0 for something else you'll confuse all of the developers, which is worse IMHO than confusing a few people outside the circle. Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 8:21:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from outlier.axl.net (outlier.axl.net [216.66.11.20]) by hub.freebsd.org (Postfix) with SMTP id 960F215165 for ; Mon, 10 Jan 2000 08:21:50 -0800 (PST) (envelope-from matt@axl.net) Received: (qmail 50255 invoked from network); 10 Jan 2000 16:21:48 -0000 Received: from ws-01.matthennigus.lightningdsl.net (HELO sinister) (216.66.30.66) by outlier.axl.net with SMTP; 10 Jan 2000 16:21:48 -0000 Reply-To: From: "Matthew B. Henniges" To: "FreeBSD Stable" Subject: uptime abort trap Date: Mon, 10 Jan 2000 11:23:56 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all- I have a cronjob in /etc/crontab: */1 * * * * root /usr/bin/uptime >> /var/log/load about once every 2 days, I find a mail like this in my mailbox. From: Cron Daemon [root@outlier.axl.net] Sent: Friday, January 07, 2000 5:11 PM To: root@outlier.axl.net Subject: Cron /usr/bin/uptime >> /var/log/load Abort trap Does anybody know what this means? Thanks in advance for the help. -Matt matt@outlier:~> uname -a FreeBSD outlier.axl.net 3.4-STABLE FreeBSD 3.4-STABLE #0: Mon Dec 20 05:29:28 EST 1999 root@outlier.axl.net:/usr/src/sys/compile/OUTLIER i386 matt@outlier:~> dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #0: Mon Dec 20 05:29:28 EST 1999 root@outlier.axl.net:/usr/src/sys/compile/OUTLIER Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 258351104 (252296K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0258000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 chip3: rev 0x02 on pci0.7.3 vga0: rev 0x7a int a irq 18 on pci0.11.0 ahc0: rev 0x00 int a irq 16 on pci0.15.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x30 int a irq 19 on pci0.17.0 xl0: Ethernet address: 00:50:04:63:36:2f xl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 250 packets/entry by default Waiting 10 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changingda0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) da1 at ahc0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) Matthew B. Henniges Axl.net Communications http://www.axl.net (203) 552-1714 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 8:41:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 55ED314C21 for ; Mon, 10 Jan 2000 08:41:51 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id AF8ECE8A8; Mon, 10 Jan 2000 11:41:49 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id LAA08379; Mon, 10 Jan 2000 11:41:49 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14458.3021.635905.646030@onceler.kcilink.com> Date: Mon, 10 Jan 2000 11:41:49 -0500 (EST) To: Szilveszter Adam Cc: freebsd-stable@freebsd.org Subject: Re: Help _please_ "make world" faila In-Reply-To: <20000109213340.A24196@petra.hos.u-szeged.hu> References: <200001091832.KAA13213@netcom.com> <20000109213340.A24196@petra.hos.u-szeged.hu> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "SA" == Szilveszter Adam writes: SA> Is the enclosed output all that you get? If so, am I right in SA> assuming that you do not delete /usr/obj/* before each build? IMHO SA> it is pretty much compulsory, esp if you also cvsup in the SA> meantime, that is /usr/src changes. Doesn't make world do that for you? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9: 8:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-7-38.adsl.one.net [216.23.15.38]) by hub.freebsd.org (Postfix) with ESMTP id EF8AA14FE9 for ; Mon, 10 Jan 2000 09:08:32 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id MAA02715; Mon, 10 Jan 2000 12:10:29 -0500 (EST) (envelope-from cokane) Date: Mon, 10 Jan 2000 12:10:29 -0500 From: Coleman Kane To: Kip Macy Cc: David Bushong , R Joseph Wright , freebsd-stable@FreeBSD.ORG Subject: Re: CPU voltage (was Re: load spike strangeness) Message-ID: <20000110121029.A2688@evil.2y.net> References: <20000108223540.A58762@Bushong.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kip@lyris.com on Mon, Jan 10, 2000 at 12:57:21AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that these readings have to do not only with the uneven voltages in the power supply, b ut also the accuracy of the instruments used to record them. --cokane Kip Macy had the audacity to say: > My machine is not overclocked and I get similar results > > > > Motherboard Temp Voltages > > 26C / 78F / 299K Vcore1: +1.953V > Vcore2: +1.953V > Fan Speeds + 3.3V: +3.375V > + 5.0V: +4.906V > 1: 3013 rpm +12.0V: +12.625V > 2: 3708 rpm -12.0V: -13.562V > 3: 0 rpm - 5.0V: -5.584V > > > On Sat, 8 Jan 2000, David Bushong wrote: > > > On Sat, Jan 08, 2000 at 10:03:44PM -0800, R Joseph Wright wrote: > > > Awhile back I was having trouble getting through kernel compiles, the > > > machine would reboot during the compile. Someone on some newsgroup said > > > "are you overclocking?". I checked my settings. No, I wasn't > > > overclocking. But my voltage setting looked wrong. It was set at 2.2 > > > volts or whatever and I thought it was supposed to be at 2.4. So I > > > changed it to 2.4. My problem was solved. I was flying through the > > > compiles. Then I was looking through my motherboard manual and realized > > > that it was supposed to be set at 2.2 after all. I prefer it the way it > > > is though. Do you think there is anything wrong with that? > > > > > Hmm. lmmon -i produces some scary results: > > > > Voltages > > > > Vcore1: +2.781V > > Vcore2: +1.469V > > + 3.3V: +3.312V > > + 5.0V: +4.932V > > +12.0V: +12.250V <-- > > -12.0V: -13.125V <-- > > - 5.0V: -5.532V <-- > > > > Those look disturbingly off.. maybe this much drift is common, I don't know. > > However, I never have any problem with the machine, other than this benign > > occurance.. and I do tend to tax it every now and again (couple ports > > building, world building, mp3 encodes, the usual). Ack, can't believe I > > forgot to mention I'm running with soft updates enabled on both drives > > (and root). While I was reading this thread btw, I got another spike, and > > by measuring pixel widths in xload, came up with 30 pixels @ 10 seconds per > > pixel, or 300 seconds, or exactly 5 minutes, which seems awfully round. > > > > Re: overclocking thing: ok, people, I know it's my machine. Take a chill > > pill. I have a very stable CPU, a well ventilated machine, and a jumperless > > motherboard that makes it very easy to switch settings. However, as I have > > said, this machine has been rock solid (except for during a few of those > > sketchy 3.1 release ;) I'll go ahead and try turning off the overclocking > > and see if > > a) it affects the voltage (which does worry me a bit) > > b) I continue to see this load strangeness (I suspect I will) > > > > --David Bushong > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:11:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AB5D915252 for ; Mon, 10 Jan 2000 09:11:51 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id JAA94573; Mon, 10 Jan 2000 09:11:50 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 09:11:50 -0800 From: "David O'Brien" To: Michael Robinson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.4 BSD forever? Message-ID: <20000110091150.A94525@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001090610.OAA09477@netrinsics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <200001090610.OAA09477@netrinsics.com> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >the 5.x releases, I'm gonna have to think about taking down > >the ole poster with `4.4 > 5.4' on it.... > > > >(not that that would be a *bad* thing, I just wonder if I can > >find where said poster is hanging in this mess) > > Your Mt. Xinu poster is being underutilized (and underappreciated). It isn't a Mt. Xinu poster. It is a BSDI poster with the Daemon on it and it did say "4.4 > 5.4". "5.4" refered to System V Rel. 4., which was fairly new at the time. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:14:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7725D14CFE for ; Mon, 10 Jan 2000 09:14:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id JAA94628; Mon, 10 Jan 2000 09:14:55 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 09:14:55 -0800 From: "David O'Brien" To: Joseph Scott Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.4 BSD forever? Message-ID: <20000110091455.B94525@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <010501bf5989$2c4b7ec0$0200000a@danco.home> <3877057D.30063B1B@owp.csus.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <3877057D.30063B1B@owp.csus.edu> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 08, 2000 at 01:38:05AM -0800, Joseph Scott wrote: > > Perhaps we should skip version 4.4 of FreeBSD out of respect for our > fore fathers. ( IE: release versions 4.0, 4.1, 4.2, 4.3, 4.5 ). > > It would kind of feel strange to have a release version of 4.4 for > FreeBSD. If I have anything to do with it, there will be a FreeBSD 4.5 so the world will know what comes after 4.4BSD. The only nostalgic issues is if we should release the 4.x series as "4.xFreeBSD". -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:17:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BBA4F14E3C for ; Mon, 10 Jan 2000 09:17:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id JAA94654; Mon, 10 Jan 2000 09:17:04 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 09:17:04 -0800 From: "David O'Brien" To: Johan Petersson , freebsd-stable@FreeBSD.ORG Subject: Re: vim-5.5.67 Message-ID: <20000110091704.C94525@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000108165314.E2853@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <20000108165314.E2853@marder-1> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 08, 2000 at 04:53:14PM +0000, Mark Ovens wrote: > Use the vim-lite port, or build vim5 using > > # make LITE=yes install > > (which is all the vim-lite port does) Acutally if you build Vim locally on an X-less machine, the X11 support will keep out since you don't the libs + headers. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:18:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 2A72514E3C for ; Mon, 10 Jan 2000 09:18:34 -0800 (PST) (envelope-from nasby@shell-1.enteract.com) Received: from shell-1.enteract.com (nasby@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id LAA32114 for ; Mon, 10 Jan 2000 11:18:33 -0600 (CST) (envelope-from nasby@shell-1.enteract.com) Received: (from nasby@localhost) by shell-1.enteract.com (8.9.3/8.9.3) id LAA94642 for freebsd-stable@freebsd.org; Mon, 10 Jan 2000 11:18:33 -0600 (CST) (envelope-from nasby) Date: Mon, 10 Jan 2000 11:18:33 -0600 From: "Jim C. Nasby" To: freebsd-stable@freebsd.org Subject: Re: vinum problem Message-ID: <20000110111833.E83528@enteract.com> Reply-To: jim@nasby.net Mail-Followup-To: freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-Operating-System: FreeBSD 3.3-STABLE i386 X-Distributed: Join the Effort! http://www.distributed.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which devices is it complaining about? I found it very easy to accidentally refer to the character/block devices (ie: /dev/vinum/raid0) at times during vinum setup instead of the raw devices (ie: /dev/vinum/rraid0). This will definitely cause some odd problems. I don't remember the step offhand where you have to use the raw device (newfs?), but if you used the block device instead you'll have to rebuild your vinum setup. On Mon, Jan 10, 2000 at 10:35:45AM +0000, Thomas Graichen wrote: > i have discovered some problems with vinum under 3.3-RELEASE - i > wanted to create a vinum stripe over two disks - everything i got > set up fine - but after setting "start_vinum" to YES - it started > on bootup but somehow trashed my whole /dev directory resulting > in things like fsck saying the the devices are not the correct > block/char type etc. - anyone else seen anything similar ? > > btw. i am using soft updates - maybe a problem of the two together ? > > t > > -- > graichen@innominate.de > innominate AG > networking people > fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain-candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:24:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 2BC5615224; Mon, 10 Jan 2000 09:24:17 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 7480CE8A5; Mon, 10 Jan 2000 12:24:16 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id MAA08671; Mon, 10 Jan 2000 12:24:16 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14458.5568.152019.715536@onceler.kcilink.com> Date: Mon, 10 Jan 2000 12:24:16 -0500 (EST) To: ports@freebsd.org, freebsd-stable@freebsd.org Subject: question on necessity of tcp_wrappers port X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to me that since 3.4 has tcp wrappers integrated into it (inetd has support built in, and libwrap is there) that the tcp_wrappers port is unnecessary. It really confused me when I did the install because the tcp_wrappers package was offered to be installed during the installation, and was not marked as "obsolete" in any way. Perhaps it should be marked unnecessary or "for backwards compat only"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:28:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 18F741516E for ; Mon, 10 Jan 2000 09:28:31 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 127icE-0001IB-00; Mon, 10 Jan 2000 09:28:26 -0800 Date: Mon, 10 Jan 2000 09:28:24 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Allen Pulsifer Cc: "freebsd-stable@FreeBSD. ORG" , jkh@zippy.cdrom.com Subject: RE: Next release should be called 5.0 (was:4.4 BSD forever?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Allen Pulsifer wrote: > I have to agree with this poster. The next release should be > called FreeBSD 5.0. > > "BSD 4.4" is a desciptive term still used to describe a whole > family of OS's. People outside the FreeBSD circle are going to be > confused between BSD 4.4 and FreeBSD 4.4. This can easily be avoided, > at no cost, by calling the next release FreeBSD 5.0. > > Allen Actually, no. The distribution is called 4.4BSD, not BSD 4.4. The same goes for 4.1 or 4.2 which were known as 4.1BSD and 4.2BSD respectively. Anyone who understands what BSD is, will know the difference. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:42:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 951F215224 for ; Mon, 10 Jan 2000 09:42:21 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id MAA01921 for ; Mon, 10 Jan 2000 12:42:17 -0500 (EST) From: "Allen Pulsifer" To: "freebsd-stable@FreeBSD. ORG" Subject: RE: Next release should be called 5.0 (was:4.4 BSD forever?) Date: Mon, 10 Jan 2000 12:42:18 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, no. The distribution is called 4.4BSD, not BSD 4.4. The same > goes for 4.1 or 4.2 which were known as 4.1BSD and 4.2BSD respectively. > Anyone who understands what BSD is, will know the difference. You're right. My bad. 4.4BSD. See how easy it is to get it confused? Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:48:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B3A2414D21 for ; Mon, 10 Jan 2000 09:48:39 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id JAA94795; Mon, 10 Jan 2000 09:48:34 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 09:48:34 -0800 From: "David O'Brien" To: Coleman Kane Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110094834.D94525@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000109214046.7913BA54DB@netcom1.netcom.com> <20000110004054.A1181@evil.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <20000110004054.A1181@evil.2y.net> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 12:40:54AM -0500, Coleman Kane wrote: > Obviously, you have never tried to make world with the new egcs, it is almost WHY do you need to make world with GCC 2.95.2? Gcc 2.7.2 acutally produces smaller code. For some things even faster code. What is so glammorous about a Gcc 2.95 built world and kernel? Use the base compiler to compile the product and install the `egcs' port for your own code. The big short falling with Gcc 2.7.2 is a total piece of crap C++ compiler. Since the only thing written in C++ in /usr/src/ is groff (and very old style C++), who cares. > impossible since there are many violations of ANSI C and C++ in the code right > now. The kernel does, however, properly compile (minus some ext2fs crap). Send patches then, if you are a programmer. -- -- David (obrien@FreeBSD.org) [maintainer of /usr/src/contrib/gcc, `gcc-devel', `egcs', `pgcc'] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 9:53:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1EBCD14FA6 for ; Mon, 10 Jan 2000 09:53:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id JAA94843; Mon, 10 Jan 2000 09:53:27 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 09:53:27 -0800 From: "David O'Brien" To: Brad Knowles Cc: Jonathan Michaels , freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110095327.E94525@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000109235744.01C49A54EE@netcom1.netcom.com> <20000110234635.A21865@phoenix.welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad please don't spread falsness. On Mon, Jan 10, 2000 at 02:19:10PM +0100, Brad Knowles wrote: > There are also some issues with laptops and PC Cards, especially > CardBus cards. No version of FreeBSD does or ever has supported CardBus. So there can't be any 4.0 issues here. There are issues with PCCard support (ie, the 16-bit, not 32-bit devices). > > few adaptec aha1542b's that are running very well, some of teh ..snip.. > Watch the older cards. I think that AHA152x series support was 154x != 152x. FreeBSD has *always* supported the AHA-154x [minus a a month or so after the CAM switch while the `aha' driver was being updated]. > just recently added back into 3.x-STABLE, specifically with > 3.4-RELEASE (at least, I recall seeing that when last I read the > RELEASE_NOTES). I don't recall whether or not they're supported > under 4.x-CURRENT. The `aic' driver came into -CURRENT first as it has to. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 10: 4:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 70BE514C03; Mon, 10 Jan 2000 10:04:09 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id NAA34213; Mon, 10 Jan 2000 13:03:50 -0500 (EST) (envelope-from mi) Message-Id: <200001101803.NAA34213@misha.cisco.com> Subject: Re: When does the 4.x branch go stable? In-Reply-To: <20000110094834.D94525@relay.nuxi.com> from "David O'Brien" at "Jan 10, 2000 09:48:34 am" To: obrien@FreeBSD.ORG Date: Mon, 10 Jan 2000 13:03:50 -0500 (EST) Cc: Coleman Kane , freebsd-stable@FreeBSD.ORG Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien once wrote: > WHY do you need to make world with GCC 2.95.2? Gcc 2.7.2 acutally > produces smaller code. For some things even faster code. What is so > glammorous about a Gcc 2.95 built world and kernel? FYI, I put together the http://virtual-estates.net/bm/ , although the latest was 2.95.1 back then. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 10: 8: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 4557E14A03 for ; Mon, 10 Jan 2000 10:07:50 -0800 (PST) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id TAA07362; Mon, 10 Jan 2000 19:07:35 +0100 (MET) Received: by petra.hos.u-szeged.hu (Linux Smail3.2.0.92 #1) id m127jHX-000pAuC; Mon, 10 Jan 2000 18:11:07 +0000 () Date: Mon, 10 Jan 2000 19:11:07 +0100 From: Szilveszter Adam To: freebsd-stable@freebsd.org Subject: Help _please_ "make world" faila Message-ID: <20000110191107.B31598@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-stable@freebsd.org References: <200001091832.KAA13213@netcom.com> <20000109213340.A24196@petra.hos.u-szeged.hu> <14458.3021.635905.646030@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <14458.3021.635905.646030@onceler.kcilink.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 11:41:49AM -0500, Vivek Khera wrote: > >>>>> "SA" == Szilveszter Adam writes: > > SA> Is the enclosed output all that you get? If so, am I right in > SA> assuming that you do not delete /usr/obj/* before each build? IMHO > SA> it is pretty much compulsory, esp if you also cvsup in the > SA> meantime, that is /usr/src changes. > > Doesn't make world do that for you? Hi! As you could see from the enclosed logs, what it does is that it removes the immutable flags from the /usr/obj/usr/src/tmp dir (temp build tree) and then rm -rf-es that directory. Cut'n'paste from my own logs: root@fonix - 103 # make buildworld -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp -------------------------------------------------------------- >>> Making make -------------------------------------------------------------- For more, see /usr/src/Makefile, /usr/src/Makefile.inc0 and /usr/src/Makefile.inc1 And IMHO it is on purpose. If the code in /usr/src has not changed since your last compile much then you can recompile the system real quick (I measured about 40 mins vs the normal 1 hour 45 mins) if you just made some minor change to, say some of the utils that are not in the toolchain used to build the system (or, if you discover that the code is broken for some reason and you fix it.) In these cases it is enough to say 'make -DNOCLEAN buildworld' and the work that is once done will not have to be done again, it only recompiles the part that has changed. But otherwise keeping those now-stale obj files is not what we want, we want the new source in /usr/src to be used. Therefore it is highly recommended that you blow /usr/obj/* after you're finished. As a bonus, you even get some 150Megs of this disk space back, which is not bad, either.:-) Regards: Szilveszter ADAM -- ------------------------------------------------------------------------------- * Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu * * Homepage : none * alternate email: cc@flanker.itl.net.ua * * Finger sziszi@petra.hos.u-szeged.hu for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 10:27: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7D7B014D6B for ; Mon, 10 Jan 2000 10:27:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA98697; Mon, 10 Jan 2000 10:26:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Allen Pulsifer" Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) In-reply-to: Your message of "Mon, 10 Jan 2000 09:13:35 EST." Date: Mon, 10 Jan 2000 10:26:39 -0800 Message-ID: <98695.947528799@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have to agree with this poster. The next release should be > called FreeBSD 5.0. Guys, guys, can we end this discussion now? A new version numbering scheme was already chosen for 3.0 and we're sticking with it, up to and including release 4.4. None of this discussion has come even close to making me change my mind, so unless you guys have some more substantive arguments you've yet to trot out yet, I honestly have to recommend that you save your fingers the wear-and-tear. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 10:44:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by hub.freebsd.org (Postfix) with ESMTP id 7903A1530C for ; Mon, 10 Jan 2000 10:44:31 -0800 (PST) (envelope-from n4cnw@springmail.com) Received: from smui2.atl.mindspring.net (smui2.atl.mindspring.net [207.69.200.123]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id NAA29557 for ; Mon, 10 Jan 2000 13:44:29 -0500 (EST) Received: by smui2.atl.mindspring.net id NAA0000019160; Mon, 10 Jan 2000 13:44:29 -0500 (EST) Date: Mon, 10 Jan 2000 13:44:29 -0500 From: Mike Murphree To: freebsd-stable@freebsd.org Reply-To: n4cnw@springmail.com Subject: Ports Y2K problem? Message-ID: X-Originating-IP: 12.13.248.12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple of days ago I cvsuped from 3.3-stable to 3.4 stable. Afterwards I did make world, rebuilt the kernel, and also updated the ports (via cvsup). I then built the graphics/camediacontrol port and noticed afterwards when looking at the man page for it, that the date at the bottom was Jan 8, 1900. Has this been reported before? Thanks, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 11: 9:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 348A7157F5 for ; Mon, 10 Jan 2000 11:09:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id LAA95310; Mon, 10 Jan 2000 11:09:37 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 11:09:36 -0800 From: "David O'Brien" To: Mikhail Teterin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110110936.A95288@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000110094834.D94525@relay.nuxi.com> <200001101803.NAA34213@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <200001101803.NAA34213@misha.cisco.com> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 01:03:50PM -0500, Mikhail Teterin wrote: > FYI, I put together the http://virtual-estates.net/bm/ , although the > latest was 2.95.1 back then. But your table doesn't say which compiler was used for what. Thus I can't tell what that table is telling me. You need 8 figures in that table to tell us anything about the compiler. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 11:12:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hawaii.rr.com (hnlmail3.hawaii.rr.com [24.25.227.37]) by hub.freebsd.org (Postfix) with ESMTP id D381915372 for ; Mon, 10 Jan 2000 11:12:46 -0800 (PST) (envelope-from art@hawaii.rr.com) Received: from taz ([24.31.76.79]) by hawaii.rr.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 10 Jan 2000 09:11:42 -1000 Message-Id: <3.0.6.32.20000110091234.008f4100@pop-server.hawaii.rr.com> X-Sender: art@pop-server.hawaii.rr.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 10 Jan 2000 09:12:34 -1000 To: From: "Art Neilson, WH7N" Subject: Re: uptime abort trap Cc: stable@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ##################################################################### # DANGER! WARNING! LOOK OUT! VORSICHT! # # This is the *system* crontab file, used by the system to execute # commands on behalf of users. It is the old BSD crontab file, # and it's format may be different than expected. # # DO NOT use the crontab -u root -e command to edit this file, edit # it directly with vi and beware the file format is different than # the SYSV crontab file format! # # Please see crontab(1) and crontab(5) for info on the standard # AT&T SYSV crontab facility available on the system (var/cron/tabs). # ##################################################################### At 11:23 AM 1/10/00 -0500, you wrote: >Hello all- > >I have a cronjob in /etc/crontab: > >*/1 * * * * root /usr/bin/uptime >> >/var/log/load > > >about once every 2 days, I find a mail like this in my mailbox. > > >From: Cron Daemon [root@outlier.axl.net] >Sent: Friday, January 07, 2000 5:11 PM >To: root@outlier.axl.net >Subject: Cron /usr/bin/uptime >> /var/log/load > >Abort trap > > > >Does anybody know what this means? > >Thanks in advance for the help. > >-Matt > > >matt@outlier:~> uname -a >FreeBSD outlier.axl.net 3.4-STABLE FreeBSD 3.4-STABLE #0: Mon Dec 20 >05:29:28 EST 1999 root@outlier.axl.net:/usr/src/sys/compile/OUTLIER >i386 > >matt@outlier:~> dmesg >Copyright (c) 1992-1999 FreeBSD Inc. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. >FreeBSD 3.4-STABLE #0: Mon Dec 20 05:29:28 EST 1999 > root@outlier.axl.net:/usr/src/sys/compile/OUTLIER >Timecounter "i8254" frequency 1193182 Hz >CPU: Celeron (686-class CPU) > Origin = "GenuineIntel" Id = 0x665 Stepping = 5 > >Features=0x183fbffCMOV,PAT,PSE36,MMX,FXSR> >real memory = 268435456 (262144K bytes) >avail memory = 258351104 (252296K bytes) >Programming 24 pins in IOAPIC #0 >FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 >Preloaded elf kernel "kernel" at 0xc0258000. >Pentium Pro MTRR support enabled >Probing for devices on PCI bus 0: >chip0: rev 0x03 on pci0.0.0 >chip1: rev 0x03 on pci0.1.0 >chip2: rev 0x02 on pci0.7.0 >chip3: rev 0x02 on pci0.7.3 >vga0: rev 0x7a int a irq 18 on >pci0.11.0 >ahc0: rev 0x00 int a irq 16 on pci0.15.0 >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs >xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x30 int a irq 19 on pci0.17.0 >xl0: Ethernet address: 00:50:04:63:36:2f >xl0: autoneg complete, link status good (full-duplex, 100Mbps) >Probing for devices on PCI bus 1: >Probing for PnP devices: >Probing for devices on the ISA bus: >sc0 on isa >sc0: VGA color <16 virtual consoles, flags=0x0> >atkbdc0 at 0x60-0x6f on motherboard >atkbd0 irq 1 on isa >fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa >fdc0: FIFO enabled, 8 bytes threshold >fd0: 1.44MB 3.5in >vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa >npx0 on motherboard >npx0: INT 16 interface >APIC_IO: Testing 8254 interrupt delivery >APIC_IO: routing 8254 via pin 2 >IP packet filtering initialized, divert disabled, rule-based forwarding >disabled, default to accept, logging limited to 250 packets/entry by default >Waiting 10 seconds for SCSI devices to settle >SMP: AP CPU #1 Launched! >changingda0 at ahc0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI-3 device >da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing >Enabled >da0: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) >da1 at ahc0 bus 0 target 6 lun 0 >da1: Fixed Direct Access SCSI-3 device >da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing >Enabled >da1: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) > >Matthew B. Henniges >Axl.net Communications >http://www.axl.net >(203) 552-1714 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > -- __ / ) _/_ It is a capital mistake to theorise before one has data. /--/ __ / Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III, WH7N Bank of Hawaii Tech Support art@hawaii.rr.com, art@boh.com, ah6pz@arrl.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 11:36:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5871214D21; Mon, 10 Jan 2000 11:36:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA32038; Mon, 10 Jan 2000 12:36:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA11612; Mon, 10 Jan 2000 12:36:24 -0700 (MST) Message-Id: <200001101936.MAA11612@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 10 Jan 2000 09:53:27 PST." <20000110095327.E94525@relay.nuxi.com> References: <20000110095327.E94525@relay.nuxi.com> <20000109235744.01C49A54EE@netcom1.netcom.com> <20000110234635.A21865@phoenix.welearn.com.au> Date: Mon, 10 Jan 2000 12:36:24 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000110095327.E94525@relay.nuxi.com> "David O'Brien" writes: : 154x != 152x. FreeBSD has *always* supported the AHA-154x [minus a a : month or so after the CAM switch while the `aha' driver was being : updated]. This is wrong. The cam code in the FreeBSD has always supported the 1542 via the aha driver. It was a requirement for the integration, which is why I wrote it in the first place. Got in touble with my boss for writing it even no less. There were some problems with the 1542B for a short period of time, and the 1542A still doesn't work (although I now have hardware, I've been busy on other projects). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 12: 1:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-69.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.197]) by hub.freebsd.org (Postfix) with ESMTP id E3F7215337 for ; Mon, 10 Jan 2000 12:01:31 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA26417; Mon, 10 Jan 2000 20:01:25 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00480; Mon, 10 Jan 2000 08:59:24 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001100859.IAA00480@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Mikhail Teterin Cc: stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: PPP: a big disappointment of 3.4 In-Reply-To: Message from Mikhail Teterin of "Sun, 09 Jan 2000 10:41:51 EST." <200001091541.KAA74870@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jan 2000 08:59:24 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yesterday, I upgraded my father's 3.0-CURRENT to the 3.4 and now he is > unable to get online. When ppp's chat script completes, ppp logs > > Warning: truncated pap header (0 > 5) > > several times and proceeds to redialing. The /etc/ppp/ppp.conf is > the same as before. The ISP is Ziplink. He says, there were occasional > problems getting online before, but last night we were unable to do it > at all. > > Sorry, I typed the message by memory and do not have the log here -- > his machine is off-line... I'm going to bring an older ppp to him (from > 3.2-STABLE) to see if it will work better. Any clues? I think you'll need to find out what the exact message was. If it was perhaps auth_ReadHeader: Short packet header (4 > 0) ! then you're receiving an empty authentication packet. Older (3.0) versions of ppp would probably happily ignore this. Your best bet is to ``set log physical'' and send me the output - I should be able to determine if this is the case. > -mi -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 12: 2: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-69.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.197]) by hub.freebsd.org (Postfix) with ESMTP id 6400A1534A for ; Mon, 10 Jan 2000 12:01:33 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA26420; Mon, 10 Jan 2000 20:01:26 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00425; Mon, 10 Jan 2000 08:02:51 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001100802.IAA00425@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: "Mr. K." Cc: stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: process stuck in ttywri In-Reply-To: Message from "Mr. K." of "Sat, 08 Jan 2000 10:59:11 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jan 2000 08:02:51 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is the second time I've seen this on two completely different > machines (different network, different configuration, different state) so > I'm wondering if anyone else has run into it. What happens is while I'm > doing a make, one of the processes will get stuck. If I look at top, I > will see that one of the processes is stuck in ttywri. I know I have very > little information so I don't expect any solutions, but I was only > wondering if maybe someone else has run into this also, or maybe it was > already fixed? Also, if anyone wants to tell me something specific I > should look for next time it happens... > > FreeBSD [censored].home.com 3.4-STABLE FreeBSD 3.4-STABLE #1: Sun > Dec 19 04:22:13 GMT 1999 > root@[censored].home.com:/usr/src/sys/compile/HOMER i386 I saw this twice in one day on my back-end box running -current from December 4. I was (strangely enough) running ppp, and conveniently, ``show physical'' shows the results of an ioctl(TIOCOUTQ). The tty had (from memory) about 1700 bytes in the output queue. I was still receiving data but the output queue was jammed and the tty (correctly) wasn't select()ing for write. Unfortunately, as this is a TA, I had no CTS light to check, but I assume CTS was not high and that the modem at the other end was having problems..... I actually wrote it off to a dodgy TA as I've never seen the problem since :-/ -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 12:34:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-4-4.adsl.one.net [216.2.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 4977E14ED5; Mon, 10 Jan 2000 12:34:16 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id PAA40893; Mon, 10 Jan 2000 15:37:04 -0500 (EST) (envelope-from cokane) Date: Mon, 10 Jan 2000 15:37:03 -0500 From: Coleman Kane To: "David O'Brien" Cc: Coleman Kane , freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110153703.A19250@evil.2y.net> References: <20000109214046.7913BA54DB@netcom1.netcom.com> <20000110004054.A1181@evil.2y.net> <20000110094834.D94525@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000110094834.D94525@relay.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Jan 10, 2000 at 12:49:21PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, GCC 2.95.x can be patched for pentium, ppro, and k6 optimization to make your programs run faster and more efficiently. If you could compile the base system with it, you would glean more performance from the box. If you go to http://www.goof.com/pcg/ you can see what I'm talking about, there is also a port in /usr/ports/lang/pgcc. --cokane David O'Brien had the audacity to say: > On Mon, Jan 10, 2000 at 12:40:54AM -0500, Coleman Kane wrote: > > Obviously, you have never tried to make world with the new egcs, it is almost > > WHY do you need to make world with GCC 2.95.2? Gcc 2.7.2 acutally > produces smaller code. For some things even faster code. What is so > glammorous about a Gcc 2.95 built world and kernel? > > Use the base compiler to compile the product and install the `egcs' port > for your own code. The big short falling with Gcc 2.7.2 is a total piece > of crap C++ compiler. Since the only thing written in C++ in /usr/src/ > is groff (and very old style C++), who cares. > > > impossible since there are many violations of ANSI C and C++ in the code right > > now. The kernel does, however, properly compile (minus some ext2fs crap). > > Send patches then, if you are a programmer. > > -- > -- David (obrien@FreeBSD.org) > [maintainer of /usr/src/contrib/gcc, `gcc-devel', `egcs', `pgcc'] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 14:12: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wookie.bellsouth.cl (bellsouth.cl [206.48.84.212]) by hub.freebsd.org (Postfix) with ESMTP id B3FFE14A29 for ; Mon, 10 Jan 2000 14:11:55 -0800 (PST) (envelope-from marcelo@msm.cl) Received: from sinner.msm.cl ([206.48.86.98]) by wookie.bellsouth.cl (8.8.8/8.8.8) with ESMTP id TAA20126 for ; Mon, 10 Jan 2000 19:11:23 -0300 Message-Id: <4.2.0.58.20000110191137.00b8eb80@192.168.1.10> X-Sender: miturbe@192.168.1.10 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 10 Jan 2000 19:11:38 -0400 To: freebsd-stable@FreeBSD.ORG From: "Marcelo J. Iturbe" Subject: System hanging.. kind of... Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am running FreeBSD 3.3, and I have set up 3 files in my=20 /usr/local/etc/rc.d system. They are apache.sh, mysql.sh, and postfix.sh When ever the system boots it seems to hang after the last .sh file. I have to type ^D to get the login prompt. I thought that this command would kill what ever process it last booted,=20 but that is not the case. I also thought that it might be an error within=20 the .sh files no matter what the last command is, it still hangs. Any thoughts? Thanks for your help, Marcelo *********************************************** ICQ 22921676 MSM Interactive. Dario Urzua 1940, Providencia, Chile. Phone: (56-2)204-3510=A0 Fax: (56-2) 204-3508 Email: marcelo@msm.cl=A0=A0=A0=A0http://www.msm.cl ******************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 14:21:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 5CC671537B for ; Mon, 10 Jan 2000 14:21:50 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 127nC7-00084S-00; Mon, 10 Jan 2000 14:21:48 -0800 Date: Mon, 10 Jan 2000 14:21:44 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Marcelo J. Iturbe" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: System hanging.. kind of... In-Reply-To: <4.2.0.58.20000110191137.00b8eb80@192.168.1.10> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Marcelo J. Iturbe wrote: > Hello, > I am running FreeBSD 3.3, and I have set up 3 files in my > /usr/local/etc/rc.d system. > They are apache.sh, mysql.sh, and postfix.sh > When ever the system boots it seems to hang after the last .sh file. > I have to type ^D to get the login prompt. > I thought that this command would kill what ever process it last booted, > but that is not the case. I also thought that it might be an error within > the .sh files no matter what the last command is, it still hangs. > > Any thoughts? First of all, this belongs on questions. Second, ^D is the end-of-file character. Something in your startup is prompting for input. By sending it the ^D, it seems to be continuing without input. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 18: 8:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.mi.home.com (ha1.rdc2.mi.home.com [24.2.68.68]) by hub.freebsd.org (Postfix) with ESMTP id 7E881152EC for ; Mon, 10 Jan 2000 18:08:14 -0800 (PST) (envelope-from dakott@home.com) Received: from cc939825-a.stcl1.mi.home.com ([24.7.250.15]) by mail.rdc2.mi.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <20000111020808.CTQH14123.mail.rdc2.mi.home.com@cc939825-a.stcl1.mi.home.com>; Mon, 10 Jan 2000 18:08:08 -0800 Date: Mon, 10 Jan 2000 21:08:06 -0500 (EST) From: David Kott To: "Marcelo J. Iturbe" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: System hanging.. kind of... In-Reply-To: <4.2.0.58.20000110191137.00b8eb80@192.168.1.10> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000, Marcelo J. Iturbe wrote: > Hello, > I am running FreeBSD 3.3, and I have set up 3 files in my > /usr/local/etc/rc.d system. > They are apache.sh, mysql.sh, and postfix.sh > When ever the system boots it seems to hang after the last .sh file. > I have to type ^D to get the login prompt. > I thought that this command would kill what ever process it last booted, > but that is not the case. I also thought that it might be an error within > the .sh files no matter what the last command is, it still hangs. > > Any thoughts? Is it hanging attempting to resolve an IP address perhaps? -d Curiosity may, or may not, have killed Schrodinger's cat. -townba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 18:15:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from void.dynip.com (hobax2-059.dialup.optusnet.com.au [198.142.241.59]) by hub.freebsd.org (Postfix) with ESMTP id 92AA715327 for ; Mon, 10 Jan 2000 18:15:21 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 031B755BA; Tue, 11 Jan 2000 13:15:10 +1100 (EST) Message-Id: <4.2.2.20000111130502.016b1450@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 11 Jan 2000 13:14:53 +1100 To: "Mr. K." From: james Subject: Re: process stuck in ttywri Cc: stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:59 8/1/2000 -0500, Mr. K. wrote: >This is the second time I've seen this on two completely different >machines (different network, different configuration, different state) so >I'm wondering if anyone else has run into it. What happens is while I'm >doing a make, one of the processes will get stuck. If I look at top, I >will see that one of the processes is stuck in ttywri. I know I have very >little information so I don't expect any solutions, but I was only >wondering if maybe someone else has run into this also, or maybe it was >already fixed? Also, if anyone wants to tell me something specific I >should look for next time it happens... > >FreeBSD [censored].home.com 3.4-STABLE FreeBSD 3.4-STABLE #1: Sun >Dec 19 04:22:13 GMT 1999 >root@[censored].home.com:/usr/src/sys/compile/HOMER i386 Hi, I'm going to add a "me too" to this. I've had the problem on both 3.4-STABLE, and 4.0-CURRENT. I haven't checked before what state anything was in (i will next time it happens). My FreeBSD machine doesn't even have a keyboard/monitor, so i don't know if it happens when i'm not telnetting to it. Basically, the make stops, and the telnet becomes unresponsive. I have to manually disconnect, and then reconnect, only to find a bunch of make's etc sitting in 'ps'. Sometimes they keep going (!?), sometimes they dont. Also, some telnet sessions mysteriously freeze (they like to freeze during cvsup). Wondering what's going on, i press a key, and then everything floods in and i realise that cvsup finished ages ago. I'm telnetting to my FreeBSD machine over my LAN, via 'vr0' @ 100Mbps FD. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 18:21:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 87F36154B1 for ; Mon, 10 Jan 2000 18:21:13 -0800 (PST) (envelope-from brameld@twave.net) Received: from [208.219.234.46] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id ja761237 for ; Mon, 10 Jan 2000 21:20:03 -0500 Message-ID: <387A93EA.C018B4EE@twave.net> Date: Mon, 10 Jan 2000 21:22:35 -0500 From: Walter Brameld X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: David Kott Cc: "Marcelo J. Iturbe" , freebsd-stable@FreeBSD.ORG Subject: Re: System hanging.. kind of... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kott wrote: > On Mon, 10 Jan 2000, Marcelo J. Iturbe wrote: > > > Hello, > > I am running FreeBSD 3.3, and I have set up 3 files in my > > /usr/local/etc/rc.d system. > > They are apache.sh, mysql.sh, and postfix.sh > > When ever the system boots it seems to hang after the last .sh file. > > I have to type ^D to get the login prompt. > > I thought that this command would kill what ever process it last booted, > > but that is not the case. I also thought that it might be an error within > > the .sh files no matter what the last command is, it still hangs. > > > > Any thoughts? > > Is it hanging attempting to resolve an IP address perhaps? > > -d > > Curiosity may, or may not, have killed Schrodinger's cat. > -townba > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I think that cat has probably starved to death by now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 20:10:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 61BF615402; Mon, 10 Jan 2000 20:10:13 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (robinson@bt-220-213.bta.net.cn [202.106.220.213]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id MAA02382; Tue, 11 Jan 2000 12:10:01 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.9.3) id MAA71581; Tue, 11 Jan 2000 12:10:39 +0800 (CST) (envelope-from robinson) Date: Tue, 11 Jan 2000 12:10:39 +0800 (CST) From: Michael Robinson Message-Id: <200001110410.MAA71581@netrinsics.com> To: obrien@freebsd.org Subject: Re: 4.4 BSD forever? Cc: freebsd-stable@freebsd.org In-Reply-To: <20000110091150.A94525@relay.nuxi.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: >It isn't a Mt. Xinu poster. It is a BSDI poster with the Daemon on it >and it did say "4.4 > 5.4". "5.4" refered to System V Rel. 4., which was >fairly new at the time. Oh. Nevermind. The one I'm looking for is the Mt. Xinu poster with the ratty BSD X-Wing Fighter blowing up the AT&T "Death Star" logo. I'm pretty sure that one said "4.2 > V". -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 20:36:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 93DF31540C for ; Mon, 10 Jan 2000 20:36:52 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id UAA98556; Mon, 10 Jan 2000 20:36:45 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id UAA44575; Mon, 10 Jan 2000 20:36:45 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 20:36:45 -0800 From: "David O'Brien" To: Coleman Kane Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110203645.D62163@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <20000109214046.7913BA54DB@netcom1.netcom.com> <20000110004054.A1181@evil.2y.net> <20000110094834.D94525@relay.nuxi.com> <20000110153703.A19250@evil.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000110153703.A19250@evil.2y.net>; from cokane@one.net on Mon, Jan 10, 2000 at 03:37:03PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, GCC 2.95.x can be patched for pentium, ppro, and k6 optimization > to make your programs run faster and more efficiently. If you could > compile the base system with it, you would glean more performance from > the box. If you go to http://www.goof.com/pcg/ you can see what I'm > talking about, Yes, but I have yet to have *anyone* post any numbers that show that using `pgcc' made their system "faster". I have heard from people that `pgcc' made this system less stable. `pgcc' is an experimental testing grounds for new IA-32 optimizations. This implies the code it produces may not be the most robust. Me, I'll only use a world and kernel built by a released version of GCC. > there is also a port in /usr/ports/lang/pgcc. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Like no kidding. Who do you think made that port and maintains it?? Geez. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 20:41:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6AD98153E7 for ; Mon, 10 Jan 2000 20:41:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id UAA98571 for ; Mon, 10 Jan 2000 20:41:47 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id UAA44653 for stable@freebsd.org; Mon, 10 Jan 2000 20:41:47 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 20:41:47 -0800 From: "David O'Brien" To: stable@freebsd.org Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110204146.E62163@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <20000110094834.D94525@relay.nuxi.com> <200001101803.NAA34213@misha.cisco.com> <20000110110936.A95288@relay.nuxi.com> <20000110154204.B19250@evil.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000110154204.B19250@evil.2y.net>; from cokane@one.net on Mon, Jan 10, 2000 at 03:42:04PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 03:42:04PM -0500, Coleman Kane wrote: > Follow the link, dude. ..snip.. > David O'Brien had the audacity to say: > > But your table doesn't say which compiler was used for what. > > Thus I can't tell what that table is telling me. My apologies. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 20:44:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-1-181.adsl.one.net [216.23.20.181]) by hub.freebsd.org (Postfix) with ESMTP id 46CB3153A2 for ; Mon, 10 Jan 2000 20:44:11 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id XAA13690; Mon, 10 Jan 2000 23:46:40 -0500 (EST) (envelope-from cokane) Date: Mon, 10 Jan 2000 23:46:40 -0500 From: Coleman Kane To: "David O'Brien" Cc: Coleman Kane , freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110234640.A98425@evil.2y.net> References: <20000109214046.7913BA54DB@netcom1.netcom.com> <20000110004054.A1181@evil.2y.net> <20000110094834.D94525@relay.nuxi.com> <20000110153703.A19250@evil.2y.net> <20000110203645.D62163@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000110203645.D62163@dragon.nuxi.com>; from obrien@NUXI.com on Mon, Jan 10, 2000 at 11:37:25PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien had the audacity to say: > Yes, but I have yet to have *anyone* post any numbers that show that > using `pgcc' made their system "faster". > Some other guy just put up a link to his page showing performance gain of about 25% using gcc-2.95 vs gcc-2.7. > I have heard from people that `pgcc' made this system less stable. > `pgcc' is an experimental testing grounds for new IA-32 optimizations. > This implies the code it produces may not be the most robust. Me, I'll > only use a world and kernel built by a released version of GCC. > The only thing I was pointing out was that the sources were not fully compatible with gcc-2.95. I understand that, and was simply following up to another post here. > > > there is also a port in /usr/ports/lang/pgcc. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Like no kidding. Who do you think made that port and maintains it?? > Geez. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 20:48:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B0CAE153B2 for ; Mon, 10 Jan 2000 20:48:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id UAA98686; Mon, 10 Jan 2000 20:48:41 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 20:48:41 -0800 From: "David O'Brien" To: Coleman Kane Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110204841.B98651@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000109214046.7913BA54DB@netcom1.netcom.com> <20000110004054.A1181@evil.2y.net> <20000110094834.D94525@relay.nuxi.com> <20000110153703.A19250@evil.2y.net> <20000110203645.D62163@dragon.nuxi.com> <20000110234640.A98425@evil.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <20000110234640.A98425@evil.2y.net> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 11:46:40PM -0500, Coleman Kane wrote: > > Yes, but I have yet to have *anyone* post any numbers that show that > > using `pgcc' made their system "faster". > > Some other guy just put up a link to his page showing performance gain > of about 25% using gcc-2.95 vs gcc-2.7. If you mean the gzip/bzip2 test, yes I will agree for some things it makes sense. HOWEVER, this topic started off as about building the FreeBSD world and kernel with a different compiler. > The only thing I was pointing out was that the sources were not fully > compatible with gcc-2.95. I understand that, and was simply following > up to another post here. Since the 4.0 sources are buildable with Gcc 2.95, it shouldn't take too much time for someone that cared to come up with a patchset to allow 3.4 to be compiled with Gcc 2.95. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 20:53:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C6CE414A10 for ; Mon, 10 Jan 2000 20:53:40 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id UAA98731; Mon, 10 Jan 2000 20:53:34 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 20:53:34 -0800 From: "David O'Brien" To: Mikhail Teterin Cc: stable@FreeBSD.ORG Subject: Re: isprint(3) and LANG/LOCALE Message-ID: <20000110205334.C98651@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001100505.AAA86278@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <200001100505.AAA86278@rtfm.newton> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is the subject supposed to consider the LANG setting? I'd think so, but I would email ache@freebsd.org as he is our internationalization guy. Possibly putting calls to setlocale() in main() will help. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 20:57:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 10FA0152CC for ; Mon, 10 Jan 2000 20:57:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id UAA98760 for freebsd-stable@FreeBSD.ORG; Mon, 10 Jan 2000 20:57:10 -0800 (PST) (envelope-from obrien) Date: Mon, 10 Jan 2000 20:57:10 -0800 From: "David O'Brien" To: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) Message-ID: <20000110205710.D98651@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 09:28:24AM -0800, Tom wrote: > > Actually, no. The distribution is called 4.4BSD, not BSD 4.4. The same > goes for 4.1 or 4.2 which were known as 4.1BSD and 4.2BSD respectively. > Anyone who understands what BSD is, will know the difference. And the triva question is why was there 1BSD, 2BSD, 3BSD, and then the switch to 4.0BSD - 4.4BSD. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 21: 4:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wcn4.wcnet.net (mail.wcnet.net [216.88.248.234]) by hub.freebsd.org (Postfix) with ESMTP id AF8CC14CB7; Mon, 10 Jan 2000 21:03:51 -0800 (PST) (envelope-from jestess@wcnet.net) Received: from wcnet.net [216.88.253.163] by wcn4.wcnet.net with ESMTP (SMTPD32-5.05) id A9B32D32027E; Mon, 10 Jan 2000 23:03:47 -0600 Message-ID: <387AB942.92C7C2E5@wcnet.net> Date: Mon, 10 Jan 2000 23:01:54 -0600 From: John Estess Organization: compulsive or none, depending on the day X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) References: <20000110205710.D98651@relay.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And the triva question is why was there 1BSD, 2BSD, 3BSD, and then the switch > to 4.0BSD - 4.4BSD. For an asymptotic approach to 5? The unreachable goal... Little did they know the next release was to be 4.4.1. -- _/ _/_/_/ || John Estess _/ _/ _/_/ || jestess@wcnet.net _/_/_/ _/_/_/ || To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 21: 7:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 25702153EE; Mon, 10 Jan 2000 21:07:34 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id AAA25161; Tue, 11 Jan 2000 00:07:30 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id AAA90968; Tue, 11 Jan 2000 00:07:30 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001110507.AAA90968@rtfm.newton> Subject: Re: isprint(3) and LANG/LOCALE In-Reply-To: <20000110205334.C98651@relay.nuxi.com> from "David O'Brien" at "Jan 10, 2000 08:53:34 pm" To: obrien@freebsd.org Date: Tue, 11 Jan 2000 00:07:30 -0500 (EST) Cc: ache@freebsd.org, stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"Is the subject supposed to consider the LANG setting? I'd think so, =>but => =I would email ache@freebsd.org as he is our internationalization guy. Is not he reading -stable? =Possibly putting calls to setlocale() in main() will help. Does not appear to change the result of this little program... -mi #include #include #include main(int argc, char *argv[]) { char *c; setlocale(LC_ALL, ""); for(c = argv[argc-1]; *c; *c++) printf("for %c isprint() returns %d\n", *c, isprint(*c)); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 21:20: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flophouse.com (flophouse.com [206.169.156.66]) by hub.freebsd.org (Postfix) with ESMTP id 9C8D8153A2 for ; Mon, 10 Jan 2000 21:19:59 -0800 (PST) (envelope-from dpassage@flophouse.com) Received: from flophouse.com (localhost [127.0.0.1]) by flophouse.com (8.9.3/8.9.3) with ESMTP id VAA11757 for ; Mon, 10 Jan 2000 21:20:13 -0800 (PST) (envelope-from dpassage@flophouse.com) Message-Id: <200001110520.VAA11757@flophouse.com> To: freebsd-stable@freebsd.org Subject: Re: Trouble loading installing on my Aptiva In-reply-to: Your message of "Sun, 09 Jan 2000 22:57:33 PST." Date: Mon, 10 Jan 2000 21:20:12 -0800 From: "David G. Paschich" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As a followup to my own message, I went to the BIOS and turned off all the power management and "fast booting" functionality and now my new machine is pleased as punch and cvsupping away. Thanks! > > Hi, > > > > On Sun, Jan 09, 2000 at 01:05:47PM -0800, David G. Paschich wrote: > > > So I just got me a shiny new IBM Aptiva with one of them wacky Athlon > > > processors in it, and FreeBSD 3.x won't load on it. > > ... hmm. I'm running a 'built-by-myself' Athlon machine (K7-700, > > Gigabyte-Mainboard, SymbiosLogic SCSI hostadaptor, fxp network) > > under -current and -stable without any problems. > > > > Really without any problems? No, .. of course not. > > I had to _really_carefully_ select the memory. > > > > Athlon-boards are more then picky about memory. > > Just adjust the BIOS-settings concerning the memory-timing to > > some conservative values and try again. > > If this doesn't help -> swap the memory. > > I'll try that, thanks. As an aside, the -current shapshot from Sunday > booted up just fine, but I'd rather be on the -stable branch than the > -current one for this machine's eventual use. > > Of course, I could always just wait a month for 4.0 to _become_ > -stable :) > > -------- > David G. Paschich > dpassage@flophouse.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 22: 6:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 4452A15418; Mon, 10 Jan 2000 22:06:10 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA92931; Tue, 11 Jan 2000 12:03:15 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 11 Jan 2000 12:03:14 +0600 (NS) From: Max Khon To: Mikhail Teterin Cc: obrien@FreeBSD.ORG, ache@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: isprint(3) and LANG/LOCALE In-Reply-To: <200001110507.AAA90968@rtfm.newton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 11 Jan 2000, Mikhail Teterin wrote: > =>Is the subject supposed to consider the LANG setting? I'd think so, > =>but > => > =I would email ache@freebsd.org as he is our internationalization guy. > > Is not he reading -stable? > > =Possibly putting calls to setlocale() in main() will help. > > Does not appear to change the result of this little program... > > -mi > > #include > #include > > #include > > main(int argc, char *argv[]) { > char *c; > setlocale(LC_ALL, ""); > for(c = argv[argc-1]; *c; *c++) > printf("for %c isprint() returns %d\n", *c, isprint(*c)); > } char is signed. you should use 'unsigned char *c' for isprint to work with chars > 127 this happens because _BSD_CT_RUNE_T_ is #define'ed as 'int' (is signed) in machine/ansi.h possibly this should be changed to int. ask ache about it. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 10 22: 8:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 20CD214E6B; Mon, 10 Jan 2000 22:07:56 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA93049; Tue, 11 Jan 2000 12:05:10 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 11 Jan 2000 12:05:10 +0600 (NS) From: Max Khon To: Mikhail Teterin Cc: obrien@FreeBSD.ORG, ache@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: isprint(3) and LANG/LOCALE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! [...] > possibly this should be changed to int. ask ache about it. grrr. i mean 'unsigned' /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 0:42:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id ADEE01521D; Tue, 11 Jan 2000 00:42:21 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA69288; Tue, 11 Jan 2000 09:42:14 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Brad Knowles Cc: Holtor , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Kernel Option: TCP_DROP_SYNFIN References: <20000109201829.20220.qmail@web116.yahoomail.com> From: Dag-Erling Smorgrav Date: 11 Jan 2000 09:42:13 +0100 In-Reply-To: Brad Knowles's message of "Sun, 9 Jan 2000 23:03:20 +0100" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles writes: > At 12:18 PM -0800 2000/1/9, Holtor wrote: > > Would this help stop SYN floods from breaking my > > freebsd computer? if anyones tried it, please speak > > up with any results or how it works. Thanks! > I've used it and haven't seen it do any harm to the systems I was > using it on, although I can't speak for how well it might have helped > them survive a SYN flood. Unless you're using TTCP (TCP for > Transactions), you should probably be safe in enabling it. It doesn't have anything to do with syn floods at all. It merely prevents OS fingerprinting (at least the way nmap does it). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 1:40:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id CC2B71543A; Tue, 11 Jan 2000 01:40:32 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 127xmm-000PVx-00; Tue, 11 Jan 2000 11:40:20 +0200 From: Sheldon Hearn To: Vivek Khera Cc: ports@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: question on necessity of tcp_wrappers port In-reply-to: Your message of "Mon, 10 Jan 2000 12:24:16 EST." <14458.5568.152019.715536@onceler.kcilink.com> Date: Tue, 11 Jan 2000 11:40:19 +0200 Message-ID: <98077.947583619@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jan 2000 12:24:16 EST, Vivek Khera wrote: > It seems to me that since 3.4 has tcp wrappers integrated into it > (inetd has support built in, and libwrap is there) that the > tcp_wrappers port is unnecessary. I think it may as well be left lying around in case it still works for RELENG_2_2 users. However, I do think that it should be marked broken for everything that has a /usr/include/tcpd.h . Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 2:35:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 4828615191; Tue, 11 Jan 2000 02:35:36 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id LAA75580; Tue, 11 Jan 2000 11:35:27 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Tue, 11 Jan 2000 11:35:27 +0100 (CET) From: Trond Endrestol To: FreeBSD stable , FreeBSD current Subject: Making sure /var/tmp/vi.recover exists during reboot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is something you might want to put in /etc/rc in both -stable and -current. Scenario: /tmp is MFS, /var/tmp, /usr/tmp and /usr/local/tmp are symlinks to /tmp, and hence /var/tmp/vi.recover does not exist at reboot and causes «cosmetic interference» on the console during reboot. Solution: Add these lines after the «# Recover vi editor files.» line (about line #345): if [ ! -d /var/tmp/vi.recover ]; then mkdir /var/tmp/vi.recover; chmod 1777 /var/tmp/vi.recover; chown root:wheel /var/tmp/vi.recover; fi ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.3 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 3: 2:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns1.kema.nl (dns1.kema.nl [194.53.253.50]) by hub.freebsd.org (Postfix) with ESMTP id 8A89C15366; Tue, 11 Jan 2000 03:02:16 -0800 (PST) (envelope-from jaap@114046.kema.nl) Received: (from root@localhost) by dns1.kema.nl (8.9.1a/8.6.12) id MAA04339; Tue, 11 Jan 2000 12:02:15 +0100 (MET) Received: by dns1.kema.nl via smap (V1.3) id sma004074; Tue, 11 Jan 00 12:01:48 +0100 Received: from 114046.kema.nl ([194.53.231.193]) by emma.kema.nl (8.7.5/8.6.12) with ESMTP id GAA23496; Tue, 11 Jan 2000 06:06:02 -0500 (EST) Received: from 114046.kema.nl (localhost [127.0.0.1]) by 114046.kema.nl (8.9.3/8.9.3) with ESMTP id MAA09106; Tue, 11 Jan 2000 12:07:24 +0100 (CET) (envelope-from jaap@114046.kema.nl) Message-Id: <200001111107.MAA09106@114046.kema.nl> To: obrien@FreeBSD.ORG Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) In-reply-to: Your message of Mon, 10 Jan 2000 20:57:10 -0800. <20000110205710.D98651@relay.nuxi.com> Date: Tue, 11 Jan 2000 12:07:24 +0100 From: Jaap Akkerhuis Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And the triva question is why was there 1BSD, 2BSD, 3BSD, and then the switch to 4.0BSD - 4.4BSD. As far as I remember, 1BSD was v6 stuff only BSD internal distributions (and good friends) with Pascal & ex; 2BSD was for v7 licences with csh (job control) and vi; 3BSD for v32 licences and virtual memory for the VAX and with 4BSD FFS was introduced, lisp and for DARPA later on networking stuff in 4.1c. Something like that. jaap To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 3:22:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 405F915343; Tue, 11 Jan 2000 03:22:45 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 127zNa-0002Lo-00; Tue, 11 Jan 2000 13:22:26 +0200 From: Sheldon Hearn To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Tue, 11 Jan 2000 11:35:27 +0100." Date: Tue, 11 Jan 2000 13:22:26 +0200 Message-ID: <9039.947589746@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000 11:35:27 +0100, Trond Endrestol wrote: > This is something you might want to put in /etc/rc in both -stable > and -current. > > Scenario: > > /tmp is MFS, > /var/tmp, /usr/tmp and /usr/local/tmp are symlinks to /tmp, Not until someone can explain how making /var/tmp a symlink to /tmp is sensible, given that /var/tmp is documented as containing "temporary files that are kept between system reboots" (see hier(7)). So basically, no. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 3:40:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 2067415467; Tue, 11 Jan 2000 03:40:45 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id MAA81050; Tue, 11 Jan 2000 12:40:33 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Tue, 11 Jan 2000 12:40:33 +0100 (CET) From: Trond Endrestol To: Jaap Akkerhuis Cc: obrien@FreeBSD.ORG, "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) In-Reply-To: <200001111107.MAA09106@114046.kema.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Jaap Akkerhuis wrote: > > And the triva question is why was there 1BSD, 2BSD, 3BSD, and > then the switch to 4.0BSD - 4.4BSD. > > > As far as I remember, 1BSD was v6 stuff only BSD internal distributions > (and good friends) with Pascal & ex; 2BSD was for v7 licences with > csh (job control) and vi; 3BSD for v32 licences and virtual memory > for the VAX and with 4BSD FFS was introduced, lisp and for DARPA > later on networking stuff in 4.1c. Something like that. According to Kirk McKusick's chapter in «Open Sources: Voices from the Open Source Revolution» 4.1BSD was originally planned to be released as 5BSD, but there were objections from AT&T. AT&T said that the customers would be confused if both SysV and 5BSD were available. (Huh?) Berkeley agreed to keep the major number at 4 and only increase the minor number. That's why Berkeley released subsequent releases as 4.1, 4.2, 4.3 and 4.4BSD. See http://www.oreilly.com/catalog/opensources/book/kirkmck.html for more information. ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.3 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 3:55: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from abc.123.org (123.org [195.244.241.123]) by hub.freebsd.org (Postfix) with ESMTP id 37B6D1547A; Tue, 11 Jan 2000 03:54:51 -0800 (PST) (envelope-from k@abc.123.org) Received: (from k@localhost) by abc.123.org (8.9.3/8.9.3) id MAA37141; Tue, 11 Jan 2000 12:54:14 +0100 (CET) (envelope-from k) Date: Tue, 11 Jan 2000 12:54:14 +0100 From: Kai Voigt To: Trond Endrestol Cc: Jaap Akkerhuis , obrien@FreeBSD.ORG, "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) Message-ID: <20000111125414.Y27079@abc.123.org> References: <200001111107.MAA09106@114046.kema.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: 123.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trond Endrestol wrote: > On Tue, 11 Jan 2000, Jaap Akkerhuis wrote: > > According to Kirk McKusick's chapter in «Open Sources: Voices from the > Open Source Revolution» 4.1BSD was originally planned to be released > as 5BSD, but there were objections from AT&T. AT&T said that the > customers would be confused if both SysV and 5BSD were available. > (Huh?) Berkeley agreed to keep the major number at 4 and only increase > the minor number. That's why Berkeley released subsequent releases as > 4.1, 4.2, 4.3 and 4.4BSD. Oh, then it should be FreeBSD 6.0, so we won't conflict with SysV :-) Or we switch to letters instead of numbers, or name it after the current president of some carribean country? SCNR, Kai -- kai voigt hamburger chaussee 36 24113 kiel 04 31 - 22 19 98 69 http://k.123.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 4: 5: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 23E4C14D9F for ; Tue, 11 Jan 2000 04:05:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id EAA11134; Tue, 11 Jan 2000 04:05:01 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id EAA46293; Tue, 11 Jan 2000 04:05:01 -0800 (PST) (envelope-from obrien) Date: Tue, 11 Jan 2000 04:05:00 -0800 From: "David O'Brien" To: Trond Endrestol Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) Message-ID: <20000111040500.A46259@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001111107.MAA09106@114046.kema.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: ; from trond@ramstind.gtf.ol.no on Tue, Jan 11, 2000 at 12:40:33PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 12:40:33PM +0100, Trond Endrestol wrote: > According to Kirk McKusick's chapter in «Open Sources: Voices from the > Open Source Revolution» 4.1BSD was originally planned to be released > as 5BSD, but there were objections from AT&T. AT&T said that the > customers would be confused if both SysV and 5BSD were available. > (Huh?) Berkeley agreed to keep the major number at 4 and only increase > the minor number. That's why Berkeley released subsequent releases as > 4.1, 4.2, 4.3 and 4.4BSD. Correct answer! Now that we've had our education contribution from this topic, it is time to let the discussion of the next major release of FreeBSD DIE! -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 4:37:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bender.cl.msu.edu (bender.cl.msu.edu [35.8.1.212]) by hub.freebsd.org (Postfix) with ESMTP id 57D9215448 for ; Tue, 11 Jan 2000 04:37:45 -0800 (PST) (envelope-from muk@bender.cl.msu.edu) Received: (from muk@localhost) by bender.cl.msu.edu (8.9.3/8.9.3) id HAA89627 for freebsd-stable@FreeBSD.ORG; Tue, 11 Jan 2000 07:39:49 -0500 (EST) (envelope-from muk) Date: Tue, 11 Jan 2000 07:39:49 -0500 From: "Matthew A. Kolb" To: freebsd-stable@FreeBSD.ORG Subject: Re: System hanging.. kind of... Message-ID: <20000111073949.A89610@bender.cl.msu.edu> References: <4.2.0.58.20000110191137.00b8eb80@192.168.1.10> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <4.2.0.58.20000110191137.00b8eb80@192.168.1.10>; from marcelo@msm.cl on Mon, Jan 10, 2000 at 07:11:38PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 10, 2000 at 07:11:38PM -0400, Marcelo J. Iturbe wrote: > Hello, > I am running FreeBSD 3.3, and I have set up 3 files in my > /usr/local/etc/rc.d system. > They are apache.sh, mysql.sh, and postfix.sh ---->If you're running apache-modssl (i noted the apache.sh), it may be that the script is requesting a pem-passphrase. ---->(if you entered a non-null passphrase when prompted for one at the compile-install phase this will be the case.) > I have to type ^D to get the login prompt. ---->Giving end of input to apache.sh (^C would kill it) > I thought that this command would kill what ever process it last booted, ---->Nope (again...end of input) > but that is not the case. I also thought that it might be an error within > the .sh files no matter what the last command is, it still hangs. ---->Not an error...its a feature :) > Thanks for your help, > Marcelo > ./kolb -- Matthew A(U). Kolb Michigan State University SCNC 110 Computer Center (517)355-4500 x 124 kolb@bender.cl.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 5:59: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from router.difi.de (router.difi.de [212.6.96.2]) by hub.freebsd.org (Postfix) with ESMTP id CB4EA15583 for ; Tue, 11 Jan 2000 05:59:05 -0800 (PST) (envelope-from uwe.laverenz@difi.de) Received: from max.difi.de (max.difi.de [192.168.1.2]) by router.difi.de (8.9.3/8.9.3) with ESMTP id OAA49611 for ; Tue, 11 Jan 2000 14:59:04 +0100 (CET) (envelope-from uwe.laverenz@difi.de) Received: from difi.de (edv1.difi.de [192.168.1.54]) by max.difi.de (8.9.3/8.9.3) with ESMTP id OAA21817 for ; Tue, 11 Jan 2000 14:59:03 +0100 (CET) (envelope-from uwe.laverenz@difi.de) Message-ID: <387B3727.4F692BCE@difi.de> Date: Tue, 11 Jan 2000 14:59:03 +0100 From: Uwe Laverenz Organization: DIFI Dierk Filmer GmbH X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: 3.x to current not possible? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a complete CVS tree of the BSD sources on my machine and would like to install -current on a spare 3.x machine for testing purposes. But it seems that upgrading a 3.x machine via source is not possible at this time? I wasn't able to build a snap on my 3.4 machine either. So, before I start downloading/installing via ftp: is there a workaround for this situation? Thank you, Uwe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 6: 4:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id B60221547D; Tue, 11 Jan 2000 06:04:09 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id JAA28007; Tue, 11 Jan 2000 09:04:07 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id JAA92453; Tue, 11 Jan 2000 09:04:07 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001111404.JAA92453@rtfm.newton> Subject: Re: isprint(3) and LANG/LOCALE In-Reply-To: from Max Khon at "Jan 11, 2000 12:05:10 pm" To: Max Khon Date: Tue, 11 Jan 2000 09:04:07 -0500 (EST) Cc: Mikhail Teterin , obrien@FreeBSD.ORG, ache@FreeBSD.ORG, stable@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Tue, 11 Jan 2000 06:22:31 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1282Bg-0001nl-00; Tue, 11 Jan 2000 16:22:20 +0200 From: Sheldon Hearn To: Uwe Laverenz Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.x to current not possible? In-reply-to: Your message of "Tue, 11 Jan 2000 14:59:03 +0100." <387B3727.4F692BCE@difi.de> Date: Tue, 11 Jan 2000 16:22:20 +0200 Message-ID: <6928.947600540@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000 14:59:03 +0100, Uwe Laverenz wrote: > I have a complete CVS tree of the BSD sources on my machine and would > like to install -current on a spare 3.x machine for testing purposes. > But it seems that upgrading a 3.x machine via source is not possible at > this time? I wasn't able to build a snap on my 3.4 machine either. We're on the threshold of being able to upgrade 3.x machines to CURRENT properly, although the CURRENT ``world'' has been broken a lot in the last few days. I must admit, I thought we'd already got to the stage where you could fairly easily upgrade from legacy systems. How long ago did you try with CURRENT sources? If more than a day ago, you might very well want to try again? Perhaps you'd like to post the actual error messages you get when you try to upgrade to CURRENT? If so, please post them to the freebsd-current mailing list. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 6:47:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [199.103.137.198]) by hub.freebsd.org (Postfix) with ESMTP id 1DEE51501C; Tue, 11 Jan 2000 06:47:47 -0800 (PST) (envelope-from loverso@infolibria.com) Received: from infolibria.com (border [199.103.137.193]) by mail.infolibria.com (Postfix) with ESMTP id 206B9DDB82; Tue, 11 Jan 2000 09:49:54 -0500 (EST) Message-ID: <387B42CA.D67EBD06@infolibria.com> Date: Tue, 11 Jan 2000 09:48:42 -0500 From: John LoVerso X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) References: <20000110205710.D98651@relay.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And the triva question is why was there 1BSD, 2BSD, 3BSD, and then the switch > to 4.0BSD - 4.4BSD. While Jaap and Trond gave a historically correct answer, I consider this sequence among the many cases of what I call "conservation of version numbers", a principal that gets applied as a project gets more notice or usage. Basically, leading major version numbers become fixed for fear of alienating the user population. Instead, additional trailing version information is appended, leading to messy versioning and (sometimes) confusion about the "latest version". In most cases, this principal gets applied as marketing organizations get involved in the naming of releases. Consider "4.4BSD-Lite Release 2", "System Vr4.2", "X11R6.4", "OSF/1 1.3", "NT 4.0.1381 SP6", "HTTP/1.1", "JDK 1.2.2", etc. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 6:49: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from router.difi.de (router.difi.de [212.6.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 6B91B154DA for ; Tue, 11 Jan 2000 06:48:04 -0800 (PST) (envelope-from uwe.laverenz@difi.de) Received: from max.difi.de (max.difi.de [192.168.1.2]) by router.difi.de (8.9.3/8.9.3) with ESMTP id PAA49759; Tue, 11 Jan 2000 15:48:02 +0100 (CET) (envelope-from uwe.laverenz@difi.de) Received: from difi.de (edv1.difi.de [192.168.1.54]) by max.difi.de (8.9.3/8.9.3) with ESMTP id PAA25386; Tue, 11 Jan 2000 15:48:02 +0100 (CET) (envelope-from uwe.laverenz@difi.de) Message-ID: <387B42A0.307180D@difi.de> Date: Tue, 11 Jan 2000 15:48:02 +0100 From: Uwe Laverenz Organization: DIFI Dierk Filmer GmbH X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.x to current not possible? References: <6928.947600540@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Sheldon, > I must admit, I thought we'd already got to the stage where you could > fairly easily upgrade from legacy systems. How long ago did you try > with CURRENT sources? If more than a day ago, you might very well want > to try again? My last attempt was yesterday morning, and to my surprise "make buildworld" worked without any problems. This shows that things have improved very much, since this wouldn't have been possible a few weeks ago. After the buildworld I switched to single user mode and tried to run "make installworld" which crashed with signal 12 in /bin/sh. The machine was running 3.3-STABLE (december 6th). > Perhaps you'd like to post the actual error messages you get when > you try to upgrade to CURRENT? If so, please post them to the > freebsd-current mailing list. Ok, I'll start a new attempt this evening. Thanks, Uwe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 7:14:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id C3DDA15493 for ; Tue, 11 Jan 2000 07:14:19 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id QAA38786; Tue, 11 Jan 2000 16:14:16 +0100 (CET) (envelope-from olli) Date: Tue, 11 Jan 2000 16:14:16 +0100 (CET) Message-Id: <200001111514.QAA38786@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: load spike strangeness X-Newsgroups: list.freebsd-stable In-Reply-To: <858qfm$17gj$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It happened again, and I noticed it in time to record a few stats... But I fear that this is not enough to actually debug the problem. What else could I do if this happenes again? In this particular case, the load dropped back to 0.0 after a few minutes, for no apparent reason. BTW, this is some 3-stable (not the newest, but I watched the same behaviour on all kinds of different versions). Script started on Tue Jan 11 16:02:40 2000 lysithea# top -S -b 999999 last pid: 665; load averages: 1.07, 1.03, 0.98 up 0+11:03:46 16:02:46 38 processes: 1 running, 37 sleeping Mem: 29M Active, 6368K Inact, 8152K Wired, 2064K Cache, 3861K Buf, 16M Free Swap: 128M Total, 128M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 569 root 2 0 21856K 20180K select 0:52 0.00% 0.00% XF86_SVGA 195 root 2 0 784K 472K select 0:05 0.00% 0.00% moused 222 ekg 10 0 764K 468K nanslp 0:05 0.00% 0.00% heartbeat 640 netscape 2 0 15192K 12700K select 0:03 0.00% 0.00% navigator-4.08 602 root 2 0 2036K 1368K select 0:02 0.00% 0.00% bigredknob 93 root 2 -12 1040K 668K select 0:02 0.00% 0.00% xntpd 232 root 10 0 764K 464K nanslp 0:01 0.00% 0.00% idlewatch 255 root 2 0 1184K 704K select 0:01 0.00% 0.00% sshd1 596 netscape 2 0 1684K 1176K select 0:01 0.00% 0.00% fvwm 4 root 18 0 0K 0K syncer 0:00 0.00% 0.00% syncer 115 daemon 2 0 784K 480K sbwait 0:00 0.00% 0.00% rwhod 17 root 10 0 32532K 2268K mfsidl 0:00 0.00% 0.00% mount_mfs 645 root 2 0 1228K 780K select 0:00 0.00% 0.00% sshd1 85 root 2 0 812K 468K select 0:00 0.00% 0.00% syslogd 262 root 10 0 504K 188K wait 0:00 0.00% 0.00% sh 650 root 18 0 1180K 848K pause 0:00 0.00% 0.00% zsh 2 root -18 0 0K 0K psleep 0:00 0.00% 0.00% pagedaemon 264 root 10 0 504K 168K wait 0:00 0.00% 0.00% sh 641 netscape 2 0 10048K 7492K select 0:00 0.00% 0.00% navigator-4.08 647 root 18 0 456K 284K pause 0:00 0.00% 0.00% csh 665 root 28 0 1500K 756K RUN 0:00 0.00% 0.00% top 109 root 10 0 208K 32K nfsidl 0:00 0.00% 0.00% nfsiod 599 netscape 2 0 792K 484K select 0:00 0.00% 0.00% FvwmClean 263 root 10 0 496K 164K wait 0:00 0.00% 0.00% sh 639 netscape 18 0 448K 272K pause 0:00 0.00% 0.00% csh 568 root 10 0 1860K 1012K wait 0:00 0.00% 0.00% xinit 583 netscape 18 0 448K 240K pause 0:00 0.00% 0.00% csh 0 root -18 0 0K 0K sched 0:00 0.00% 0.00% swapper 663 root 18 0 452K 280K pause 0:00 0.00% 0.00% csh 662 root 2 0 808K 584K select 0:00 0.00% 0.00% script 584 netscape 10 0 504K 168K wait 0:00 0.00% 0.00% sh 1 root 10 0 484K 168K wait 0:00 0.00% 0.00% init 110 root 10 0 208K 32K nfsidl 0:00 0.00% 0.00% nfsiod 229 root 10 0 492K 188K wait 0:00 0.00% 0.00% sh 32 root 18 0 204K 60K pause 0:00 0.00% 0.00% adjkerntz 111 root 10 0 208K 32K nfsidl 0:00 0.00% 0.00% nfsiod 112 root 10 0 208K 32K nfsidl 0:00 0.00% 0.00% nfsiod 3 root 18 0 0K 0K psleep 0:00 0.00% 0.00% vmdaemon lysithea# vmstat 5 procs memory page disk faults cpu r b w avm fre flt re pi po fr sr fd0 in sy cs us sy id 1 0 0 6592 18860 3 0 0 0 3 0 0 235 184 21 0 0 99 0 0 0 6916 18860 1 0 0 0 0 0 0 231 30 12 0 0 100 0 0 0 6916 18860 1 0 0 0 0 0 0 231 29 13 0 0 100 0 0 0 5904 18860 1 0 0 0 0 0 0 231 29 13 0 0 100 ^C lysithea# ps -auxww USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 667 0.0 0.4 404 240 p1 R+ 4:03PM 0:00.00 ps -auxww root 1 0.0 0.3 484 168 ?? Is 5:59AM 0:00.01 /sbin/init -- root 2 0.0 0.0 0 0 ?? DL 5:59AM 0:00.06 (pagedaemon) root 3 0.0 0.0 0 0 ?? DL 5:59AM 0:00.00 (vmdaemon) root 4 0.0 0.0 0 0 ?? DL 5:59AM 0:00.30 (syncer) root 17 0.0 3.6 32532 2268 ?? SLs 5:59AM 0:00.20 mfs -o nosuid -s 64000 -m 0 -T minimum /dev/zero /tmp (mount_mfs) root 32 0.0 0.1 204 60 ?? Is 5:59AM 0:00.00 adjkerntz -i root 85 0.0 0.8 812 468 ?? Is 4:59AM 0:00.12 syslogd -s root 93 0.0 1.1 1040 668 ?? S; Tue, 11 Jan 2000 07:25:19 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id KAA26821; Tue, 11 Jan 2000 10:25:12 -0500 (EST) Date: Tue, 11 Jan 2000 10:25:12 -0500 (EST) From: "Mr. K." To: james Cc: freebsd-stable@freebsd.org Subject: Re: Telnet freezes with wait chan of 'ttywri'/'ttywai' In-Reply-To: <4.2.2.20000111213124.00a2c3d0@mail.southcom.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, james wrote: > > Hi, > > I've just had another freeze on a telnet session from my Windows machine to > my FreeBSD 4.0-CURRENT machine with a wait chan of 'ttywri'. I decided to I've run into this also, several times. > Any ideas what could be wrong? I can send any other output or config if you > like.. I just don't want to include some massive email if the problem is > really trivial or whatever.. > Here's an off the wall question which might explain why not everyone is running into this. Are you using windows 2000? I think I started running into this problem about the same time I "upgraded" to windows 2000. > Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 7:27:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.vitts.com (mail.vitts.com [216.64.31.74]) by hub.freebsd.org (Postfix) with ESMTP id 1DB1A14E6B for ; Tue, 11 Jan 2000 07:27:49 -0800 (PST) (envelope-from michaelremski@ellacoya.com) Received: from ellacoya.com ([216.64.109.139]) by mail.vitts.com (InterMail v4.01.00 201-232-112) with ESMTP id <20000111152927.GKEF1342.mail.vitts.com@ellacoya.com>; Tue, 11 Jan 2000 10:29:27 -0500 Message-ID: <387B4C75.3DC13240@ellacoya.com> Date: Tue, 11 Jan 2000 10:29:57 -0500 From: Michael Remski X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Uwe Laverenz Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.x to current not possible? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There was a thread a while ago about needing to build a -current kernel with the 3.x tools, rebooting and then doing a build/installworld. I don't know if this is still true (content to stay with -stable), but if one did not do this, the usual error was a "Sig 12". m -- "To keep in silence our designs, my friends would think I was a nut" Peter Gabriel, Solsbury Hill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 7:29:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ktts.kharkov.ua (ktts.kharkov.ua [193.124.57.65]) by hub.freebsd.org (Postfix) with ESMTP id D3AA114D64 for ; Tue, 11 Jan 2000 07:29:25 -0800 (PST) (envelope-from tosh@assa.vl.net.ua) Received: from assa.vl.net.ua (assa.vl.net.ua [193.124.76.15]) by ktts.kharkov.ua (8.9.3/8.9.3) with ESMTP id RAA01997 for ; Tue, 11 Jan 2000 17:24:06 +0200 (EET) Received: from assa ([192.168.1.1]) by assa.vl.net.ua with esmtp (Exim 2.053 #1) id 12839E-0007PY-00 for freebsd-stable@freebsd.org; Tue, 11 Jan 2000 17:23:52 +0200 Date: Tue, 11 Jan 2000 17:23:51 +0200 (EET) From: Anton X-Sender: tosh@assa To: freebsd-stable@freebsd.org Subject: fbsdboot.exe can't load elf kernels Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello. is there way to boot fbsd3.x from dos? all ok with 2.2.8, but in 3.x fbsdboot.exe say 'Invalid format'. also i see that fbsdboot.exe is not changed since 2.xx it can't support elf format at all? best *. anton. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 7:53:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from doe.ellink.ru (doe.ellink.ru [195.190.108.2]) by hub.freebsd.org (Postfix) with ESMTP id ECFA714F64 for ; Tue, 11 Jan 2000 07:51:01 -0800 (PST) (envelope-from cdshop@ellink.ru) Received: from ellink.ru (dialup-36.ellink.ru [195.190.108.164]) by doe.ellink.ru (8.9.3/892/Nevalink/990119) with ESMTP id SAA24147 for ; Tue, 11 Jan 2000 18:46:56 +0300 (MSK) Message-ID: <387B5069.4C029A1B@ellink.ru> Date: Tue, 11 Jan 2000 18:46:49 +0300 From: Andrew Prudkov X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: FreeBSD-stable@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 8:11:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 6AD0614A2B for ; Tue, 11 Jan 2000 08:11:10 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id RAA43373; Tue, 11 Jan 2000 17:11:03 +0100 (CET) (envelope-from olli) Date: Tue, 11 Jan 2000 17:11:03 +0100 (CET) Message-Id: <200001111611.RAA43373@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels X-Newsgroups: list.freebsd-stable In-Reply-To: <85fibl$2bkh$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anton wrote in list.freebsd-stable: > is there way to boot fbsd3.x from dos? all ok with 2.2.8, > but in 3.x fbsdboot.exe say 'Invalid format'. > also i see that fbsdboot.exe is not changed since 2.xx > it can't support elf format at all? Correct, fbsdboot.exe does not support ELF kernels, and it's considered obsolete. (It didn't work for me anymore even before the switch to ELF, so there must be even more brokenness in there.) Just don't boot FreeBSD from DOS. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 8:19:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 430C214C2E for ; Tue, 11 Jan 2000 08:19:56 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id QAA06632; Tue, 11 Jan 2000 16:20:09 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001111611.RAA43373@dorifer.heim3.tu-clausthal.de> Date: Tue, 11 Jan 2000 16:20:09 -0000 (GMT) From: "Steve O'Hara-Smith" To: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-00 Oliver Fromme wrote: > Just don't boot FreeBSD from DOS. Indeed a search on the mailing lists about this issue will reveal a large number of gotchas related to VM86, bios vectors and such like that make this a very bad idea. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 8:25:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cichlids.com (as15-092.rp-plus.de [149.221.237.92]) by hub.freebsd.org (Postfix) with ESMTP id 5F308154D2 for ; Tue, 11 Jan 2000 08:25:19 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id F37A1AB93; Tue, 11 Jan 2000 17:23:26 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id RAA08412; Tue, 11 Jan 2000 17:23:10 +0100 (CET) (envelope-from alex) Date: Tue, 11 Jan 2000 17:23:10 +0100 From: Alexander Langer To: Sheldon Hearn Cc: Uwe Laverenz , freebsd-stable@FreeBSD.ORG Subject: Re: 3.x to current not possible? Message-ID: <20000111172310.B8348@cichlids.cichlids.com> Mail-Followup-To: Sheldon Hearn , Uwe Laverenz , freebsd-stable@FreeBSD.ORG References: <387B3727.4F692BCE@difi.de> <6928.947600540@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6928.947600540@axl.noc.iafrica.com>; from sheldonh@uunet.co.za on Tue, Jan 11, 2000 at 04:22:20PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Sheldon Hearn (sheldonh@uunet.co.za): > Perhaps you'd like to post the actual error messages you get when > you try to upgrade to CURRENT? If so, please post them to the > freebsd-current mailing list. Also, he should read /usr/src/UPGRADING Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 8:43:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 2962415528 for ; Tue, 11 Jan 2000 08:43:42 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id LAA39737; Tue, 11 Jan 2000 11:43:07 -0500 (EST) (envelope-from mi) Message-Id: <200001111643.LAA39737@misha.cisco.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: from "Steve O'Hara-Smith" at "Jan 11, 2000 04:20:09 pm" To: "Steve O'Hara-Smith" Date: Tue, 11 Jan 2000 11:43:07 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve O'Hara-Smith once wrote: > On 11-Jan-00 Oliver Fromme wrote: > > Just don't boot FreeBSD from DOS. > > Indeed a search on the mailing lists about this issue will > reveal a large number of gotchas related to VM86, bios vectors and > such like that make this a very bad idea. Can one still TRY boot boot/loader instead of kernel? -mi (blessed to not even have the DOS installed to test) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 8:49:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id E0800153AD; Tue, 11 Jan 2000 08:49:11 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA30064; Tue, 11 Jan 2000 08:49:10 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda30062; Tue Jan 11 08:49:10 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id IAA31925; Tue, 11 Jan 2000 08:49:10 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdj31917; Tue Jan 11 08:48:27 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id IAA52758; Tue, 11 Jan 2000 08:48:26 -0800 (PST) Message-Id: <200001111648.IAA52758@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdr52753; Tue Jan 11 08:48:08 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: obrien@FreeBSD.ORG Cc: "freebsd-stable@FreeBSD. ORG" Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) In-reply-to: Your message of "Mon, 10 Jan 2000 20:57:10 PST." <20000110205710.D98651@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 08:48:08 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000110205710.D98651@relay.nuxi.com>, "David O'Brien" writes: > On Mon, Jan 10, 2000 at 09:28:24AM -0800, Tom wrote: > > > > Actually, no. The distribution is called 4.4BSD, not BSD 4.4. The same > > goes for 4.1 or 4.2 which were known as 4.1BSD and 4.2BSD respectively. > > Anyone who understands what BSD is, will know the difference. > > And the triva question is why was there 1BSD, 2BSD, 3BSD, and then the switch > to 4.0BSD - 4.4BSD. UCB and AT&T had agreed that there were to be no new releases of BSD and that 4BSD was the final release. 4.1BSD - 4.4BSD were named such because they were "officially" only modifications to 4BSD and as such were not full releases. In fact they contained more new features than previous releases and were modifications to 4BSD in name only. It's all in Kirk's book the Design and Implementation of 4.4BSD. It's interesting to note that this is what happens when lawyers and marketing people get involved with release numbering. Note SunOS 4.1.4, Solaris 2.x, Solaris 7, 8 as another good example. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 8:49:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 4170B15528 for ; Tue, 11 Jan 2000 08:49:56 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id QAA06653; Tue, 11 Jan 2000 16:49:33 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001111643.LAA39737@misha.cisco.com> Date: Tue, 11 Jan 2000 16:49:33 -0000 (GMT) From: "Steve O'Hara-Smith" To: Mikhail Teterin Subject: Re: fbsdboot.exe can't load elf kernels Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-00 Mikhail Teterin wrote: > Steve O'Hara-Smith once wrote: > Can one still TRY boot boot/loader instead of kernel? One can always try, but the guts of the problem are that the vectors may have been rewritten by DOS and there is no way to recover the originals. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 9:24:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from void.dynip.com (hobax2-059.dialup.optusnet.com.au [198.142.241.59]) by hub.freebsd.org (Postfix) with ESMTP id 75961154C1 for ; Tue, 11 Jan 2000 09:24:39 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 8870D55BA; Wed, 12 Jan 2000 04:24:31 +1100 (EST) Message-Id: <4.2.2.20000112040306.00de6ab0@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 12 Jan 2000 04:13:57 +1100 To: "Mr. K." From: james Subject: Re: Telnet freezes with wait chan of 'ttywri'/'ttywai' Cc: freebsd-stable@freebsd.org In-Reply-To: References: <4.2.2.20000111213124.00a2c3d0@mail.southcom.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:25 11/1/2000 -0500, Mr. K. wrote: > > Any ideas what could be wrong? I can send any other output or config if > you > > like.. I just don't want to include some massive email if the problem is > > really trivial or whatever.. > > >Here's an off the wall question which might explain why not everyone is >running into this. Are you using windows 2000? I think I started running >into this problem about the same time I "upgraded" to windows 2000. Nope. Still on 98se. Hmm.. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 11:42:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shell13.ba.best.com (shell13.ba.best.com [206.184.139.144]) by hub.freebsd.org (Postfix) with ESMTP id D06FE15070 for ; Tue, 11 Jan 2000 11:42:36 -0800 (PST) (envelope-from rone@ennui.org) Received: (from rone@localhost) by shell13.ba.best.com (8.9.3/8.9.2/best.sh) id LAA00337 for freebsd-stable@FreeBSD.ORG; Tue, 11 Jan 2000 11:42:31 -0800 (PST) From: remorse code Message-Id: <200001111942.LAA00337@shell13.ba.best.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001111611.RAA43373@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Jan 11, 0 05:11:03 pm" To: freebsd-stable@FreeBSD.ORG Date: Tue, 11 Jan 2000 11:42:31 -0800 (PST) X-URL: http://ennui.org/rone/ X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme writes: Just don't boot FreeBSD from DOS. If that's the case, has fbsdboot.exe been removed from the 3.4 CD? rone -- Insultant: n. Contract worker who gets paid an obscene hourly wage to insult full-time company employees. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 11:51:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 8973B154D4; Tue, 11 Jan 2000 11:51:43 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id LAA30658; Tue, 11 Jan 2000 11:47:55 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda30656; Tue Jan 11 11:47:43 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id LAA38198; Tue, 11 Jan 2000 11:47:42 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdc38196; Tue Jan 11 11:47:36 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id LAA55191; Tue, 11 Jan 2000 11:47:35 -0800 (PST) Message-Id: <200001111947.LAA55191@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdL55184; Tue Jan 11 11:46:44 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Dag-Erling Smorgrav Cc: Brad Knowles , Holtor , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Kernel Option: TCP_DROP_SYNFIN In-reply-to: Your message of "11 Jan 2000 09:42:13 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 11:46:43 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: > Brad Knowles writes: > > At 12:18 PM -0800 2000/1/9, Holtor wrote: > > > Would this help stop SYN floods from breaking my > > > freebsd computer? if anyones tried it, please speak > > > up with any results or how it works. Thanks! > > I've used it and haven't seen it do any harm to the systems I was > > using it on, although I can't speak for how well it might have helped > > them survive a SYN flood. Unless you're using TTCP (TCP for > > Transactions), you should probably be safe in enabling it. > > It doesn't have anything to do with syn floods at all. It merely > prevents OS fingerprinting (at least the way nmap does it). The following ipfw rule will also prevent OS fingerprinting. deny log tcp from any to any in tcpflg fin,syn Would this too have problems with TTCP? The reason I ask is that I've been using this rule for a ever since 2.2.x (cannot remember the exact date) and I haven't had any problems with TTCP enabled. I know I should look at the RFC (and I will after lunch), but I'll ask anyway. Does TTCP use packets with SYN/FIN set? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 12:44:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id E692F15019; Tue, 11 Jan 2000 12:44:45 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA22500; Tue, 11 Jan 2000 21:44:15 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001111947.LAA55191@cwsys.cwsent.com> References: <200001111947.LAA55191@cwsys.cwsent.com> Date: Tue, 11 Jan 2000 21:41:43 +0100 To: Cy Schubert - ITSD Open Systems Group , Dag-Erling Smorgrav From: Brad Knowles Subject: Re: Kernel Option: TCP_DROP_SYNFIN Cc: Holtor , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:46 AM -0800 2000/1/11, Cy Schubert - ITSD Open Systems Group wrote: > The following ipfw rule will also prevent OS fingerprinting. > > deny log tcp from any to any in tcpflg fin,syn > > Would this too have problems with TTCP? Yup. I haven't read the RFC, but I've read the first bit of _TCP/IP Illustrated, Volume 3: TCP for Transactions, HTTP, NNTP, and the UNIX(r) Domain Protocols_ by Stevens, and by definition TTCP uses SYN+FIN. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 13:54:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 2DE0714F08 for ; Tue, 11 Jan 2000 13:54:17 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id WAA79448; Tue, 11 Jan 2000 22:54:15 +0100 (CET) (envelope-from olli) Date: Tue, 11 Jan 2000 22:54:15 +0100 (CET) Message-Id: <200001112154.WAA79448@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels X-Newsgroups: list.freebsd-stable In-Reply-To: <85g153$2l11$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG remorse code wrote in list.freebsd-stable: > Oliver Fromme writes: > Just don't boot FreeBSD from DOS. > > If that's the case, has fbsdboot.exe been removed from the 3.4 CD? Yes, as far as I know. fbsdboot.exe was located in /usr/mdec, and /usr/mdec is gone. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 14:14:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (adsl-gte-la-216-86-200-115.mminternet.com [216.86.200.115]) by hub.freebsd.org (Postfix) with ESMTP id 192D314D80 for ; Tue, 11 Jan 2000 14:14:15 -0800 (PST) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id OAA11571; Tue, 11 Jan 2000 14:13:54 -0800 (PST) (envelope-from boing) From: Geff Hanoian Message-Id: <200001112213.OAA11571@kusanagi.boing.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001111942.LAA00337@shell13.ba.best.com> from remorse code at "Jan 11, 2000 11:42:31 am" To: rone@ennui.org (remorse code) Date: Tue, 11 Jan 2000 14:13:49 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oliver Fromme writes: > Just don't boot FreeBSD from DOS. > > If that's the case, has fbsdboot.exe been removed from the 3.4 CD? Some embedded systems (PICOBSD) will only boot off a DOS partition. Won't this affect those? Geff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 14:30:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 01B0314E7D for ; Tue, 11 Jan 2000 14:30:53 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id OAA90477; Tue, 11 Jan 2000 14:30:40 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 11 Jan 2000 14:30:40 -0800 (PST) From: Doug White To: Geff Hanoian Cc: remorse code , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001112213.OAA11571@kusanagi.boing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Geff Hanoian wrote: > > Oliver Fromme writes: > > Just don't boot FreeBSD from DOS. > > > > If that's the case, has fbsdboot.exe been removed from the 3.4 CD? > > Some embedded systems (PICOBSD) will only boot off a DOS partition. Won't this > affect those? Like what? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 14:43:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [171.64.234.70]) by hub.freebsd.org (Postfix) with ESMTP id 993BD152BB; Tue, 11 Jan 2000 14:43:18 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id OAA90308; Tue, 11 Jan 2000 14:43:17 -0800 (PST) Date: Tue, 11 Jan 2000 14:43:17 -0800 (PST) From: Bob Vaughan Message-Id: <200001112243.OAA90308@tantivy.stanford.edu> To: obrien@FreeBSD.ORG, robinson@netrinsics.com Subject: Re: 4.4 BSD forever? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <200001110410.MAA71581@netrinsics.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Tue, 11 Jan 2000 12:10:39 +0800 (CST) > From: Michael Robinson > Subject: Re: 4.4 BSD forever? > > "David O'Brien" writes: > >It isn't a Mt. Xinu poster. It is a BSDI poster with the Daemon on it > >and it did say "4.4 > 5.4". "5.4" refered to System V Rel. 4., which was > >fairly new at the time. > > Oh. Nevermind. The one I'm looking for is the Mt. Xinu poster with the > ratty BSD X-Wing Fighter blowing up the AT&T "Death Star" logo. I'm pretty > sure that one said "4.2 > V". > > -Michael Robinson I have one of the "4.4 > 5.4" posters, which IIRC wwere being handed out from the BSDI booth at Interop 93 San Francisco. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 19792, Stanford, Ca 94309 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 15: 4:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (adsl-gte-la-216-86-200-115.mminternet.com [216.86.200.115]) by hub.freebsd.org (Postfix) with ESMTP id 3CA7C151FE for ; Tue, 11 Jan 2000 15:04:35 -0800 (PST) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id PAA11724; Tue, 11 Jan 2000 15:04:31 -0800 (PST) (envelope-from boing) From: Geff Hanoian Message-Id: <200001112304.PAA11724@kusanagi.boing.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: from Doug White at "Jan 11, 2000 2:30:40 pm" To: dwhite@resnet.uoregon.edu (Doug White) Date: Tue, 11 Jan 2000 15:04:20 -0800 (PST) Cc: boing@boing.com, rone@ennui.org, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 11 Jan 2000, Geff Hanoian wrote: > > > > Oliver Fromme writes: > > > Just don't boot FreeBSD from DOS. > > > > > > If that's the case, has fbsdboot.exe been removed from the 3.4 CD? > > > > Some embedded systems (PICOBSD) will only boot off a DOS partition. Won't this > > affect those? > > Like what? Like, if I am required by the hardware (for whatever reason) to boot off of a FAT16 partition with a 'Command.com' type thing, wouldn't the fbsdboot.exe allow me to still boot a bsd kernel. Where as if I must install the boot loader, I might not even be able to get the boot loader to show up on the hardware disk emulator. Does that make sense? Geff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 15:31: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (oberon.ntu-kpi.kiev.ua [195.178.136.20]) by hub.freebsd.org (Postfix) with ESMTP id 46BBE15191 for ; Tue, 11 Jan 2000 15:30:48 -0800 (PST) (envelope-from jar@ntu-kpi.kiev.ua) Received: by relay1.ntu-kpi.kiev.ua (Postfix, from userid 1122) id 0F6D72FA1B; Wed, 12 Jan 2000 01:30:40 +0200 (EET) From: Yaroslav Halchinsky To: freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.2-STABLE (i386)) Message-Id: <20000111233040.0F6D72FA1B@relay1.ntu-kpi.kiev.ua> Date: Wed, 12 Jan 2000 01:30:40 +0200 (EET) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, tosh@assa.vl.net.ua wrote: > is there way to boot fbsd3.x from dos? all ok with 2.2.8, > but in 3.x fbsdboot.exe say 'Invalid format'. > also i see that fbsdboot.exe is not changed since 2.xx > it can't support elf format at all? fbsdboot.exe wants your kernel to be a.out format, I guess. I'm not aware of any problems a.out kernel can bring, but in the situation with netboot which also wants a.out kernels it worked pretty well. Don't exactly remember how did I manage to build that kind of kernel, you may want to start with "makeoptions" in config file. -- Regards, Yaroslav Halchinsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 16: 5: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id A798314C0C for ; Tue, 11 Jan 2000 16:05:03 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2021.bossig.com [208.26.242.21]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id ; Tue, 11 Jan 2000 16:12:36 -0800 Message-ID: <387BC51B.BE88772D@3-cities.com> Date: Tue, 11 Jan 2000 16:04:43 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Mr. K." Cc: james , freebsd-stable@freebsd.org Subject: Re: Telnet freezes with wait chan of 'ttywri'/'ttywai' References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Mr. K." wrote: > > On Tue, 11 Jan 2000, james wrote: > > > > > Hi, > > > > I've just had another freeze on a telnet session from my Windows machine to > > my FreeBSD 4.0-CURRENT machine with a wait chan of 'ttywri'. I decided to > > I've run into this also, several times. > > > Any ideas what could be wrong? I can send any other output or config if you > > like.. I just don't want to include some massive email if the problem is > > really trivial or whatever.. > > > Here's an off the wall question which might explain why not everyone is > running into this. Are you using windows 2000? I think I started running > into this problem about the same time I "upgraded" to windows 2000. I've seem something like a freeze but it was really Win 2000 / FreeBSD 3.4 not echoing. The characters were making it though but just didn't show up in the terminal window. Kent > > > Cheers > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 16:44:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 3270C1513A for ; Tue, 11 Jan 2000 16:44:19 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with SMTP id RAA10486; Tue, 11 Jan 2000 17:41:50 -0700 (MST) Date: Tue, 11 Jan 2000 17:41:49 -0700 (MST) From: "Forrest W. Christian" To: Geff Hanoian Cc: remorse code , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001112213.OAA11571@kusanagi.boing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Geff Hanoian wrote: > Some embedded systems (PICOBSD) will only boot off a DOS partition. Huh? Since when? I use PicoBSD a lot and rarely (if ever) have any dos-like os on it. However, I DO agree that being able to use DOS as a fancy boot loader is a Good Thing (tm). - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 17: 5:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id BB68114EF2 for ; Tue, 11 Jan 2000 17:05:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA01750; Tue, 11 Jan 2000 17:11:52 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120111.RAA01750@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geff Hanoian Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Tue, 11 Jan 2000 15:04:20 PST." <200001112304.PAA11724@kusanagi.boing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 17:11:52 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Like, if I am required by the hardware (for whatever reason) to boot off of > a FAT16 partition with a 'Command.com' type thing, wouldn't the fbsdboot.exe > allow me to still boot a bsd kernel. Where as if I must install the boot > loader, I might not even be able to get the boot loader to show up on the > hardware disk emulator. > > Does that make sense? It sounds like a contrived hypothetical example. Would you care to share a real-world example with us? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 17: 5:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 50C6414EF2 for ; Tue, 11 Jan 2000 17:05:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA01718; Tue, 11 Jan 2000 17:10:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120110.RAA01718@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Forrest W. Christian" Cc: Geff Hanoian , remorse code , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Tue, 11 Jan 2000 17:41:49 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 17:10:47 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, I DO agree that being able to use DOS as a fancy boot loader is a > Good Thing (tm). This would only be a Good Thing if DOS didn't totally screw the machine up. As it is, it's a Very Bloody Stupid thing, and this is exactly why we have the loader instead. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 17: 6:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id A36EC150AC for ; Tue, 11 Jan 2000 17:06:47 -0800 (PST) (envelope-from kris@hiwaay.net) Received: from tnt6-216-180-5-210.dialup.HiWAAY.net (tnt6-216-180-5-210.dialup.HiWAAY.net [216.180.5.210]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id TAA20575; Tue, 11 Jan 2000 19:06:10 -0600 (CST) Date: Tue, 11 Jan 2000 19:06:06 -0600 (CST) From: Kris Kirby To: "Forrest W. Christian" Cc: Geff Hanoian , remorse code , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, I DO agree that being able to use DOS as a fancy boot loader is a > Good Thing (tm). Gee Forrest, that's kinda redundant... :-) --- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "God gave them the ability to reproduce... ... Science gave us the hope they won't." -KBK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 17:19: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (adsl-gte-la-216-86-200-115.mminternet.com [216.86.200.115]) by hub.freebsd.org (Postfix) with ESMTP id 9488614E5E for ; Tue, 11 Jan 2000 17:18:59 -0800 (PST) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id RAA12047; Tue, 11 Jan 2000 17:18:46 -0800 (PST) (envelope-from boing) From: Geff Hanoian Message-Id: <200001120118.RAA12047@kusanagi.boing.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: from "Forrest W. Christian" at "Jan 11, 2000 5:41:49 pm" To: forrestc@iMach.com (Forrest W. Christian) Date: Tue, 11 Jan 2000 17:18:37 -0800 (PST) Cc: boing@boing.com, rone@ennui.org, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 11 Jan 2000, Geff Hanoian wrote: > > > Some embedded systems (PICOBSD) will only boot off a DOS partition. > > Huh? Since when? > > I use PicoBSD a lot and rarely (if ever) have any dos-like os on it. > > However, I DO agree that being able to use DOS as a fancy boot loader is a > Good Thing (tm). I breifly examined building an embedded system and some of them only wanted to boot off a fat 16 partition with a "command.com" like thing. Didn't research it too much, but it didn't seem flexible enough to boot off of a boot/loader type thing. Sure PicoBSD works fine on a floppy with a normal intel box and the boot/loader stuff. Geff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 17:22:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (adsl-gte-la-216-86-200-115.mminternet.com [216.86.200.115]) by hub.freebsd.org (Postfix) with ESMTP id 17AAE1546E; Tue, 11 Jan 2000 17:22:51 -0800 (PST) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id RAA12091; Tue, 11 Jan 2000 17:22:52 -0800 (PST) (envelope-from boing) From: Geff Hanoian Message-Id: <200001120122.RAA12091@kusanagi.boing.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001120111.RAA01750@mass.cdrom.com> from Mike Smith at "Jan 11, 2000 5:11:52 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Tue, 11 Jan 2000 17:22:47 -0800 (PST) Cc: boing@boing.com, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Like, if I am required by the hardware (for whatever reason) to boot off of > > a FAT16 partition with a 'Command.com' type thing, wouldn't the fbsdboot.exe > > allow me to still boot a bsd kernel. Where as if I must install the boot > > loader, I might not even be able to get the boot loader to show up on the > > hardware disk emulator. > > > > Does that make sense? > > It sounds like a contrived hypothetical example. Would you care to share > a real-world example with us? Mike, I did the research a few months ago. One manufacturer actually wanted to sell us a compiler to install a "DOS thing" according the sales person. I don't remember the models, etc. I'll look it up at some point. Maybe some embedded experts could lend a hand? I'm defintely an embedded beginner. It could have been my lack of understanding and the salesperson's lack of technical knowledge / communication skills. Geff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 17:30:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id CC7DC15451 for ; Tue, 11 Jan 2000 17:30:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02138; Tue, 11 Jan 2000 17:37:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120137.RAA02138@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geff Hanoian Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Tue, 11 Jan 2000 17:18:37 PST." <200001120118.RAA12047@kusanagi.boing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 17:37:03 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I breifly examined building an embedded system and some of them only > wanted to boot off a fat 16 partition with a "command.com" like thing. > Didn't research it too much, but it didn't seem flexible enough to boot > off of a boot/loader type thing. Sure PicoBSD works fine on a floppy with > a normal intel box and the boot/loader stuff. I can fairly say that I have a reasonable amount of experience with embedded systems, and I can't recall seeing anything like this in the last ten or so years. You may have been looking at a system with layered software like DOS-in-ROM, or possibly just something totally weird I guess. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 17:39:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id ADFE315495; Tue, 11 Jan 2000 17:39:15 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.3/8.9.3) with ESMTP id UAA50677; Tue, 11 Jan 2000 20:39:14 -0500 (EST) (envelope-from melange@yip.org) Date: Tue, 11 Jan 2000 20:39:13 -0500 (EST) From: Bob K X-Sender: melange@localhost To: Mike Smith Cc: Geff Hanoian , freebsd-stable@FreeBSD.ORG Subject: [OT] DOS-in-ROM (was Re: fbsdboot.exe can't load elf kernels) In-Reply-To: <200001120137.RAA02138@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Mike Smith wrote: > > I breifly examined building an embedded system and some of them only > > wanted to boot off a fat 16 partition with a "command.com" like thing. > > Didn't research it too much, but it didn't seem flexible enough to boot > > off of a boot/loader type thing. Sure PicoBSD works fine on a floppy with > > a normal intel box and the boot/loader stuff. > > I can fairly say that I have a reasonable amount of experience with > embedded systems, and I can't recall seeing anything like this in the > last ten or so years. > > You may have been looking at a system with layered software like > DOS-in-ROM, or possibly just something totally weird I guess. Just as an aside, I spent all day today using an 80286 laptop with DOS-in-ROM (running TeleMate off a floppy). Now this has got me wondering if PicoBSD would run on that thing... Bob "I love signing autographs. I'll sign anything but veal cutlets. My ballpoint pen slips on veal cutlets." - Casey Stengel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 18:13:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 9BE7E15457; Tue, 11 Jan 2000 18:13:43 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 128DHx-000Fx4-00; Tue, 11 Jan 2000 18:13:33 -0800 Date: Tue, 11 Jan 2000 18:13:28 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Bob K Cc: Mike Smith , Geff Hanoian , freebsd-stable@FreeBSD.ORG Subject: Re: [OT] DOS-in-ROM (was Re: fbsdboot.exe can't load elf kernels) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Bob K wrote: > On Tue, 11 Jan 2000, Mike Smith wrote: > > > > I breifly examined building an embedded system and some of them only > > > wanted to boot off a fat 16 partition with a "command.com" like thing. > > > Didn't research it too much, but it didn't seem flexible enough to boot > > > off of a boot/loader type thing. Sure PicoBSD works fine on a floppy with > > > a normal intel box and the boot/loader stuff. > > > > I can fairly say that I have a reasonable amount of experience with > > embedded systems, and I can't recall seeing anything like this in the > > last ten or so years. > > > > You may have been looking at a system with layered software like > > DOS-in-ROM, or possibly just something totally weird I guess. > > Just as an aside, I spent all day today using an 80286 laptop with > DOS-in-ROM (running TeleMate off a floppy). Now this has got me wondering > if PicoBSD would run on that thing... FreeBSD will never run on a 286. > Bob > "I love signing autographs. I'll sign anything but veal cutlets. My > ballpoint pen slips on veal cutlets." - Casey Stengel Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 18:32:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by hub.freebsd.org (Postfix) with ESMTP id 6F927154C7 for ; Tue, 11 Jan 2000 18:32:32 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 935571BD4; Tue, 11 Jan 2000 20:51:35 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14459.56870.755754.646792@anarcat.dyndns.org> Date: Tue, 11 Jan 2000 20:51:34 -0500 (EST) To: Geff Hanoian Cc: rone@ennui.org (remorse code), freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels References: <200001111942.LAA00337@shell13.ba.best.com> <200001112213.OAA11571@kusanagi.boing.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Reply-To: beaupran@iro.umontreal.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I'm not mistaken, PicoBSD boots from a ufs floppy. --- Big Brother told Geff Hanoian to write, at 14:13 of January 11: > > Oliver Fromme writes: > > Just don't boot FreeBSD from DOS. > > > > If that's the case, has fbsdboot.exe been removed from the 3.4 CD? > > Some embedded systems (PICOBSD) will only boot off a DOS partition. Won't this > affect those? > > Geff > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19: 1:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 3DB60154F4; Tue, 11 Jan 2000 19:00:56 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with SMTP id TAA11462; Tue, 11 Jan 2000 19:59:09 -0700 (MST) Date: Tue, 11 Jan 2000 19:59:08 -0700 (MST) From: "Forrest W. Christian" To: Geff Hanoian Cc: Mike Smith , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001120122.RAA12091@kusanagi.boing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Geff Hanoian wrote: > I did the research a few months ago. One manufacturer actually wanted > to sell us a compiler to install a "DOS thing" according the sales person. > I don't remember the models, etc. I'll look it up at some point. Maybe some > embedded experts could lend a hand? I'm defintely an embedded beginner. Nearly 100% of "modern" Flash Memory devices either emulate an IDE drive in Hardware or have emulate a standard BIOS disk device using some sort of BIOS driver, usually in such a way so that it will boot a DOS-like OS from it. Of course, the ones which truly emulate an IDE drive at the hardware level just work like an IDE drive, although slower on writes. The BIOS ones get tricky. Obviously, if the boot loader only uses bios calls to do it's dirty work, these work well, at least through the boot process. If the boot loader tries to access the hardware directly, and it doesn't directly support the flash device, then the boot loader doesn't work. Of course, this also applies to the OS. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:21: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (adsl-gte-la-216-86-200-115.mminternet.com [216.86.200.115]) by hub.freebsd.org (Postfix) with ESMTP id 9E2BA154C6; Tue, 11 Jan 2000 19:20:56 -0800 (PST) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id TAA12354; Tue, 11 Jan 2000 19:20:57 -0800 (PST) (envelope-from boing) From: Geff Hanoian Message-Id: <200001120320.TAA12354@kusanagi.boing.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: from "Forrest W. Christian" at "Jan 11, 2000 7:59: 8 pm" To: forrestc@iMach.com (Forrest W. Christian) Date: Tue, 11 Jan 2000 19:20:52 -0800 (PST) Cc: boing@boing.com, msmith@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 11 Jan 2000, Geff Hanoian wrote: > > > I did the research a few months ago. One manufacturer actually wanted > > to sell us a compiler to install a "DOS thing" according the sales person. > > I don't remember the models, etc. I'll look it up at some point. Maybe some > > embedded experts could lend a hand? I'm defintely an embedded beginner. > > Nearly 100% of "modern" Flash Memory devices either emulate an IDE drive > in Hardware or have emulate a standard BIOS disk device using some sort of > BIOS driver, usually in such a way so that it will boot a DOS-like OS from > it. This is what I remember from my research. > Of course, the ones which truly emulate an IDE drive at the hardware level > just work like an IDE drive, although slower on writes. > > The BIOS ones get tricky. Obviously, if the boot loader only uses bios > calls to do it's dirty work, these work well, at least through the boot > process. If the boot loader tries to access the hardware directly, and it > doesn't directly support the flash device, then the boot loader doesn't > work. Of course, this also applies to the OS. And that's assuming you could actually get a UFS partition on the "drive emulator thing"? But if you were only capable of loading files to a fat16, then wouldn't fbsdboot.exe (or whatever it's called) be necessary? Geff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:32:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 40063150E1; Tue, 11 Jan 2000 19:32:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA03976; Tue, 11 Jan 2000 19:38:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120338.TAA03976@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geff Hanoian Cc: forrestc@iMach.com (Forrest W. Christian), msmith@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Tue, 11 Jan 2000 19:20:52 PST." <200001120320.TAA12354@kusanagi.boing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 19:38:24 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Of course, the ones which truly emulate an IDE drive at the hardware level > > just work like an IDE drive, although slower on writes. > > > > The BIOS ones get tricky. Obviously, if the boot loader only uses bios > > calls to do it's dirty work, these work well, at least through the boot > > process. If the boot loader tries to access the hardware directly, and it > > doesn't directly support the flash device, then the boot loader doesn't > > work. Of course, this also applies to the OS. > > And that's assuming you could actually get a UFS partition on the "drive > emulator thing"? But if you were only capable of loading files to a fat16, > then wouldn't fbsdboot.exe (or whatever it's called) be necessary? No. Firstly, you are again raising a hypothetical question without actually suggesting anything that might require this, so bear with me if I don't take it too seriously. Things just don't really work like this. However, if you assume that you can for some reason only boot from a FAT16 filesystem, and for some reason you want to run FreeBSD on this hardware and only this hardware, then you would rewrite boot2 to read FAT filesystems. There is still no need to boot DOS. In a very few cases, you'll find disk 'emulators' that offer BIOS interfaces to the emulated disk. These are rapidly declining in popularity because they offer very poor performance for Windows-using customers. They also typically fare very poorly or not at all under other operating systems, as they tend to require timer interrupts in a very hostile fashion. Please; take it from me that "booting DOS to boot another operating system" is so far beyond a joke in most situations that we don't even want to pretend in public that it's done, let alone talk about supporting it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:32:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 5889F154EC for ; Tue, 11 Jan 2000 19:32:50 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from nwlink.com (ip248.r8.d.bel.nwlink.com [207.202.173.248]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id TAA14386 for ; Tue, 11 Jan 2000 19:32:48 -0800 (PST) Message-ID: <387BF513.8A2D607E@nwlink.com> Date: Tue, 11 Jan 2000 19:29:23 -0800 From: R Joseph Wright X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Nearly 100% of "modern" Flash Memory devices either emulate an IDE drive > in Hardware or have emulate a standard BIOS disk device using some sort of > BIOS driver, usually in such a way so that it will boot a DOS-like OS from > it. Which brings up the question that keeps nagging at me: How possible is it to create a pc bios that is geared towards BSD/linux? This would include its own lightweight repair shell. Couldn't this solve a lot of problems with pc hardware, to have a unix-oriented bios? -- Best Regards, Joseph You will do foolish things, but do them with enthusiasm. Colette. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:33:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 73E9C1551F; Tue, 11 Jan 2000 19:33:28 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id JAA33394; Wed, 12 Jan 2000 09:32:09 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 12 Jan 2000 09:32:08 +0600 (NS) From: Max Khon To: Mikhail Teterin Cc: obrien@FreeBSD.ORG, ache@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: isprint(3) and LANG/LOCALE In-Reply-To: <200001111404.JAA92453@rtfm.newton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 11 Jan 2000, Mikhail Teterin wrote: > =grrr. i mean 'unsigned' > > Yes, that helped! A call to setlocale() was also neccessary, though... > I'll send a patch for the Jpeg port. setlocale() is always necessary to make locales work. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:37:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 1998214FC6 for ; Tue, 11 Jan 2000 19:37:10 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA04076; Tue, 11 Jan 2000 19:43:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120343.TAA04076@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: R Joseph Wright Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Tue, 11 Jan 2000 19:29:23 PST." <387BF513.8A2D607E@nwlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 19:43:35 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Nearly 100% of "modern" Flash Memory devices either emulate an IDE drive > > in Hardware or have emulate a standard BIOS disk device using some sort of > > BIOS driver, usually in such a way so that it will boot a DOS-like OS from > > it. > > Which brings up the question that keeps nagging at me: How possible is > it to create a pc bios that is geared towards BSD/linux? This would > include its own lightweight repair shell. Couldn't this solve a lot of > problems with pc hardware, to have a unix-oriented bios? No. If you think about what BIOS code actually does, this should really be fairly obvious. In all reality, new BIOS features are actually directed towards the same sort of problems that we're facing, even if the process is driven largely by Microsoft. Take a look at eg. ACPI to see what I mean. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:44:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id DCC23150E1; Tue, 11 Jan 2000 19:44:20 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from nwlink.com (ip248.r8.d.bel.nwlink.com [207.202.173.248]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id TAA16095; Tue, 11 Jan 2000 19:44:19 -0800 (PST) Message-ID: <387BF7C5.AA29A063@nwlink.com> Date: Tue, 11 Jan 2000 19:40:53 -0800 From: R Joseph Wright X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels References: <200001120343.TAA04076@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > > > Nearly 100% of "modern" Flash Memory devices either emulate an IDE drive > > > in Hardware or have emulate a standard BIOS disk device using some sort of > > > BIOS driver, usually in such a way so that it will boot a DOS-like OS from > > > it. > > > > Which brings up the question that keeps nagging at me: How possible is > > it to create a pc bios that is geared towards BSD/linux? This would > > include its own lightweight repair shell. Couldn't this solve a lot of > > problems with pc hardware, to have a unix-oriented bios? > > No. If you think about what BIOS code actually does, this should really > be fairly obvious. Sorry, I'm clueless 8). What does it do, exactly? > > In all reality, new BIOS features are actually directed towards the same > sort of problems that we're facing, even if the process is driven largely > by Microsoft. Take a look at eg. ACPI to see what I mean. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com -- Best Regards, Joseph You will do foolish things, but do them with enthusiasm. Colette. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:52:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id D24EC14DCF for ; Tue, 11 Jan 2000 19:52:34 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id JAA34055; Wed, 12 Jan 2000 09:50:41 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 12 Jan 2000 09:50:41 +0600 (NS) From: Max Khon To: Anton Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 11 Jan 2000, Anton wrote: > is there way to boot fbsd3.x from dos? all ok with 2.2.8, > but in 3.x fbsdboot.exe say 'Invalid format'. > also i see that fbsdboot.exe is not changed since 2.xx > it can't support elf format at all? "Carlos C. Tapang" once patched fbsdboot to load ELF kernels. He put it to ftp://ftp.genericwindows.com/pub/fbsdboot.exe but this host does not exist anymore. I have a copy of his fbsdboot at ftp://iclub.nsu.ru/pub/FreeBSD/incoming/fbsdboot.exe I have not tested it. Tell me if it works or not. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 19:57:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 1154F14E37 for ; Tue, 11 Jan 2000 19:57:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA04357; Tue, 11 Jan 2000 20:04:05 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120404.UAA04357@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: R Joseph Wright Cc: stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Tue, 11 Jan 2000 19:40:53 PST." <387BF7C5.AA29A063@nwlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 20:04:05 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > No. If you think about what BIOS code actually does, this should really > > be fairly obvious. > > Sorry, I'm clueless 8). What does it do, exactly? Provides an abstract interface to a completely arbitrary hardware instance. Since there are no hardware standards at this level, you'd have to duplicate the unix-specific BIOS for every piece of hardware out there. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 21:14: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id AE77014BE7 for ; Tue, 11 Jan 2000 21:13:58 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with SMTP id WAA12645; Tue, 11 Jan 2000 22:12:08 -0700 (MST) Date: Tue, 11 Jan 2000 22:12:07 -0700 (MST) From: "Forrest W. Christian" To: R Joseph Wright Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <387BF513.8A2D607E@nwlink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, R Joseph Wright wrote: > Which brings up the question that keeps nagging at me: How possible is > it to create a pc bios that is geared towards BSD/linux? This would > include its own lightweight repair shell. Couldn't this solve a lot of > problems with pc hardware, to have a unix-oriented bios? My take on this is: Possible != Portable. Or better put, Writing a "FreeBSD-cool" bios would be relatively easy. Trying to keep it updated and/or make it work on a whole bunch of different vendor's computers wouldn't. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 21:43:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 6F43214F2D; Tue, 11 Jan 2000 21:43:27 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with SMTP id WAA12834; Tue, 11 Jan 2000 22:41:46 -0700 (MST) Date: Tue, 11 Jan 2000 22:41:45 -0700 (MST) From: "Forrest W. Christian" To: Mike Smith Cc: Geff Hanoian , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001120338.TAA03976@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Mike Smith wrote: > In a very few cases, you'll find disk 'emulators' that offer BIOS > interfaces to the emulated disk. These are rapidly declining in > popularity because they offer very poor performance for Windows-using > customers. They also typically fare very poorly or not at all under > other operating systems, as they tend to require timer interrupts in a > very hostile fashion. I agree with your statement in general. However, in the "truly" embedded PC world, the most popular off-the-shelf Flash Disk solution (M-Systems DiskOnChip-Millenium) is actually of this type. However, this solution also provides native drivers for Windows and a whole host of other OS'es. If there isn't a FreeBSD driver available, expect one from me in a few weeks. However, in the "truly" embedded world, you generally do not want a multiple-stage boot process. In fact, I have spent a fair bit of time eradicating (sp?) most of the "unneccesary" multi-stage boot from the PicoBSD stuff I'm doing for a product of mine. The idea of actually putting a DOS "partition" on the system seems crazy. > Please; take it from me that "booting DOS to boot another operating > system" is so far beyond a joke in most situations that we don't even want > to pretend in public that it's done, let alone talk about supporting it. There is only one circumstance in which this might be acceptable, and that is to support co-habitation with an OS which REQUIRES it's own MBR which doesn't support dual-booting to a FreeBSD partition. I can't think of any modern OS that works this way. And even if there was, I can think of a million other ways to get around this than writing a DOS-based loader. A few byte program which basically executes the FreeBSD bootstrap program comes to mind. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 22:11:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 9AD9215507; Tue, 11 Jan 2000 22:11:31 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id WAA26942; Tue, 11 Jan 2000 22:11:17 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001120611.WAA26942@gndrsh.dnsmgr.net> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: from "Forrest W. Christian" at "Jan 11, 2000 10:41:45 pm" To: forrestc@iMach.com (Forrest W. Christian) Date: Tue, 11 Jan 2000 22:11:17 -0800 (PST) Cc: msmith@FreeBSD.ORG (Mike Smith), boing@boing.com (Geff Hanoian), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > However, in the "truly" embedded world, you generally do not want a > multiple-stage boot process. In fact, I have spent a fair bit of time > eradicating (sp?) most of the "unneccesary" multi-stage boot from the > PicoBSD stuff I'm doing for a product of mine. The idea of actually > putting a DOS "partition" on the system seems crazy. I've been thinking of reverse engineering or obtaining through other means the Award ``BIOS boot block'' code that resides in a certain motherboard so that I can simply FLASH the FreeBSD kernel into the 2MB FLASH roms for an embedded project. One of the forseen problems with doing this is that the BIOS boot block code usually does the absolute minimum as far as chipset configuration goes and given the complexity of modern chipsets this leaves a big gapping hole. I have on other occasions modified AWARD bios's to add things like the netboot code for a specific NIC card that doesn't have a EEPROM socket on it. I justed grab the space normally used by the SMDS/Symbios BIOS and splatted the code right in. Worked like a champ :-) Hummmm... I can easily cram boot0, boot1 and boot2 in there, but loader is a bit to big at 128K bytes :-(. ... > - Forrest W. Christian (forrestc@imach.com) KD7EHZ ^^^^^^ Hey... a ham from my own region newer than me, and a FreeBSD'er :-) 73, -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 11 23:52: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 9165215449 for ; Tue, 11 Jan 2000 23:51:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA00488; Tue, 11 Jan 2000 23:58:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120758.XAA00488@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rodney W. Grimes" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Tue, 11 Jan 2000 22:11:17 PST." <200001120611.WAA26942@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jan 2000 23:58:43 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hummmm... I can easily cram boot0, boot1 and boot2 in there, but loader > is a bit to big at 128K bytes :-(. You don't need the loader for most 'embedded' applications. Boot2 will do you fine. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 0:16:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ktts.kharkov.ua (ktts.kharkov.ua [193.124.57.65]) by hub.freebsd.org (Postfix) with ESMTP id 3784F14DE0 for ; Wed, 12 Jan 2000 00:16:21 -0800 (PST) (envelope-from tosh@assa.vl.net.ua) Received: from assa.vl.net.ua (assa.vl.net.ua [193.124.76.15]) by ktts.kharkov.ua (8.9.3/8.9.3) with ESMTP id KAA02338; Wed, 12 Jan 2000 10:13:05 +0200 (EET) Received: from assa ([192.168.1.1]) by assa.vl.net.ua with esmtp (Exim 2.053 #1) id 128Itl-0000jt-00; Wed, 12 Jan 2000 10:12:57 +0200 Date: Wed, 12 Jan 2000 10:12:56 +0200 (EET) From: Anton X-Sender: tosh@assa To: Max Khon Cc: freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello. On Wed, 12 Jan 2000, Max Khon wrote: > ftp://iclub.nsu.ru/pub/FreeBSD/incoming/fbsdboot.exe > I have not tested it. Tell me if it works or not. it can boot elf cernels, but i have: no init panic: no init rebooting at N seconds... maybe i must specify root device? but how? i dont remember such problems with old fbsdboot.exe (or it's kernel's problem?) anton. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 0:23:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 6BE7814DE0 for ; Wed, 12 Jan 2000 00:23:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA00633; Wed, 12 Jan 2000 00:28:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001120828.AAA00633@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Anton Cc: Max Khon , freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Wed, 12 Jan 2000 10:12:56 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 00:28:20 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The ability to load and start a kernel != the ability to boot and run same. You cannot boot and run FreeBSD once DOS has been booted on the system. You should give up now before you waste any more of your or our time. There are good technical reasons why this is the case. If you don't understand them, please trust those of us that do. Thankyou. > hello. > > On Wed, 12 Jan 2000, Max Khon wrote: > > > ftp://iclub.nsu.ru/pub/FreeBSD/incoming/fbsdboot.exe > > I have not tested it. Tell me if it works or not. > > it can boot elf cernels, but i have: > > no init > panic: no init > > rebooting at N seconds... > > maybe i must specify root device? but how? > i dont remember such problems with old fbsdboot.exe > (or it's kernel's problem?) > > anton. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 0:30:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7DEBF14C80; Wed, 12 Jan 2000 00:30:49 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA76720; Wed, 12 Jan 2000 09:30:45 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Cy Schubert - ITSD Open Systems Group Cc: Brad Knowles , Holtor , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Kernel Option: TCP_DROP_SYNFIN References: <200001111947.LAA55191@cwsys.cwsent.com> From: Dag-Erling Smorgrav Date: 12 Jan 2000 09:30:44 +0100 In-Reply-To: Cy Schubert - ITSD Open Systems Group's message of "Tue, 11 Jan 2000 11:46:43 -0800" Message-ID: Lines: 23 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group writes: > In message , Dag-Erling Smorgrav > writes: > > It doesn't have anything to do with syn floods at all. It merely > > prevents OS fingerprinting (at least the way nmap does it). > The following ipfw rule will also prevent OS fingerprinting. > > deny log tcp from any to any in tcpflg fin,syn It does precisely the same thing as TCP_DROP_SYNFIN, except much slower. > Would this too have problems with TTCP? The reason I ask is that I've > been using this rule for a ever since 2.2.x (cannot remember the exact > date) and I haven't had any problems with TTCP enabled. I know I > should look at the RFC (and I will after lunch), but I'll ask anyway. > Does TTCP use packets with SYN/FIN set? Yes, if the request (or reply) is short enough to fit in a single segment, which is exceedingly rare these days. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 1:13:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id 2C46D150B6; Wed, 12 Jan 2000 01:12:36 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id KAA01286; Wed, 12 Jan 2000 10:11:43 +0100 (MET) Date: Wed, 12 Jan 2000 10:11:40 +0100 (MET) From: Marcin Cieslak To: "Forrest W. Christian" Cc: Mike Smith , Geff Hanoian , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels (flash cards off topic) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Forrest W. Christian wrote: > I agree with your statement in general. However, in the "truly" embedded > PC world, the most popular off-the-shelf Flash Disk solution (M-Systems > DiskOnChip-Millenium) is actually of this type. However, this solution > also provides native drivers for Windows and a whole host of other OS'es. > If there isn't a FreeBSD driver available, expect one from me in a few > weeks. Once there I managed to read a flash card containing Cisco IOS (it was M-Systems - or other manufacturer). However, the flash was one of linear types - just plain of bytes, and no wd/ata emulation. pccardd from PAO (3.2 then I guess) of course didn't detect nor load the driver, but I read this using pccardc without any problem (all filesystem structure, very simple at the moment and file contents). I guess that some special operation would be required to program the flash, but... Well, this is no longer freebsd-stable, is it? :) -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 1:49:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id A816A154C8 for ; Wed, 12 Jan 2000 01:49:48 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id KAA00831 for ; Wed, 12 Jan 2000 10:49:31 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Wed, 12 Jan 2000 10:49:31 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: shutdown problems FBSD 3.4-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I installed vinum with softupdates, I have several problems when shutting down the server. Whenever I shut down the machine, init reports a non dying process and tells me, that ps axl has been adviced. After a few seconds this process, which name I never see, has obviously been killed and the system performs a normal shutdown or reboot. But sometimes the las tmessage on the screen is that all disks has been sync'ed but nothing happens further on. The system is stuck in this process and seems to be frozen. Only a reset or powercycle can help, but then fsck reports some dirty partitions ... How can I find out what process won't dy? How to figure out what process causes the hanging or freezing the system after shutdown? With regards, Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 2:13:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.access1.net (smtp.access1.net [206.13.101.40]) by hub.freebsd.org (Postfix) with ESMTP id 94FE714EE6; Wed, 12 Jan 2000 02:13:37 -0800 (PST) (envelope-from ccthomas@access1.net) Received: from bsdone.SAMBA [209.244.113.6] by smtp.access1.net (SMTPD32-5.01) id A37849E400CE; Wed, 12 Jan 2000 02:12:08 PDT Message-ID: <387C54F5.167EB0E7@access1.net> Date: Wed, 12 Jan 2000 05:18:29 -0500 From: Courtney Thomas X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: Mike Smith Cc: Anton , Max Khon , freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels References: <200001120828.AAA00633@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings ! What would be the best reference(es) [on/off web] describing said process(es) ? Thanks, Courtney <--------------------------------------------------------------- Mike Smith wrote: > > The ability to load and start a kernel != the ability to boot and run > same. > > You cannot boot and run FreeBSD once DOS has been booted on the system. > You should give up now before you waste any more of your or our time. > > There are good technical reasons why this is the case. If you don't > understand them, please trust those of us that do. > > Thankyou. > > > hello. > > > > On Wed, 12 Jan 2000, Max Khon wrote: > > > > > ftp://iclub.nsu.ru/pub/FreeBSD/incoming/fbsdboot.exe > > > I have not tested it. Tell me if it works or not. > > > > it can boot elf cernels, but i have: > > > > no init > > panic: no init > > > > rebooting at N seconds... > > > > maybe i must specify root device? but how? > > i dont remember such problems with old fbsdboot.exe > > (or it's kernel's problem?) > > > > anton. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 3:41:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nts6.dvacm.gov (rems8.cio.med.va.gov [204.176.52.23]) by hub.freebsd.org (Postfix) with ESMTP id 249E814E5E for ; Wed, 12 Jan 2000 03:41:10 -0800 (PST) (envelope-from lluisma@osi-technologies.com) Received: from osi-technologies.com (localhost.dvacm.gov [127.0.0.1]) by nts6.dvacm.gov (8.9.3/8.9.3) with ESMTP id GAA03007; Wed, 12 Jan 2000 06:41:10 -0500 (EST) (envelope-from lluisma@osi-technologies.com) Message-ID: <387C6856.2FA1CB42@osi-technologies.com> Date: Wed, 12 Jan 2000 06:41:10 -0500 From: lluisma X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: 3.4-RELEASE and ThinkPad 770Z with 256MB memory Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I attempted to install 3.4 and it hangs after displaying "Probing PnP devices...". I was able to install RedHat Linux 6.1 but it only recognize 64MB memory instead of 256(I fixed this by adding append="mem=255M" to lilo.conf). Any suggestions are highly appreciated. Regards, LLU Linux version 2.2.12-20 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:40:35 EDT 1999 Detected 363963129 Hz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 362.91 BogoMIPS Memory: 256432k/261120k available (1008k kernel code, 412k reserved, 2924k data, 64k init) DENTRY hash table entries: 262144 (order: 9, 2097152 bytes) Buffer-cache hash table entries: 262144 (order: 8, 1048576 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) VFS: Diskquotas version dquot_6.4.0 initialized CPU: Intel Mobile Pentium II stepping 0a Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au) PCI: PCI BIOS revision 2.10 entry at 0xfd880 PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP TCP: Hash tables configured (ehash 262144 bhash 65536) Initializing RT netlink socket Starting kswapd v 1.5 Detected PS/2 Mouse Port. Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled pty: 256 Unix98 ptys configured apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) Real Time Clock Driver v1.09 RAM disk driver initialized: 16 RAM disks of 4096K size PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:DMA, hdd:pio hda: IBM-DCYA-214000, ATA DISK drive hdc: MATSHITADVD-ROM SR-8171, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: IBM-DCYA-214000, 7559MB w/420kB Cache, CHS=1023/240/63 hdc: ATAPI 20X DVD-ROM drive, 512kB Cache Uniform CDROM driver Revision: 2.56 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 raid5: measuring checksumming speed raid5: MMX detected, trying high-speed MMX checksum routines pII_mmx : 809.625 MB/sec p5_mmx : 850.392 MB/sec 8regs : 625.221 MB/sec 32regs : 350.520 MB/sec using fastest function: p5_mmx (850.392 MB/sec) scsi : 0 hosts. scsi : detected total. md.c: sizeof(mdp_super_t) = 4096 Partition check: hda: hda1 hda2 < hda5 hda6 hda7 hda8 > RAMDISK: Compressed image found at block 0 autodetecting RAID arrays autorun ... ... autorun DONE. VFS: Mounted root (ext2 filesystem). autodetecting RAID arrays autorun ... ... autorun DONE. VFS: Mounted root (ext2 filesystem) readonly. change_root: old root has d_count=1 Trying to unmount old root ... okay Freeing unused kernel memory: 64k freed Adding Swap: 529160k swap-space (priority -1) Linux PCMCIA Card Services 3.0.14 kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 options: [pci] [cardbus] [apm] Intel PCIC probe: TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50103000, 2 sockets host opts [0]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 2/4] host opts [1]: [ring] [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 5/7] ISA irqs (scanned) = 3,4,7,9,10 status change on irq 10 cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef cs: IO port probe 0x0100-0x04ff: excluding 0x130-0x137 0x200-0x207 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff cs: memory probe 0x60000000-0x60ffffff: clean. eth0: 3Com 3c589, io 0x300, irq 3, hw_addr 00:10:4B:EC:45:E4 8K FIFO split 5:3 Rx:Tx, auto xcvr eth0: flipped to 10baseT eth0: flipped to 10baseT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 3:52:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 900B11517D for ; Wed, 12 Jan 2000 03:52:30 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA01268; Wed, 12 Jan 2000 06:52:22 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA06788; Wed, 12 Jan 2000 06:52:21 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA66800; Wed, 12 Jan 2000 06:52:21 -0500 (EST) Date: Wed, 12 Jan 2000 06:52:21 -0500 (EST) From: Thomas David Rivers Message-Id: <200001121152.GAA66800@lakes.dignus.com> To: lluisma@osi-technologies.com, stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-Reply-To: <387C6856.2FA1CB42@osi-technologies.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uh... you're talking about install Linux, right? Perhaps you should take that up on a Linux mailing list... Of course, I would say the best answer to your problems would be to stop trying to install Linux and try out FreeBSD! - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 4: 2:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nts6.dvacm.gov (rems8.cio.med.va.gov [204.176.52.23]) by hub.freebsd.org (Postfix) with ESMTP id A6EE3154EB for ; Wed, 12 Jan 2000 04:02:51 -0800 (PST) (envelope-from lluisma@osi-technologies.com) Received: from osi-technologies.com (localhost.dvacm.gov [127.0.0.1]) by nts6.dvacm.gov (8.9.3/8.9.3) with ESMTP id HAA03032; Wed, 12 Jan 2000 07:02:18 -0500 (EST) (envelope-from lluisma@osi-technologies.com) Message-ID: <387C6D49.24EE19FB@osi-technologies.com> Date: Wed, 12 Jan 2000 07:02:17 -0500 From: lluisma X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Thomas David Rivers Cc: stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory References: <200001121152.GAA66800@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > Uh... you're talking about install Linux, right? Perhaps you I am trying to install FreeBSD 3.4. I was just displaying dmesg output from a running Linux system because I attempted to replace Linux with FreeBSD and the bsd install hangs after probing PnP devices. The dmesg is just to show you what kind of laptop I have and see if someone can give some ideas to make bsd install. I'm dying to have freebsd installed on this laptop... Thanks for any help. > > should take that up on a Linux mailing list... > > Of course, I would say the best answer to your problems would be > to stop trying to install Linux and try out FreeBSD! > > - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 4: 3: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 1FED1154EB for ; Wed, 12 Jan 2000 04:03:00 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id HAA41322; Wed, 12 Jan 2000 07:02:26 -0500 (EST) (envelope-from matt@zigg.com) Date: Wed, 12 Jan 2000 07:02:22 -0500 (EST) From: Matt Behrens To: Thomas David Rivers Cc: lluisma@osi-technologies.com, stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-Reply-To: <200001121152.GAA66800@lakes.dignus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 12 Jan 2000, Thomas David Rivers wrote: > Uh... you're talking about install Linux, right? Perhaps you > should take that up on a Linux mailing list... Well, actually, he was successful with Linux but not with FreeBSD. I'd wager the Linux dmesg was an attempt to let people see if he's got some funky hardware that might be causing his FreeBSD problem. > Of course, I would say the best answer to your problems would be > to stop trying to install Linux and try out FreeBSD! Looks like he's trying to do exactly that. :-) - -- Matt Behrens Owner/Administrator, zigg.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4fG1R+xq4JbgNGlMRAjWpAKClDqv95uNIfa/LmHeqnwQGdboKwwCeJyT6 cW9cTe6yQE5eR3VQZm1wLS4= =ZbYw -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 4:20:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtppzh.pzh.nl (webshield.pzh.nl [194.178.168.50]) by hub.freebsd.org (Postfix) with SMTP id 204F3154C1 for ; Wed, 12 Jan 2000 04:20:15 -0800 (PST) (envelope-from MULHUIJZEN@PZH.NL) Received: FROM smtp.pzh.nl BY smtppzh.pzh.nl ; Wed Jan 12 13:19:30 2000 0000 Received: from PZH40-1-Message_Server by smtp.pzh.nl with Novell_GroupWise; Wed, 12 Jan 2000 13:19:35 +0100 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Wed, 12 Jan 2000 13:19:21 +0100 From: "ROGIER MULHUIJZEN" To: Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I attempted to install 3.4 and it hangs after displaying "Probing PnP >devices...". I was able to install RedHat Linux 6.1 but it only >recognize 64MB memory instead of 256(I fixed this by adding >append="mem=255M" to lilo.conf). >Any suggestions are highly appreciated. Did you use the visual config to disable any devices, or did you boot straight away? If you didn't, try disabling as many devices as you think possible. If you did, could you try booting with the emergency repair disk and doing a dmesg (if that is possible, I think it is) from the shell? Also, on my Toshiba Tecra 8000 flashing the BIOS had a significant influence on the probing messages for PCI. I know PCI isn't exactly PnP, but you might as well give it a go. =) DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 5:34:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from logatome.francenet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 9AD5714DF0 for ; Wed, 12 Jan 2000 05:34:27 -0800 (PST) (envelope-from e-masson@kisoft-services.com) Received: from kisoft-services.com (pppA142.francenet.fr [193.149.100.52]) by logatome.francenet.fr (8.9.3/8.9.3) with ESMTP id OAA94813; Wed, 12 Jan 2000 14:34:17 +0100 (CET) Message-ID: <387C831E.2EEDD314@kisoft-services.com> Date: Wed, 12 Jan 2000 14:35:26 +0100 From: Eric Masson Organization: Kisoft Services X-Mailer: Mozilla 4.6 [fr] (WinNT; I) X-Accept-Language: fr MIME-Version: 1.0 To: lluisma Cc: stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory References: <387C6856.2FA1CB42@osi-technologies.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is a wellknown problem, http://www.freebsd.org/FAQ/troubleshoot.html. Just remove memory modules to have less than 64 Mo on your THINKPAD. It will boot fine after. Then create a custom kernel with MAXMEM keyword matching the exact amount of ram displayed by the 770 at startup (the lesser one). Replug your memory modules, that's done. MAXMEM is documented in LINT, if you do not know FBSD very well, read http://www.FreeBSD.org/handbook/kernelconfig.html For Laptop issues, you could subscribe to mobile@FreeBSD.org Regards. Eric Masson lluisma a écrit : > > I attempted to install 3.4 and it hangs after displaying "Probing PnP > devices...". I was able to install RedHat Linux 6.1 but it only > recognize 64MB memory instead of 256(I fixed this by adding > append="mem=255M" to lilo.conf). > > Any suggestions are highly appreciated. > > Regards, > LLU > > Linux version 2.2.12-20 (root@porky.devel.redhat.com) (gcc version > egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:40:35 > EDT 1999 > Detected 363963129 Hz processor. > Console: colour VGA+ 80x25 > Calibrating delay loop... 362.91 BogoMIPS > Memory: 256432k/261120k available (1008k kernel code, 412k reserved, > 2924k data, 64k init) > DENTRY hash table entries: 262144 (order: 9, 2097152 bytes) > Buffer-cache hash table entries: 262144 (order: 8, 1048576 bytes) > Page-cache hash table entries: 65536 (order: 6, 262144 bytes) > VFS: Diskquotas version dquot_6.4.0 initialized > CPU: Intel Mobile Pentium II stepping 0a > Checking 386/387 coupling... OK, FPU using exception 16 error reporting. > > Checking 'hlt' instruction... OK. > POSIX conformance testing by UNIFIX > mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au) > PCI: PCI BIOS revision 2.10 entry at 0xfd880 > PCI: Using configuration type 1 > PCI: Probing PCI hardware > Linux NET4.0 for Linux 2.2 > Based upon Swansea University Computer Society NET3.039 > NET4: Unix domain sockets 1.0 for Linux NET4.0. > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > TCP: Hash tables configured (ehash 262144 bhash 65536) > Initializing RT netlink socket > Starting kswapd v 1.5 > Detected PS/2 Mouse Port. > Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled > pty: 256 Unix98 ptys configured > apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) > Real Time Clock Driver v1.09 > RAM disk driver initialized: 16 RAM disks of 4096K size > PIIX4: IDE controller on PCI bus 00 dev 39 > PIIX4: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio > ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:DMA, hdd:pio > hda: IBM-DCYA-214000, ATA DISK drive > hdc: MATSHITADVD-ROM SR-8171, ATAPI CDROM drive > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > ide1 at 0x170-0x177,0x376 on irq 15 > hda: IBM-DCYA-214000, 7559MB w/420kB Cache, CHS=1023/240/63 > hdc: ATAPI 20X DVD-ROM drive, 512kB Cache > Uniform CDROM driver Revision: 2.56 > Floppy drive(s): fd0 is 1.44M > FDC 0 is a National Semiconductor PC87306 > md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 > raid5: measuring checksumming speed > raid5: MMX detected, trying high-speed MMX checksum routines > pII_mmx : 809.625 MB/sec > p5_mmx : 850.392 MB/sec > 8regs : 625.221 MB/sec > 32regs : 350.520 MB/sec > using fastest function: p5_mmx (850.392 MB/sec) > scsi : 0 hosts. > scsi : detected total. > md.c: sizeof(mdp_super_t) = 4096 > Partition check: > hda: hda1 hda2 < hda5 hda6 hda7 hda8 > > RAMDISK: Compressed image found at block 0 > autodetecting RAID arrays > autorun ... > ... autorun DONE. > VFS: Mounted root (ext2 filesystem). > autodetecting RAID arrays > autorun ... > ... autorun DONE. > VFS: Mounted root (ext2 filesystem) readonly. > change_root: old root has d_count=1 > Trying to unmount old root ... okay > Freeing unused kernel memory: 64k freed > Adding Swap: 529160k swap-space (priority -1) > Linux PCMCIA Card Services 3.0.14 > kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 > options: [pci] [cardbus] [apm] > Intel PCIC probe: > TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50103000, 2 sockets > host opts [0]: [ring] [pwr save] [isa irq] [no pci irq] [lat > 168/176] [bus 2/4] > host opts [1]: [ring] [pwr save] [isa irq] [no pci irq] [lat > 168/176] [bus 5/7] > ISA irqs (scanned) = 3,4,7,9,10 status change on irq 10 > cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef > cs: IO port probe 0x0100-0x04ff: excluding 0x130-0x137 0x200-0x207 > 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7 > cs: IO port probe 0x0a00-0x0aff: clean. > cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff > cs: memory probe 0x60000000-0x60ffffff: clean. > eth0: 3Com 3c589, io 0x300, irq 3, hw_addr 00:10:4B:EC:45:E4 > 8K FIFO split 5:3 Rx:Tx, auto xcvr > eth0: flipped to 10baseT > eth0: flipped to 10baseT > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Any opinions expressed above | Murphy's Law Corollary : are my own, not Kisoft's | Murphy was an optimist. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 6:12:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id AB56814F74 for ; Wed, 12 Jan 2000 06:12:21 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id JAA25092; Wed, 12 Jan 2000 09:12:14 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id JAA07056; Wed, 12 Jan 2000 09:12:12 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id JAA67493; Wed, 12 Jan 2000 09:12:12 -0500 (EST) Date: Wed, 12 Jan 2000 09:12:12 -0500 (EST) From: Thomas David Rivers Message-Id: <200001121412.JAA67493@lakes.dignus.com> To: lluisma@osi-technologies.com, rivers@dignus.com Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory Cc: stable@FreeBSD.ORG In-Reply-To: <387C6D49.24EE19FB@osi-technologies.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thomas David Rivers wrote: > > > Uh... you're talking about install Linux, right? Perhaps you > > I am trying to install FreeBSD 3.4. I was just displaying dmesg output > from a running Linux system because I attempted to replace Linux with > FreeBSD and the bsd install hangs after probing PnP devices. The dmesg > is just to show you what kind of laptop I have and see if someone can > give some ideas to make bsd install. I'm dying to have freebsd installed > on this laptop... Thanks for any help. Ah - my apologies... perhaps it was too early in the morning for me to be reading e-mail :-) Just to add a possible helpful point - I find my 3.2-RELEASE on my laptop will hang after a warm-boot (with a particular ethernet card installed.) Do you have any PCMCIA cards installed? If so, try 1) Doing a cold boot (turn the machine off) 2) Remove the cards and see if it comes up. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 6:44:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by hub.freebsd.org (Postfix) with ESMTP id 674AF1551B for ; Wed, 12 Jan 2000 06:44:36 -0800 (PST) (envelope-from mike@urgle.com) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 128P0g-0001G1-00; Wed, 12 Jan 2000 14:44:30 +0000 Date: Wed, 12 Jan 2000 14:44:30 +0000 From: Mike Bristow To: R Joseph Wright Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels Message-ID: <20000112144430.A4818@lindt.urgle.com> References: <387BF513.8A2D607E@nwlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387BF513.8A2D607E@nwlink.com>; from rjoseph@nwlink.com on Tue, Jan 11, 2000 at 07:29:23PM -0800 X-Rated: cryptographic, Cocaine Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 07:29:23PM -0800, R Joseph Wright wrote: > Which brings up the question that keeps nagging at me: How possible is > it to create a pc bios that is geared towards BSD/linux? This would > include its own lightweight repair shell. Couldn't this solve a lot of > problems with pc hardware, to have a unix-oriented bios? About the only thing that I really miss, going from `real' unix to pc unix is the ability to do _anything_ with a serial console. A bios that can do it's thang over the serial port exists. But it's not very common. -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 7:12:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.san.rr.com (ns1.san.rr.com [24.25.195.3]) by hub.freebsd.org (Postfix) with ESMTP id AFE2714E1E for ; Wed, 12 Jan 2000 07:12:44 -0800 (PST) (envelope-from erich@ucsd.edu) Received: from ucsd.edu ([24.30.148.224]) by ns2.san.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Wed, 12 Jan 2000 07:12:43 -0800 Message-ID: <387C99C9.1C57CC8E@ucsd.edu> Date: Wed, 12 Jan 2000 07:12:09 -0800 From: Eric Hedstrom X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Eric Masson Cc: lluisma , stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory References: <387C6856.2FA1CB42@osi-technologies.com> <387C831E.2EEDD314@kisoft-services.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you're right about what the problem is, but the solution will be a little trickier in this case--the 770Z has 128MB built in. Eric Eric Masson wrote: > > Hi, > > This is a wellknown problem, > http://www.freebsd.org/FAQ/troubleshoot.html. Just remove memory modules > to have less than 64 Mo on your THINKPAD. It will boot fine after. Then > create a custom kernel with MAXMEM keyword matching the exact amount of > ram displayed by the 770 at startup (the lesser one). Replug your memory > modules, that's done. > MAXMEM is documented in LINT, if you do not know FBSD very well, read > http://www.FreeBSD.org/handbook/kernelconfig.html > For Laptop issues, you could subscribe to mobile@FreeBSD.org > > Regards. > > Eric Masson > > lluisma a écrit : > > > > I attempted to install 3.4 and it hangs after displaying "Probing PnP > > devices...". I was able to install RedHat Linux 6.1 but it only > > recognize 64MB memory instead of 256(I fixed this by adding > > append="mem=255M" to lilo.conf). > > > > Any suggestions are highly appreciated. > > > > Regards, > > LLU > > > > Linux version 2.2.12-20 (root@porky.devel.redhat.com) (gcc version > > egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:40:35 > > EDT 1999 > > Detected 363963129 Hz processor. > > Console: colour VGA+ 80x25 > > Calibrating delay loop... 362.91 BogoMIPS > > Memory: 256432k/261120k available (1008k kernel code, 412k reserved, > > 2924k data, 64k init) > > DENTRY hash table entries: 262144 (order: 9, 2097152 bytes) > > Buffer-cache hash table entries: 262144 (order: 8, 1048576 bytes) > > Page-cache hash table entries: 65536 (order: 6, 262144 bytes) > > VFS: Diskquotas version dquot_6.4.0 initialized > > CPU: Intel Mobile Pentium II stepping 0a > > Checking 386/387 coupling... OK, FPU using exception 16 error reporting. > > > > Checking 'hlt' instruction... OK. > > POSIX conformance testing by UNIFIX > > mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au) > > PCI: PCI BIOS revision 2.10 entry at 0xfd880 > > PCI: Using configuration type 1 > > PCI: Probing PCI hardware > > Linux NET4.0 for Linux 2.2 > > Based upon Swansea University Computer Society NET3.039 > > NET4: Unix domain sockets 1.0 for Linux NET4.0. > > NET4: Linux TCP/IP 1.0 for NET4.0 > > IP Protocols: ICMP, UDP, TCP, IGMP > > TCP: Hash tables configured (ehash 262144 bhash 65536) > > Initializing RT netlink socket > > Starting kswapd v 1.5 > > Detected PS/2 Mouse Port. > > Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled > > pty: 256 Unix98 ptys configured > > apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) > > Real Time Clock Driver v1.09 > > RAM disk driver initialized: 16 RAM disks of 4096K size > > PIIX4: IDE controller on PCI bus 00 dev 39 > > PIIX4: not 100% native mode: will probe irqs later > > ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio > > ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:DMA, hdd:pio > > hda: IBM-DCYA-214000, ATA DISK drive > > hdc: MATSHITADVD-ROM SR-8171, ATAPI CDROM drive > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > ide1 at 0x170-0x177,0x376 on irq 15 > > hda: IBM-DCYA-214000, 7559MB w/420kB Cache, CHS=1023/240/63 > > hdc: ATAPI 20X DVD-ROM drive, 512kB Cache > > Uniform CDROM driver Revision: 2.56 > > Floppy drive(s): fd0 is 1.44M > > FDC 0 is a National Semiconductor PC87306 > > md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 > > raid5: measuring checksumming speed > > raid5: MMX detected, trying high-speed MMX checksum routines > > pII_mmx : 809.625 MB/sec > > p5_mmx : 850.392 MB/sec > > 8regs : 625.221 MB/sec > > 32regs : 350.520 MB/sec > > using fastest function: p5_mmx (850.392 MB/sec) > > scsi : 0 hosts. > > scsi : detected total. > > md.c: sizeof(mdp_super_t) = 4096 > > Partition check: > > hda: hda1 hda2 < hda5 hda6 hda7 hda8 > > > RAMDISK: Compressed image found at block 0 > > autodetecting RAID arrays > > autorun ... > > ... autorun DONE. > > VFS: Mounted root (ext2 filesystem). > > autodetecting RAID arrays > > autorun ... > > ... autorun DONE. > > VFS: Mounted root (ext2 filesystem) readonly. > > change_root: old root has d_count=1 > > Trying to unmount old root ... okay > > Freeing unused kernel memory: 64k freed > > Adding Swap: 529160k swap-space (priority -1) > > Linux PCMCIA Card Services 3.0.14 > > kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 > > options: [pci] [cardbus] [apm] > > Intel PCIC probe: > > TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50103000, 2 sockets > > host opts [0]: [ring] [pwr save] [isa irq] [no pci irq] [lat > > 168/176] [bus 2/4] > > host opts [1]: [ring] [pwr save] [isa irq] [no pci irq] [lat > > 168/176] [bus 5/7] > > ISA irqs (scanned) = 3,4,7,9,10 status change on irq 10 > > cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef > > cs: IO port probe 0x0100-0x04ff: excluding 0x130-0x137 0x200-0x207 > > 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7 > > cs: IO port probe 0x0a00-0x0aff: clean. > > cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff > > cs: memory probe 0x60000000-0x60ffffff: clean. > > eth0: 3Com 3c589, io 0x300, irq 3, hw_addr 00:10:4B:EC:45:E4 > > 8K FIFO split 5:3 Rx:Tx, auto xcvr > > eth0: flipped to 10baseT > > eth0: flipped to 10baseT > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > Any opinions expressed above | Murphy's Law Corollary : > are my own, not Kisoft's | Murphy was an optimist. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 7:25:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id F3C2B14E03 for ; Wed, 12 Jan 2000 07:25:23 -0800 (PST) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id KAA23825 for ; Wed, 12 Jan 2000 10:25:23 -0500 (EST) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id KAA07254 for stable@FreeBSD.ORG; Wed, 12 Jan 2000 10:25:22 -0500 (EST) Date: Wed, 12 Jan 2000 10:25:22 -0500 From: "Sean O'Connell" To: stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory Message-ID: <20000112102522.K6665@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: stable@FreeBSD.ORG References: <387C6856.2FA1CB42@osi-technologies.com> <387C831E.2EEDD314@kisoft-services.com> <387C99C9.1C57CC8E@ucsd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387C99C9.1C57CC8E@ucsd.edu>; from erich@ucsd.edu on Wed, Jan 12, 2000 at 07:12:09AM -0800 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000 Jan 12, Eric Hedstrom (aka erich@ucsd.edu) wrote: > I think you're right about what the problem is, but the solution will be a > little trickier in this case--the 770Z has 128MB built in. > What if you interrupt the boot process (hit a spacebar before the 10 seconds are up)... disk0s4a> set kern.vm.kmem.size=67108864 where 67108864 = 64*1024*1024. You could even err on the safe side and make it half that or 32MB. From /boot/defaults/loader.conf #kern.vm.kmem.size="" # Sets the size of kernel memory (bytes) Will that help? This is untried! S ----------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 7:28:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.polytechnic.edu.na (mail.polytechnic.edu.na [196.31.225.2]) by hub.freebsd.org (Postfix) with ESMTP id BB26A14FD0 for ; Wed, 12 Jan 2000 07:28:25 -0800 (PST) (envelope-from tim@polytechnic.edu.na) Received: from [196.31.225.199] (helo=polytechnic.edu.na) by mail.polytechnic.edu.na with esmtp (Exim 3.02 #2) id 128Rbv-0000AE-00 for stable@freebsd.org; Wed, 12 Jan 2000 15:31:07 -0200 Message-ID: <387C9DA3.F53FC917@polytechnic.edu.na> Date: Wed, 12 Jan 2000 17:28:35 +0200 From: Tim Priebe Reply-To: tim@polytechnic.edu.na Organization: Polytechnic of Namibia X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I think you're right about what the problem is, but the solution will be a >little trickier in this case--the 770Z has 128MB built in. Then build the custom kernel on a functioning system, compress it and copy it to your kernel boot floppy. Tim. >Eric >Eric Masson wrote: >> >> Hi, >> >> This is a wellknown problem, >> http://www.freebsd.org/FAQ/troubleshoot.html. Just remove memory modules > >to have less than 64 Mo on your THINKPAD. It will boot fine after. Then >> create a custom kernel with MAXMEM keyword matching the exact amount of >> ram displayed by the 770 at startup (the lesser one). Replug your memory >> modules, that's done. >> MAXMEM is documented in LINT, if you do not know FBSD very well, read >> http://www.FreeBSD.org/handbook/kernelconfig.html >> For Laptop issues, you could subscribe to mobile@FreeBSD.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 7:57:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (adsl-gte-la-216-86-200-115.mminternet.com [216.86.200.115]) by hub.freebsd.org (Postfix) with ESMTP id 47DA114DB8; Wed, 12 Jan 2000 07:57:07 -0800 (PST) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id HAA14302; Wed, 12 Jan 2000 07:57:17 -0800 (PST) (envelope-from boing) From: Geff Hanoian Message-Id: <200001121557.HAA14302@kusanagi.boing.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001120338.TAA03976@mass.cdrom.com> from Mike Smith at "Jan 11, 2000 7:38:24 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Wed, 12 Jan 2000 07:57:17 -0800 (PST) Cc: boing@boing.com, forrestc@iMach.com, msmith@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Of course, the ones which truly emulate an IDE drive at the hardware level > > > just work like an IDE drive, although slower on writes. > > > > > > The BIOS ones get tricky. Obviously, if the boot loader only uses bios > > > calls to do it's dirty work, these work well, at least through the boot > > > process. If the boot loader tries to access the hardware directly, and it > > > doesn't directly support the flash device, then the boot loader doesn't > > > work. Of course, this also applies to the OS. > > > > And that's assuming you could actually get a UFS partition on the "drive > > emulator thing"? But if you were only capable of loading files to a fat16, > > then wouldn't fbsdboot.exe (or whatever it's called) be necessary? > > No. > > Firstly, you are again raising a hypothetical question without actually > suggesting anything that might require this, so bear with me if I don't > take it too seriously. Things just don't really work like this. ^^^^^^^^^^^^^^^^^^^^^^ Honest, I don't mind. This is like, "hey mechanic dude, my breaks sometimes squeak, FIX IT!" Mechanic says, "They're fine now, I can't fix it." :) > > Thanks much! Excellent info. Geff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8: 0:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.monsterbymistake.com (monsterbymistake.com [205.207.163.17]) by hub.freebsd.org (Postfix) with ESMTP id 3BE671544C for ; Wed, 12 Jan 2000 08:00:33 -0800 (PST) (envelope-from drek@MonsterByMistake.Com) Received: from bunny.monsterbymistake.com([205.207.163.17]) (1324 bytes) by mail.monsterbymistake.com via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Wed, 12 Jan 2000 11:01:08 -0500 (EST) (Smail-3.2.0.107 1999-Sep-8 #1 built 1999-Sep-11) Date: Wed, 12 Jan 2000 11:01:08 -0500 (EST) From: Agent Drek To: freebsd-stable@freebsd.org Subject: access floppy rw to lock system Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: I have a repeatable problem on my FreeBSD-3.4Stable workstation. If the floppy disk is physically tabbed as read-only and I mount it rw I can then 'lock' the system up by using vim (to read a text-file on the disk ... less had the same problem). Is this expected behaviour? I did this from the console and could still between the virtual consoles. The only way to get going again was to reboot. After that happened twice I tabbed the disk writable and things were fine. FreeBSD smash 3.4-STABLE FreeBSD 3.4-STABLE #20: Mon Jan 10 12:14:18 EST 2000 root@smash:/usr/src/sys/compile/SMASH i386 I only think that this is a problem because this could have been my server at work. Sorry if this is just a result of my own ignorance. thanks, =derek Monster By Mistake Inc > 'digital plumber' http://www.interlog.com/~drek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8:26: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id E15FA14D3D; Wed, 12 Jan 2000 08:25:57 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA01240; Wed, 12 Jan 2000 08:25:07 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda01234; Wed Jan 12 08:24:51 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id IAA43640; Wed, 12 Jan 2000 08:24:50 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdS43637; Wed Jan 12 08:23:53 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id IAA04213; Wed, 12 Jan 2000 08:23:51 -0800 (PST) Message-Id: <200001121623.IAA04213@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdwT4209; Wed Jan 12 08:23:46 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Dag-Erling Smorgrav Cc: Cy Schubert - ITSD Open Systems Group , Brad Knowles , Holtor , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Kernel Option: TCP_DROP_SYNFIN In-reply-to: Your message of "12 Jan 2000 09:30:44 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 08:23:45 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: > Cy Schubert - ITSD Open Systems Group writes: > > In message , Dag-Erling Smorgrav > > writes: > > > It doesn't have anything to do with syn floods at all. It merely > > > prevents OS fingerprinting (at least the way nmap does it). > > The following ipfw rule will also prevent OS fingerprinting. > > > > deny log tcp from any to any in tcpflg fin,syn > > It does precisely the same thing as TCP_DROP_SYNFIN, except much slower. And it would log the event. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8:31:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id CBFED154EB; Wed, 12 Jan 2000 08:30:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA02268; Wed, 12 Jan 2000 08:37:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001121637.IAA02268@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Courtney Thomas Cc: Mike Smith , Anton , Max Khon , freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Wed, 12 Jan 2000 05:18:29 EST." <387C54F5.167EB0E7@access1.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 08:37:47 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Greetings ! > > What would be the best reference(es) [on/off web] describing said > process(es) ? If you're referring to the booting and running of FreeBSD, you would want to start with the source code. > Thanks, > > Courtney > > <--------------------------------------------------------------- > > > > > Mike Smith wrote: > > > > The ability to load and start a kernel != the ability to boot and run > > same. > > > > You cannot boot and run FreeBSD once DOS has been booted on the system. > > You should give up now before you waste any more of your or our time. > > > > There are good technical reasons why this is the case. If you don't > > understand them, please trust those of us that do. > > > > Thankyou. > > > > > hello. > > > > > > On Wed, 12 Jan 2000, Max Khon wrote: > > > > > > > ftp://iclub.nsu.ru/pub/FreeBSD/incoming/fbsdboot.exe > > > > I have not tested it. Tell me if it works or not. > > > > > > it can boot elf cernels, but i have: > > > > > > no init > > > panic: no init > > > > > > rebooting at N seconds... > > > > > > maybe i must specify root device? but how? > > > i dont remember such problems with old fbsdboot.exe > > > (or it's kernel's problem?) > > > > > > anton. > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > -- > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8:40:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id C5C1014E33 for ; Wed, 12 Jan 2000 08:40:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA02338; Wed, 12 Jan 2000 08:46:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001121646.IAA02338@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Bristow Cc: R Joseph Wright , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Wed, 12 Jan 2000 14:44:30 GMT." <20000112144430.A4818@lindt.urgle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 08:46:28 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Jan 11, 2000 at 07:29:23PM -0800, R Joseph Wright wrote: > > Which brings up the question that keeps nagging at me: How possible is > > it to create a pc bios that is geared towards BSD/linux? This would > > include its own lightweight repair shell. Couldn't this solve a lot of > > problems with pc hardware, to have a unix-oriented bios? > > About the only thing that I really miss, going from `real' unix to > pc unix is the ability to do _anything_ with a serial console. > > A bios that can do it's thang over the serial port exists. But it's > not very common. www.realweasel.com ... although they've been "almost shipping" for months now. If you work out how to buy one, please let us all know. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8:43:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 6BC2515538 for ; Wed, 12 Jan 2000 08:43:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA02361; Wed, 12 Jan 2000 08:50:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001121650.IAA02361@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Sean O'Connell" Cc: stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-reply-to: Your message of "Wed, 12 Jan 2000 10:25:22 EST." <20000112102522.K6665@stat.Duke.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 08:50:16 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 2000 Jan 12, Eric Hedstrom (aka erich@ucsd.edu) wrote: > > I think you're right about what the problem is, but the solution will be a > > little trickier in this case--the 770Z has 128MB built in. > > > > What if you interrupt the boot process (hit a spacebar before > the 10 seconds are up)... > > disk0s4a> set kern.vm.kmem.size=67108864 > > where 67108864 = 64*1024*1024. You could even err on the safe side > and make it half that or 32MB. > > >From /boot/defaults/loader.conf > > #kern.vm.kmem.size="" # Sets the size of kernel memory (bytes) > > Will that help? This is untried! One problem is that with > 64MB in the system, the speculative memory probing performed by 3.x and older systems tends to kill the Thinkpad architecture dead (bad design!). I don't _think_ that this is the problem, however. The PnP probe happens at a different stage, and I suspect that this is some other, new form of brokenness. It would be very interesting if the original poster were to try a 4.0 snapshot on this machine. Note that I _have_ seen 3.x running on various thinkpad 770s, but not the Z. IBM were never able to ship me one, so I never got to fight with it either. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8:43:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from diarmadhi.mushhaven.net (diarmadhi.mushhaven.net [63.75.111.197]) by hub.freebsd.org (Postfix) with ESMTP id 047EE14D3D; Wed, 12 Jan 2000 08:43:48 -0800 (PST) (envelope-from mistwolf@diarmadhi.mushhaven.net) Received: (from mistwolf@localhost) by diarmadhi.mushhaven.net (8.9.3/8.9.3) id IAA17428; Wed, 12 Jan 2000 08:42:09 -0800 (PST) (envelope-from mistwolf) Date: Wed, 12 Jan 2000 08:42:09 -0800 From: Jamie Norwood To: Mike Smith Cc: Mike Bristow , R Joseph Wright , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels Message-ID: <20000112084209.A17390@mushhaven.net> References: <20000112144430.A4818@lindt.urgle.com> <200001121646.IAA02338@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200001121646.IAA02338@mass.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I mailed them in early december about this, and got: --- > A friend gave me the link. What is the ETA on being able to get my > paws on one? What is the estimated MSRP on them? Any chance there will > be an rj45 model, or a model with both db15 and rj45? :) 1. Available now in limited quantities due to flash having gone on allocation. 2. $250 US. 3. The RS-232 is on a DB-9P. By "RJ-45" do you mean "RS-232 on an RJ-45" or "ethernet on an RJ-45"? Jonathan --- YMMV. :) Jamie On Wed, Jan 12, 2000 at 08:46:28AM -0800, Mike Smith wrote: > > On Tue, Jan 11, 2000 at 07:29:23PM -0800, R Joseph Wright wrote: > > > Which brings up the question that keeps nagging at me: How possible is > > > it to create a pc bios that is geared towards BSD/linux? This would > > > include its own lightweight repair shell. Couldn't this solve a lot of > > > problems with pc hardware, to have a unix-oriented bios? > > > > About the only thing that I really miss, going from `real' unix to > > pc unix is the ability to do _anything_ with a serial console. > > > > A bios that can do it's thang over the serial port exists. But it's > > not very common. > > www.realweasel.com > > ... although they've been "almost shipping" for months now. If you work > out how to buy one, please let us all know. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8:46:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 09CC814D70 for ; Wed, 12 Jan 2000 08:46:37 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id JAA21577; Wed, 12 Jan 2000 09:46:36 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA04479; Wed, 12 Jan 2000 09:46:35 -0700 Date: Wed, 12 Jan 2000 09:46:35 -0700 Message-Id: <200001121646.JAA04479@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Sean O'Connell" Cc: stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-Reply-To: <20000112102522.K6665@stat.Duke.EDU> References: <387C6856.2FA1CB42@osi-technologies.com> <387C831E.2EEDD314@kisoft-services.com> <387C99C9.1C57CC8E@ucsd.edu> <20000112102522.K6665@stat.Duke.EDU> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think you're right about what the problem is, but the solution will be a > > little trickier in this case--the 770Z has 128MB built in. > > > > What if you interrupt the boot process (hit a spacebar before > the 10 seconds are up)... > > disk0s4a> set kern.vm.kmem.size=67108864 This is set too late in the boot process, since it's after the memory sizing has been done. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 8:50:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 2B79015593 for ; Wed, 12 Jan 2000 08:50:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA02419; Wed, 12 Jan 2000 08:57:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001121657.IAA02419@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@mt.sri.com (Nate Williams) Cc: "Sean O'Connell" , stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-reply-to: Your message of "Wed, 12 Jan 2000 09:46:35 MST." <200001121646.JAA04479@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 08:57:32 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think you're right about what the problem is, but the solution will be a > > > little trickier in this case--the 770Z has 128MB built in. > > > > > > > What if you interrupt the boot process (hit a spacebar before > > the 10 seconds are up)... > > > > disk0s4a> set kern.vm.kmem.size=67108864 > > This is set too late in the boot process, since it's after the memory > sizing has been done. That's correct; you want hw.physmem, but in 4.x where that's available the memory probe itself has been improved to the point where it's not typically necessary to set it... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9: 6:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybercable.tm.fr (mail.cybercable.tm.fr [195.132.0.194]) by hub.freebsd.org (Postfix) with SMTP id 9922B15109 for ; Wed, 12 Jan 2000 09:06:19 -0800 (PST) (envelope-from dbera@cybercable.tm.fr) Received: (qmail 6264879 invoked by uid 502); 12 Jan 2000 16:12:21 -0000 Received: from r22m148.cybercable.tm.fr (HELO cybercable.tm.fr) (195.132.22.148) by mail.cybercable.tm.fr with SMTP; 12 Jan 2000 16:12:21 -0000 Message-ID: <387CA734.277B44D5@cybercable.tm.fr> Date: Wed, 12 Jan 2000 17:09:24 +0100 From: David Berard X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: parallel printer & nlpt0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody, I upgrade my system from freebsd 2.X to freebsd 3.X stable of yesterday, since this, my printer (HP LaserJet 6L) stop working correctly with big files (no txt files). For example, if I try to print one of the postscript examples (tiger.ps) from de ghostscript port (gs 5.50), I obtain more or less the picture, but with some incorrect lines, and some garbages (cabalistic characters), and sometime unattended formfeed. I think lpt0 (ex nlpt0 device) is the problem, because if I change in the BIOS the mode of the parallel port (SPP, EPP 1.7, EPP 1.9, EPP+ECP), I don't obtain the same results. I also try to play with the flags of ppc device in the kernel config file, but with no luck. My motherboard is a QDI Legend V (Intel 440LX chipset). I try to compile a kernel with the olpt0 driver, but the compilation fail... I have no problem with freebsd 2.X, and linux. Do you have any suggestion ? Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9: 7:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by hub.freebsd.org (Postfix) with ESMTP id 5531F154EC; Wed, 12 Jan 2000 09:07:10 -0800 (PST) (envelope-from mike@urgle.com) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 128REe-0001KI-00; Wed, 12 Jan 2000 17:07:04 +0000 Date: Wed, 12 Jan 2000 17:07:04 +0000 From: Mike Bristow To: Mike Smith Cc: R Joseph Wright , freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels Message-ID: <20000112170704.A5073@lindt.urgle.com> References: <20000112144430.A4818@lindt.urgle.com> <200001121646.IAA02338@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001121646.IAA02338@mass.cdrom.com>; from msmith@freebsd.org on Wed, Jan 12, 2000 at 08:46:28AM -0800 X-Rated: paedophile, FBI Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 08:46:28AM -0800, Mike Smith wrote: > > On Tue, Jan 11, 2000 at 07:29:23PM -0800, R Joseph Wright wrote: > > > Which brings up the question that keeps nagging at me: How possible is > > > it to create a pc bios that is geared towards BSD/linux? This would > > > include its own lightweight repair shell. Couldn't this solve a lot of > > > problems with pc hardware, to have a unix-oriented bios? > > > > About the only thing that I really miss, going from `real' unix to > > pc unix is the ability to do _anything_ with a serial console. > > > > A bios that can do it's thang over the serial port exists. But it's > > not very common. > > www.realweasel.com It's a very clever hack. I admire them for it. Doesn't stop it being an 'orrible hack. [ for those that haven't seen them, a board that looks to the BIOS like a MGA adapter but can throw the data out of the serial port instead ] I still maintain that the /right/ solution is for the BIOS to have a ``while booting shovel data out COM1 and accept data from COM1 as if it were my keyboard'' option. I've seen them on (I think) NCR boxes. -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9:14:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from logatome.francenet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 94D3515496 for ; Wed, 12 Jan 2000 09:14:32 -0800 (PST) (envelope-from e-masson@kisoft-services.com) Received: from kisoft-services.com (pppA269.francenet.fr [193.149.100.179]) by logatome.francenet.fr (8.9.3/8.9.3) with ESMTP id SAA76695; Wed, 12 Jan 2000 18:14:13 +0100 (CET) Message-ID: <387CB671.819CADB8@kisoft-services.com> Date: Wed, 12 Jan 2000 18:14:25 +0100 From: Eric Masson Organization: Kisoft Services X-Mailer: Mozilla 4.6 [fr] (WinNT; I) X-Accept-Language: fr MIME-Version: 1.0 To: Eric Hedstrom Cc: lluisma , stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory References: <387C6856.2FA1CB42@osi-technologies.com> <387C831E.2EEDD314@kisoft-services.com> <387C99C9.1C57CC8E@ucsd.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Hedstrom a écrit : > > I think you're right about what the problem is, but the solution will be a > little trickier in this case--the 770Z has 128MB built in. > > Eric > > Eric Masson wrote: > > > > Hi, > > > > This is a wellknown problem, > > http://www.freebsd.org/FAQ/troubleshoot.html. Just remove memory modules > > to have less than 64 Mo on your THINKPAD. It will boot fine after. Then > > create a custom kernel with MAXMEM keyword matching the exact amount of > > ram displayed by the 770 at startup (the lesser one). Replug your memory > > modules, that's done. > > MAXMEM is documented in LINT, if you do not know FBSD very well, read > > http://www.FreeBSD.org/handbook/kernelconfig.html > > For Laptop issues, you could subscribe to mobile@FreeBSD.org > > > > Regards. > > > > Eric Masson > > > > lluisma a écrit : > > > > > > I attempted to install 3.4 and it hangs after displaying "Probing PnP > > > devices...". I was able to install RedHat Linux 6.1 but it only > > > recognize 64MB memory instead of 256(I fixed this by adding > > > append="mem=255M" to lilo.conf). > > > > > > Any suggestions are highly appreciated. > > > > > > Regards, > > > LLU > > > > > > Linux version 2.2.12-20 (root@porky.devel.redhat.com) (gcc version > > > egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:40:35 > > > EDT 1999 > > > Detected 363963129 Hz processor. > > > Console: colour VGA+ 80x25 > > > Calibrating delay loop... 362.91 BogoMIPS > > > Memory: 256432k/261120k available (1008k kernel code, 412k reserved, > > > 2924k data, 64k init) > > > DENTRY hash table entries: 262144 (order: 9, 2097152 bytes) > > > Buffer-cache hash table entries: 262144 (order: 8, 1048576 bytes) > > > Page-cache hash table entries: 65536 (order: 6, 262144 bytes) > > > VFS: Diskquotas version dquot_6.4.0 initialized > > > CPU: Intel Mobile Pentium II stepping 0a > > > Checking 386/387 coupling... OK, FPU using exception 16 error reporting. > > > > > > Checking 'hlt' instruction... OK. > > > POSIX conformance testing by UNIFIX > > > mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au) > > > PCI: PCI BIOS revision 2.10 entry at 0xfd880 > > > PCI: Using configuration type 1 > > > PCI: Probing PCI hardware > > > Linux NET4.0 for Linux 2.2 > > > Based upon Swansea University Computer Society NET3.039 > > > NET4: Unix domain sockets 1.0 for Linux NET4.0. > > > NET4: Linux TCP/IP 1.0 for NET4.0 > > > IP Protocols: ICMP, UDP, TCP, IGMP > > > TCP: Hash tables configured (ehash 262144 bhash 65536) > > > Initializing RT netlink socket > > > Starting kswapd v 1.5 > > > Detected PS/2 Mouse Port. > > > Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled > > > pty: 256 Unix98 ptys configured > > > apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) > > > Real Time Clock Driver v1.09 > > > RAM disk driver initialized: 16 RAM disks of 4096K size > > > PIIX4: IDE controller on PCI bus 00 dev 39 > > > PIIX4: not 100% native mode: will probe irqs later > > > ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio > > > ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:DMA, hdd:pio > > > hda: IBM-DCYA-214000, ATA DISK drive > > > hdc: MATSHITADVD-ROM SR-8171, ATAPI CDROM drive > > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > > ide1 at 0x170-0x177,0x376 on irq 15 > > > hda: IBM-DCYA-214000, 7559MB w/420kB Cache, CHS=1023/240/63 > > > hdc: ATAPI 20X DVD-ROM drive, 512kB Cache > > > Uniform CDROM driver Revision: 2.56 > > > Floppy drive(s): fd0 is 1.44M > > > FDC 0 is a National Semiconductor PC87306 > > > md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 > > > raid5: measuring checksumming speed > > > raid5: MMX detected, trying high-speed MMX checksum routines > > > pII_mmx : 809.625 MB/sec > > > p5_mmx : 850.392 MB/sec > > > 8regs : 625.221 MB/sec > > > 32regs : 350.520 MB/sec > > > using fastest function: p5_mmx (850.392 MB/sec) > > > scsi : 0 hosts. > > > scsi : detected total. > > > md.c: sizeof(mdp_super_t) = 4096 > > > Partition check: > > > hda: hda1 hda2 < hda5 hda6 hda7 hda8 > > > > RAMDISK: Compressed image found at block 0 > > > autodetecting RAID arrays > > > autorun ... > > > ... autorun DONE. > > > VFS: Mounted root (ext2 filesystem). > > > autodetecting RAID arrays > > > autorun ... > > > ... autorun DONE. > > > VFS: Mounted root (ext2 filesystem) readonly. > > > change_root: old root has d_count=1 > > > Trying to unmount old root ... okay > > > Freeing unused kernel memory: 64k freed > > > Adding Swap: 529160k swap-space (priority -1) > > > Linux PCMCIA Card Services 3.0.14 > > > kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 > > > options: [pci] [cardbus] [apm] > > > Intel PCIC probe: > > > TI 1251A PCI-to-CardBus at bus 0 slot 2, mem 0x50103000, 2 sockets > > > host opts [0]: [ring] [pwr save] [isa irq] [no pci irq] [lat > > > 168/176] [bus 2/4] > > > host opts [1]: [ring] [pwr save] [isa irq] [no pci irq] [lat > > > 168/176] [bus 5/7] > > > ISA irqs (scanned) = 3,4,7,9,10 status change on irq 10 > > > cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef > > > cs: IO port probe 0x0100-0x04ff: excluding 0x130-0x137 0x200-0x207 > > > 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7 > > > cs: IO port probe 0x0a00-0x0aff: clean. > > > cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff > > > cs: memory probe 0x60000000-0x60ffffff: clean. > > > eth0: 3Com 3c589, io 0x300, irq 3, hw_addr 00:10:4B:EC:45:E4 > > > 8K FIFO split 5:3 Rx:Tx, auto xcvr > > > eth0: flipped to 10baseT > > > eth0: flipped to 10baseT > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > > Any opinions expressed above | Murphy's Law Corollary : > > are my own, not Kisoft's | Murphy was an optimist. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message Hi, He shouldn't have bought a rich people laptop :). The solution has been given later, in this thread : build the kernel on another machine, compress it and put it on the boot disk. One more point, Thinkpads seem to need that MAXMEM is set to total RAM amount less 1 Megabyte. Regards. Eric -- Any opinions expressed above | Murphy's Law Corollary : are my own, not Kisoft's | Murphy was an optimist. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9:16: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id 11537155E5 for ; Wed, 12 Jan 2000 09:15:58 -0800 (PST) (envelope-from darcy@ok-connect.com) Received: (qmail 7387 invoked from network); 12 Jan 2000 17:15:53 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 12 Jan 2000 17:15:53 -0000 Message-Id: <3.0.32.20000112091713.015822a0@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 12 Jan 2000 09:17:14 +0000 To: freebsd-stable@freebsd.org From: Darcy Buskermolen Subject: Re: fbsdboot.exe can't load elf kernels Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:07 PM 1/12/00 +0000, you wrote: >On Wed, Jan 12, 2000 at 08:46:28AM -0800, Mike Smith wrote: >> > On Tue, Jan 11, 2000 at 07:29:23PM -0800, R Joseph Wright wrote: >> > > Which brings up the question that keeps nagging at me: How possible is >> > > it to create a pc bios that is geared towards BSD/linux? This would >> > > include its own lightweight repair shell. Couldn't this solve a lot of >> > > problems with pc hardware, to have a unix-oriented bios? >> > >> > About the only thing that I really miss, going from `real' unix to >> > pc unix is the ability to do _anything_ with a serial console. >> > >> > A bios that can do it's thang over the serial port exists. But it's >> > not very common. >> >> www.realweasel.com > >It's a very clever hack. I admire them for it. Doesn't stop it >being an 'orrible hack. > >[ for those that haven't seen them, a board that looks to the BIOS like > a MGA adapter but can throw the data out of the serial port instead ] > >I still maintain that the /right/ solution is for the BIOS to have >a ``while booting shovel data out COM1 and accept data from COM1 as if >it were my keyboard'' option. > >I've seen them on (I think) NCR boxes. Intel Server class machines also have that ability. Motherboards such as the L440GX+ Mother board have this as an option in the BIOS. > >-- >Mike Bristow, Geek At Large ``Beware of Invisible Cows'' > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9:23:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id D8EC615516 for ; Wed, 12 Jan 2000 09:23:11 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 0150AE89D; Wed, 12 Jan 2000 12:23:09 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id MAA02389; Wed, 12 Jan 2000 12:23:09 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14460.47229.719563.931246@onceler.kcilink.com> Date: Wed, 12 Jan 2000 12:23:09 -0500 (EST) To: David Berard Cc: freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 In-Reply-To: <387CA734.277B44D5@cybercable.tm.fr> References: <387CA734.277B44D5@cybercable.tm.fr> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DB" == David Berard writes: DB> Hello everybody, DB> I upgrade my system from freebsd 2.X to freebsd 3.X stable of yesterday, DB> since this, my DB> printer (HP LaserJet 6L) stop working correctly with big files (no txt DB> files). Same problem for me with a HP LJ4m. The only thing that fixed it was "lptcontrol -s" (or -p) to go into standard polled mode. I too believe the lpt0 device is not working properly. This was tested on two separate machines, one of which worked flawlessly with the lp0 printer device under BSD/OS with interrupts enabled. My question is will making lpt0 use polled mode interfere with my parallel port ZIP drive using interrupts? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9:32:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 9449214E39; Wed, 12 Jan 2000 09:32:52 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA02551; Wed, 12 Jan 2000 09:39:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001121739.JAA02551@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Bristow Cc: Mike Smith , R Joseph Wright , freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Wed, 12 Jan 2000 17:07:04 GMT." <20000112170704.A5073@lindt.urgle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 09:39:31 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I still maintain that the /right/ solution is for the BIOS to have > a ``while booting shovel data out COM1 and accept data from COM1 as if > it were my keyboard'' option. > > I've seen them on (I think) NCR boxes. Intel do this on their server boxes, to the extent that if you have a colour ANSI terminal you can run fullscreen expansion BIOS tools like eg. Adaptec's. I'm reasonably sure that it's just an extra-price option from the major BIOS vendors. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9:42: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B157315523 for ; Wed, 12 Jan 2000 09:42:03 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA28900; Wed, 12 Jan 2000 09:41:46 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001121741.JAA28900@gndrsh.dnsmgr.net> Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-Reply-To: <387C99C9.1C57CC8E@ucsd.edu> from Eric Hedstrom at "Jan 12, 2000 07:12:09 am" To: erich@ucsd.edu (Eric Hedstrom) Date: Wed, 12 Jan 2000 09:41:45 -0800 (PST) Cc: e-masson@kisoft-services.com (Eric Masson), lluisma@osi-technologies.com (lluisma), stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset iso-8859-1 unsupported, filtering to ASCII...] > I think you're right about what the problem is, but the solution will be a > little trickier in this case--the 770Z has 128MB built in. Use the npx0 hack, boot -c and set the iosiz of npx0 to 65536, which should cause the machine to come up thinking it has 64M. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9:56: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 778B0154A5; Wed, 12 Jan 2000 09:56:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA40618; Wed, 12 Jan 2000 10:55:56 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA15257; Wed, 12 Jan 2000 10:56:14 -0700 (MST) Message-Id: <200001121756.KAA15257@harmony.village.org> To: "Forrest W. Christian" Subject: Re: fbsdboot.exe can't load elf kernels Cc: Mike Smith , Geff Hanoian , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Jan 2000 22:41:45 MST." References: Date: Wed, 12 Jan 2000 10:56:14 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Forrest W. Christian" writes: : I agree with your statement in general. However, in the "truly" embedded : PC world, the most popular off-the-shelf Flash Disk solution (M-Systems : DiskOnChip-Millenium) is actually of this type. However, this solution : also provides native drivers for Windows and a whole host of other OS'es. : If there isn't a FreeBSD driver available, expect one from me in a few : weeks. I've been using phk's fla driver for these things for about 4 months now (give or take) and have found that it works really well. I have FreeBSD running on a board that is approx 2"x2"x3/8" with one of these things. The base OS takes about 15M right now, but I haven't tried to do anything that put a minimal number of files on the device. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 9:58:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 08FDB154F3; Wed, 12 Jan 2000 09:58:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA40632; Wed, 12 Jan 2000 10:58:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA15284; Wed, 12 Jan 2000 10:58:59 -0700 (MST) Message-Id: <200001121758.KAA15284@harmony.village.org> To: Marcin Cieslak Subject: Re: fbsdboot.exe can't load elf kernels (flash cards off topic) Cc: "Forrest W. Christian" , Mike Smith , Geff Hanoian , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 Jan 2000 10:11:40 +0100." References: Date: Wed, 12 Jan 2000 10:58:59 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Marcin Cieslak writes: : Once there I managed to read a flash card containing Cisco IOS : (it was M-Systems - or other manufacturer). However, the flash : was one of linear types - just plain of bytes, and no wd/ata emulation. : pccardd from PAO (3.2 then I guess) of course didn't detect : nor load the driver, but I read this using pccardc without any problem : (all filesystem structure, very simple at the moment and file contents). : I guess that some special operation would be required to program : the flash, but... Actually, I've toyed with the diea of adding support for the linear FLASH pccards. I have several, but no time to even think about this sort of project. The linear flash cards don't have an ata interface, so PAO and soon -current won't recognize them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 10: 3:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1D383154A5; Wed, 12 Jan 2000 10:03:42 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA28991; Wed, 12 Jan 2000 10:03:41 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001121803.KAA28991@gndrsh.dnsmgr.net> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001121739.JAA02551@mass.cdrom.com> from Mike Smith at "Jan 12, 2000 09:39:31 am" To: msmith@FreeBSD.ORG (Mike Smith) Date: Wed, 12 Jan 2000 10:03:40 -0800 (PST) Cc: mike@urgle.com (Mike Bristow), rjoseph@nwlink.com (R Joseph Wright), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I still maintain that the /right/ solution is for the BIOS to have > > a ``while booting shovel data out COM1 and accept data from COM1 as if > > it were my keyboard'' option. > > > > I've seen them on (I think) NCR boxes. > > Intel do this on their server boxes, to the extent that if you have a > colour ANSI terminal you can run fullscreen expansion BIOS tools like eg. > Adaptec's. I'm reasonably sure that it's just an extra-price option from > the major BIOS vendors. And the Intel BIOS code was written by a FreeBSD user, and some times hacker... who now and again shows up on the mailling lists... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 10:18:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 5792315045 for ; Wed, 12 Jan 2000 10:18:03 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id LAA22553; Wed, 12 Jan 2000 11:17:49 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA05163; Wed, 12 Jan 2000 11:17:47 -0700 Date: Wed, 12 Jan 2000 11:17:47 -0700 Message-Id: <200001121817.LAA05163@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Rodney W. Grimes" Cc: erich@ucsd.edu (Eric Hedstrom), e-masson@kisoft-services.com (Eric Masson), lluisma@osi-technologies.com (lluisma), stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-Reply-To: <200001121741.JAA28900@gndrsh.dnsmgr.net> References: <387C99C9.1C57CC8E@ucsd.edu> <200001121741.JAA28900@gndrsh.dnsmgr.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [Charset iso-8859-1 unsupported, filtering to ASCII...] > > I think you're right about what the problem is, but the solution will be a > > little trickier in this case--the 770Z has 128MB built in. > > Use the npx0 hack, boot -c and set the iosiz of npx0 to 65536, which > should cause the machine to come up thinking it has 64M. See previous email, where I mentioned this happens too late in the boot process. This *would* cause the next bootup to have the smaller amount *IF* this information was saved, but on the boo floppy it is not. However, this does not help on the boot floppy, since it's going to use the probed amount. (And yes, I have verified that this is indeed the case on my ThinkPad, and attempted the exact same thing Rod mentioned above.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 10:35:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 8807D14CAF for ; Wed, 12 Jan 2000 10:35:06 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA29110; Wed, 12 Jan 2000 10:34:27 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001121834.KAA29110@gndrsh.dnsmgr.net> Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-Reply-To: <200001121817.LAA05163@mt.sri.com> from Nate Williams at "Jan 12, 2000 11:17:47 am" To: nate@mt.sri.com (Nate Williams) Date: Wed, 12 Jan 2000 10:34:27 -0800 (PST) Cc: erich@ucsd.edu (Eric Hedstrom), e-masson@kisoft-services.com (Eric Masson), lluisma@osi-technologies.com (lluisma), stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [Charset iso-8859-1 unsupported, filtering to ASCII...] > > > I think you're right about what the problem is, but the solution will be a > > > little trickier in this case--the 770Z has 128MB built in. > > > > Use the npx0 hack, boot -c and set the iosiz of npx0 to 65536, which > > should cause the machine to come up thinking it has 64M. > > See previous email, where I mentioned this happens too late in the boot > process. This *would* cause the next bootup to have the smaller amount > *IF* this information was saved, but on the boo floppy it is not. No, this one is not too late. This actually effects sys/i386/i386/machdep.c, seach that file for NNPX to see how... > However, this does not help on the boot floppy, since it's going to use > the probed amount. > > (And yes, I have verified that this is indeed the case on my ThinkPad, > and attempted the exact same thing Rod mentioned above.) Then someone has borked the code. Note, that this hack occurs AFTER the printf() for memory size, so it is not visible in dmesg, so don't trust dmesg when using this hack. Perhaps you should add a printf inside the NNPX to prove it to yourself... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 10:35:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 94C681556E for ; Wed, 12 Jan 2000 10:35:48 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA29119; Wed, 12 Jan 2000 10:35:27 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001121835.KAA29119@gndrsh.dnsmgr.net> Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-Reply-To: <200001121817.LAA05163@mt.sri.com> from Nate Williams at "Jan 12, 2000 11:17:47 am" To: nate@mt.sri.com (Nate Williams) Date: Wed, 12 Jan 2000 10:35:26 -0800 (PST) Cc: erich@ucsd.edu (Eric Hedstrom), e-masson@kisoft-services.com (Eric Masson), lluisma@osi-technologies.com (lluisma), stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [Charset iso-8859-1 unsupported, filtering to ASCII...] > > > I think you're right about what the problem is, but the solution will be a > > > little trickier in this case--the 770Z has 128MB built in. > > > > Use the npx0 hack, boot -c and set the iosiz of npx0 to 65536, which > > should cause the machine to come up thinking it has 64M. Arrghhh... it isn't iosiz, its msize, I read the comments in LINT instead of the code in machdep.c and trusted them :-(. > See previous email, where I mentioned this happens too late in the boot > process. This *would* cause the next bootup to have the smaller amount > *IF* this information was saved, but on the boo floppy it is not. > > However, this does not help on the boot floppy, since it's going to use > the probed amount. > > (And yes, I have verified that this is indeed the case on my ThinkPad, > and attempted the exact same thing Rod mentioned above.) > > > > Nate > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 12:17:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.gmx.net (mail1.gmx.net [194.221.183.61]) by hub.freebsd.org (Postfix) with SMTP id C511314F21 for ; Wed, 12 Jan 2000 12:17:31 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 30173 invoked by uid 0); 12 Jan 2000 20:17:26 -0000 Received: from p3e9e7a4f.dip.t-dialin.net (HELO speedy.gsinet) (62.158.122.79) by mail1.gmx.net with SMTP; 12 Jan 2000 20:17:26 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id UAA09601 for freebsd-stable@freebsd.org; Wed, 12 Jan 2000 20:37:27 +0100 Date: Wed, 12 Jan 2000 20:37:27 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels Message-ID: <20000112203727.G7734@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <200001120828.AAA00633@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001120828.AAA00633@mass.cdrom.com>; from msmith@freebsd.org on Wed, Jan 12, 2000 at 12:28:20AM -0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 12, 2000 at 00:28 -0800, Mike Smith wrote: > > The ability to load and start a kernel != the ability to boot > and run same. > > You cannot boot and run FreeBSD once DOS has been booted on the > system. You should give up now before you waste any more of > your or our time. Sorry for butting in, but ... What's that bad about pure(!) DOS running in an early stage? To make it clear: I'm NOT talking about "memory managers" running already, having scrambled descriptor tables or enabling i386 features (like virtual mode or special CPU's management features). I sometimes liked to have a config.sys boot menu allowing for less experienced users (or even the experienced but lazy ones:) to have a description and choose by aim and shoot besides having a fallback config at timeout and a textual configuration which can be adjusted by ANY system running on this particular machine (to add choices, to change defaults, etc). And I remember some hardware which had to see its DOS driver for downloading images, doing nasty port access magic to enable compatibility modes, activating certain features or doing configuration another OS doesn't know about, etc. Without this driver being run the hardware is outright unusable. (You might call it broken hardware, but I DID have such stuff like a CMD640B based EIDE controller in an Asus SP3 which was quite problematic back in 1995. And I remember some sound cards needing their DOS driver to configure and enable them, i.e. make them look like a SoundBlaster and have it unlocked. And I could think of NIC clones needing some sort of pushing to look like their idol.) To cut it short: I ALWAYS appreciate a boot loader which works from DOS, since the "native" loaders coming with the separate OSes might not always fit or cope with the hardware or its configuration. To get this one more concrete (and please don't take this as a rejection "your software doesn't work for me" -- it's just "suboptimal" and "less comfortable as other systems are for me"): FreeBSD is unable to boot from my usual workstation's JAZ since it's the third SCSI drive on the machine. So I had to move to a different computer for trying out FBSD. This keeps me from using some of the workstation's special hardware and from comparing FreeBSD to the other systems which are on the machine. Installing on the spare machine I'm always caught by the aha1510 being unsupported since CAM has been introduced in 3.0(?). So I cannot access the CDROM drive and have to do a network install. If only I wouldn't have these little problems with the NICs I tried in this machine. And it's slow and old (I guess that's why it's available to "play with" :) I think you get my point: I WISH I had a DOS based loader to start an image which could provide a complete kernel with all the nessecary drivers to get a grip to all the hardware needed to operate the way I'm used to. Booting from a partition or without intervention of DOS based software is not always an option. Sometimes this "reduced choice of means" even leaves the machine unable to make it to FreeBSD running at all :( And duplicating the effort which has gone into the DOS software (if at all possible and feasible) looks like the wrong way to go. I will have a look at the ELF enabled fbsdboot.exe. And if it works -- what's the problem in delivering this one with the distro for those of us who need it desparately? > There are good technical reasons why this is the case. If you > don't understand them, please trust those of us that do. Could you please give a pointer where to learn more about this IF there's such a reason besides the "memory managers" at all? I'm aware of the complexity HIMEM and EMM & Co add to this field. But once they are eliminated -- is there still something speaking against DOS based boot loaders? I could live with this requirement to keep those managers away and I feel most other people could so, too, if they cannot or don't want to avoid to enter DOS. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 12:22: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id E58B614BE3; Wed, 12 Jan 2000 12:21:51 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id VAA12199; Wed, 12 Jan 2000 21:20:50 +0100 (MET) Date: Wed, 12 Jan 2000 21:20:47 +0100 (MET) From: Marcin Cieslak To: Warner Losh Cc: "Forrest W. Christian" , Mike Smith , Geff Hanoian , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels (flash cards off topic) In-Reply-To: <200001121758.KAA15284@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Warner Losh wrote: > The linear flash cards don't have an ata interface, > so PAO and soon -current won't recognize them. They don't have and we don't need it. Once can easily read them with low-level pccardc interface. In general, flash cards are not meant to be written too often, so I belive we won't put a real filesystem on them. Just a kernel and mfsroot image perhaps? [Added -hackers and please, remove -stable] -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 14:12:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 191A314F6A for ; Wed, 12 Jan 2000 14:12:28 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id RAA48395; Wed, 12 Jan 2000 17:12:26 -0500 (EST) (envelope-from mi) Message-Id: <200001122212.RAA48395@misha.cisco.com> Subject: installing staroffice To: stable@freebsd.org Date: Wed, 12 Jan 2000 17:12:26 -0500 (EST) Cc: msestina@cisco.com Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I'm trying to install the Staroffice port on the yesterday's -stable system (the latest linux_base port would not install on 3.2-RELEASE -- linux-bash was dying with "bad system call"). Now the setup.bin dies from signal 12... Anyone tested this recently? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 16:46:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-3-239.adsl.one.net [216.2.0.239]) by hub.freebsd.org (Postfix) with ESMTP id C2477151F5 for ; Wed, 12 Jan 2000 16:46:49 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id TAA00460 for freebsd-stable@freebsd.org; Wed, 12 Jan 2000 19:49:35 -0500 (EST) (envelope-from cokane) Date: Wed, 12 Jan 2000 19:49:35 -0500 From: Coleman Kane To: freebsd-stable@freebsd.org Subject: Linux Emulation v6.1 Message-ID: <20000112194935.A420@evil.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have now noticed that I can no longer play Quake3 under the new linux emulation, v6.1. It dies with invalid system call and dumps the core. Is this a problem of mine, or has anyone else experienced crashes from the new linux libs? --cokane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 16:50:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id BB5CB1554E for ; Wed, 12 Jan 2000 16:50:26 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA03230; Wed, 12 Jan 2000 17:50:14 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001130050.RAA03230@freeway.dcfinc.com> Subject: Re: 4.4 BSD forever? In-Reply-To: <20000109042111.D0285A80F@kendra.ne.mediaone.net> from Snuffles on Sonata at "Jan 8, 0 11:21:11 pm" To: root@kew.com (Snuffles on Sonata) Date: Wed, 12 Jan 2000 17:50:14 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Snuffles on Sonata wrote: > Some of us remember 4.1 and 4.2 as well. :-) My first BSD-flavored UNIX was a 4.2 from Mt. Xinu running on a DEC VAX 11/780. Though I'd been involved in some SysVish thingies (remember Convergent Technologies?) before that. > From a pragmatic standpoint, going to release FreeBSD 5.0 and > skipping all 4.x versions avoids confusion and honors the Source. > With this, the sequence remains linear and obvious, and has a > specific reason. Of all the comments on numbering I've read so far, I like this one. Numbers increase, so comparisons work. It pays homage, in a slightly esoteric (and geeky) way. It gives an opportunity to evangelize a bit to someone who enquires. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 17: 6:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D793E1557A for ; Wed, 12 Jan 2000 17:06:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA42189; Wed, 12 Jan 2000 18:06:51 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA18182; Wed, 12 Jan 2000 18:07:13 -0700 (MST) Message-Id: <200001130107.SAA18182@harmony.village.org> To: Gerhard Sittig Subject: Re: fbsdboot.exe can't load elf kernels Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 Jan 2000 20:37:27 +0100." <20000112203727.G7734@speedy.gsinet> References: <20000112203727.G7734@speedy.gsinet> <200001120828.AAA00633@mass.cdrom.com> Date: Wed, 12 Jan 2000 18:07:13 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000112203727.G7734@speedy.gsinet> Gerhard Sittig writes: : What's that bad about pure(!) DOS running in an early stage? To : make it clear: I'm NOT talking about "memory managers" running : already, having scrambled descriptor tables or enabling i386 : features (like virtual mode or special CPU's management : features). OLDER DOS versions can be trusted to not remap INT vectors, but newer versions do. When you remap the vectors and try to then boot FreeBSD you'll find that the vectors now point to arbitrary locations which tend to do bad things when this interrupt is called. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 17:13:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 2557914BCE for ; Wed, 12 Jan 2000 17:13:16 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA03413; Wed, 12 Jan 2000 18:09:29 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001130109.SAA03413@freeway.dcfinc.com> Subject: Re: Help _please_ "make world" faila In-Reply-To: <20000109213340.A24196@petra.hos.u-szeged.hu> from Szilveszter Adam at "Jan 9, 0 09:33:40 pm" To: sziszi@petra.hos.u-szeged.hu (Szilveszter Adam) Date: Wed, 12 Jan 2000 18:09:29 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Szilveszter Adam wrote: > If so, am I right in assuming that you do not delete /usr/obj/* before > each build? IMHO it is pretty much compulsory, esp if you also cvsup > in the meantime, that is /usr/src changes. Just to add a datapoint (and in the spirit of discouraging chicken waving), I never rm /usr/obj and have never had a build fail because of it. I will say that unless an examination of the CVSup log shows only trivial changes, I do a "make world" without "-DNOCLEAN", which I believe pretty much does the same thing as the remove. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 17:30:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 36F7215013; Wed, 12 Jan 2000 17:29:37 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA03644; Wed, 12 Jan 2000 18:28:59 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001130128.SAA03644@freeway.dcfinc.com> Subject: Re: [OT] DOS-in-ROM (was Re: fbsdboot.exe can't load elf kernels) In-Reply-To: from Bob K at "Jan 11, 0 08:39:13 pm" To: melange@yip.org (Bob K) Date: Wed, 12 Jan 2000 18:28:59 -0700 (MST) Cc: msmith@FreeBSD.ORG, boing@boing.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Bob K wrote: > Just as an aside, I spent all day today using an 80286 laptop with > DOS-in-ROM (running TeleMate off a floppy). Now this has got me wondering > if PicoBSD would run on that thing... Don't think so. The FreeBSD kernel needs 80386 hardware registers and memory management at the minimum. On the other hand, I bought (flea market, $25) a Compaq 386/20 laptop with an 80Mb hard drive and 4Mb of RAM. It boots and runs FreeBSD. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 18:15:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id D115014BE4 for ; Wed, 12 Jan 2000 18:15:07 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA03924; Wed, 12 Jan 2000 19:14:56 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001130214.TAA03924@freeway.dcfinc.com> Subject: Re: access floppy rw to lock system In-Reply-To: from Agent Drek at "Jan 12, 0 11:01:08 am" To: drek@MonsterByMistake.Com (Agent Drek) Date: Wed, 12 Jan 2000 19:14:56 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Agent Drek wrote: > > I have a repeatable problem on my FreeBSD-3.4Stable workstation. If > the floppy disk is physically tabbed as read-only and I mount it rw I > can then 'lock' the system up by using vim (to read a text-file on the > disk ... less had the same problem). Is this expected behaviour? I > did this from the console and could still between the virtual > consoles. The only way to get going again was to reboot. After that > happened twice I tabbed the disk writable and things were fine. I'd start by asking, "Why would you do that?" If you make the media read-only at the hardware level, by all means mount it read-only. If you're just asking why this interesting phenomenon occurs, that's a different question. I'm not sure if it's an MS-DOS filesystem, but a UFS mount will want to modify the superblock with the mount time and mount point. Mostly, I suspect, so that fsck can display that information. :-) -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 18:20: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id D23DD14D8C; Wed, 12 Jan 2000 18:19:57 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA03992; Wed, 12 Jan 2000 19:19:55 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001130219.TAA03992@freeway.dcfinc.com> Subject: Re: fbsdboot.exe can't load elf kernels In-Reply-To: <200001121637.IAA02268@mass.cdrom.com> from Mike Smith at "Jan 12, 0 08:37:47 am" To: msmith@FreeBSD.ORG (Mike Smith) Date: Wed, 12 Jan 2000 19:19:54 -0700 (MST) Cc: ccthomas@access1.net, msmith@FreeBSD.ORG, tosh@assa.vl.net.ua, fjoe@iclub.nsu.ru, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Mike Smith wrote: >> >> What would be the best reference(es) [on/off web] describing said >> process(es) ? > > If you're referring to the booting and running of FreeBSD, you would want > to start with the source code. What if he's asking about "You cannot boot and run FreeBSD once DOS has been booted on the system."? >> Courtney > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 18:24:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 1B77414DFD for ; Wed, 12 Jan 2000 18:24:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA03454; Wed, 12 Jan 2000 18:31:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001130231.SAA03454@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: chad@DCFinc.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Wed, 12 Jan 2000 19:19:54 MST." <200001130219.TAA03992@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 18:31:14 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I recall, Mike Smith wrote: > >> > >> What would be the best reference(es) [on/off web] describing said > >> process(es) ? > > > > If you're referring to the booting and running of FreeBSD, you would want > > to start with the source code. > > What if he's asking about "You cannot boot and run FreeBSD once DOS > has been booted on the system."? I would point out that in this thread it's already been suggested that the list archives contain the last several instances of the discussion. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 18:37:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id C800914A2D for ; Wed, 12 Jan 2000 18:37:48 -0800 (PST) (envelope-from vons@iname.com) Received: from cyril (paris11-nas3-45-248.dial.proxad.net [212.27.45.248]) by postfix1.free.fr (Postfix) with ESMTP id 3E46629B12 for ; Wed, 12 Jan 2000 23:35:50 +0100 (MET) Message-Id: <4.2.2.20000112233926.00aebd00@mail.vons.local> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 12 Jan 2000 23:39:31 +0100 To: freebsd-stable@FreeBSD.ORG From: Gert-Jan Vons Subject: Re: parallel printer & nlpt0 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 18:23 00/01/12 , Vivek Khera wrote: > >>>>> "DB" == David Berard writes: > >DB> I upgrade my system from freebsd 2.X to freebsd 3.X stable of yesterday, >DB> since this, my printer (HP LaserJet 6L) stop working correctly with >big DB> files (no txt files). > >Same problem for me with a HP LJ4m. > >The only thing that fixed it was "lptcontrol -s" (or -p) to go into >standard polled mode. I too believe the lpt0 device is not working >properly. This was tested on two separate machines, one of which >worked flawlessly with the lp0 printer device under BSD/OS with >interrupts enabled. Same here as well. Since 3.x, I also have to put the parallel port in polled mode on my PCs, a friend sees the same. This is on Asus P55TP4N or P5A with a Lexmark Optra Ep, or a brand X board with a HP LJ an Epson Stylus Photo. We have even seen problems booting FBSD when the printers were not switched off. Haven't tried it with 3.4 yet though, waiting for the CDs to arrive in Europe... Gert-Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 19: 9:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id F3A0014F54 for ; Wed, 12 Jan 2000 19:09:44 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id WAA38409; Wed, 12 Jan 2000 22:09:38 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id WAA04406; Wed, 12 Jan 2000 22:09:38 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001130309.WAA04406@rtfm.newton> Subject: Re: Linux Emulation v6.1 In-Reply-To: <20000112194935.A420@evil.2y.net> from Coleman Kane at "Jan 12, 2000 07:49:35 pm" To: Coleman Kane Date: Wed, 12 Jan 2000 22:09:38 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Wed, 12 Jan 2000 19:38:34 -0800 (PST) (envelope-from jim@nasby.net) Received: from nasby.net (sysnasby@207-229-150-232.d.enteract.com [207.229.150.232]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id VAA36870 for ; Wed, 12 Jan 2000 21:38:32 -0600 (CST) (envelope-from jim@nasby.net) Message-ID: <387D48B7.7E6CAA9C@nasby.net> Date: Wed, 12 Jan 2000 21:38:31 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: shutdown problems FBSD 3.4-STABLE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, I am having the exact same problems, except I'm not running softupdates, only vinum. The box is an Asus P2B-DS, dual PII-333s, Matrox G200, XFree86. The non-dying process I can live with. The big problems that I see is that shutdown/reboot/halt is very inconsistent in it's behavior. The 3 commands will do different things at different times (I mostly use shutdown, but I've seen the same problems with halt and reboot). 1) Box gets partway through killing processes then hangs 2) same as 1, with the addition of a continuous tone from the speaker 3) Same as 1, except that after I hit a few keys, I get the tone from the speaker I've seen this behavior on shutdown -r, shutdown now (drop to single user), reboot, and halt (maybe shutdown -h too, don't remember). This hardware was running 3.0-RELEASE for months without problems, so I rather doubt it's the hardware. I first noticed it when I started running vinum under 3.3-stable, and the problem continues. I just tried rm'ing /usr/src and /usr/obj and re-cvsupping, all to no avail. Any ideas? Greg, have you heard other cases of this? "O. Hartmann" wrote: > > Since I installed vinum with softupdates, I have several problems when shutting > down the server. Whenever I shut down the machine, init reports a non dying process > and tells me, that ps axl has been adviced. After a few seconds this process, which name I > never see, has obviously been killed and the system performs a normal shutdown or reboot. > But sometimes the las tmessage on the screen is that all disks has been sync'ed but nothing happens > further on. The system is stuck in this process and seems to be frozen. Only a reset or > powercycle can help, but then fsck reports some dirty partitions ... > > How can I find out what process won't dy? How to figure out what process causes the hanging > or freezing the system after shutdown? > > With regards, > > Gruss O. Hartmann > ------------------------------------------------------------------- > ohartman@ipamzlx.physik.uni-mainz.de > > Klimadatenserver des IPA, Universitaet Mainz > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 21:23:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 35AC714D67 for ; Wed, 12 Jan 2000 21:23:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA24683; Wed, 12 Jan 2000 21:23:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA23017; Wed, 12 Jan 2000 21:23:12 -0800 (PST) (envelope-from obrien) Date: Wed, 12 Jan 2000 21:23:12 -0800 From: "David O'Brien" To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) Message-ID: <20000112212312.F17687@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <20000110205710.D98651@relay.nuxi.com> <200001111648.IAA52758@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001111648.IAA52758@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Tue, Jan 11, 2000 at 08:48:08AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 08:48:08AM -0800, Cy Schubert - ITSD Open Systems Group wrote: > > UCB and AT&T had agreed that there were to be no new releases of BSD > and that 4BSD was the final release. 4.1BSD - 4.4BSD were named such > because they were "officially" only modifications to 4BSD and as such > were not full releases. In fact they contained more new features than > previous releases and were modifications to 4BSD in name only. This is a quote from McKusick on a previous post. It doesn't seem to back up your statements. > As I understood it, 4BSD was to be the last release based on 32V > and AT&T wouldn't license anything newer on agreeable terms, so > Berkeley released 4.1. 4.1c (later renamed to 4.2) was released to > fullfil their contractual obligation to DARPA. At least that's the > scuttlebutt at the time, which likely suffered from at least some > "telephone game" syndrome. AT&T kept wanting Berkeley to move forward to a newer license, but we resisted because the newer licenses were considerably more expensive. That had nothing to do with the naming. The 4.1 release was called that because AT&T was concerned that there would be confusion in the marketplace if there were System V and 5BSD, so we agreed to call it 4.1 instead of 5.0. The 4.1c release was never renamed 4.2. The 4.2 release followed 4.1c. The 4.1c release was what would probably be called an alpha release of 4.2 today. > It's all in Kirk's book the Design and Implementation of 4.4BSD. What page numbers? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 12 22: 4:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.monsterbymistake.com (monsterbymistake.com [205.207.163.17]) by hub.freebsd.org (Postfix) with ESMTP id C92E115090 for ; Wed, 12 Jan 2000 22:04:15 -0800 (PST) (envelope-from drek@MonsterByMistake.Com) Received: from bunny.monsterbymistake.com([205.207.163.17]) (2466 bytes) by mail.monsterbymistake.com via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Thu, 13 Jan 2000 01:04:47 -0500 (EST) (Smail-3.2.0.107 1999-Sep-8 #1 built 1999-Sep-11) Date: Thu, 13 Jan 2000 01:04:47 -0500 (EST) From: Agent Drek To: "Chad R. Larson" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system In-Reply-To: <200001130214.TAA03924@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Chad R. Larson wrote: |Date: Wed, 12 Jan 2000 19:14:56 -0700 (MST) |From: Chad R. Larson |To: Agent Drek |Cc: freebsd-stable@FreeBSD.ORG |Subject: Re: access floppy rw to lock system | |As I recall, Agent Drek wrote: |> |> I have a repeatable problem on my FreeBSD-3.4Stable workstation. If |> the floppy disk is physically tabbed as read-only and I mount it rw I |> can then 'lock' the system up by using vim (to read a text-file on the |> disk ... less had the same problem). Is this expected behaviour? I |> did this from the console and could still between the virtual |> consoles. The only way to get going again was to reboot. After that |> happened twice I tabbed the disk writable and things were fine. | |I'd start by asking, "Why would you do that?" | |If you make the media read-only at the hardware level, by all means |mount it read-only. | I'm not used to ever using a floppy disk, no need until I got ether- net card and needed info from damn diskette. |If you're just asking why this interesting phenomenon occurs, that's |a different question. I'm not sure if it's an MS-DOS filesystem, |but a UFS mount will want to modify the superblock with the mount |time and mount point. and should hang the ENTIRE system if it can't!?! I'm asking because I used the default way of thinking ... mount /floppy I usually use vim to read big files ... I'm happy to know that this is a way to instantly hang a freebsd server. This felt wrong to me so I thought I would try and get a second opinion. What if the disk was just corrupt .. could the same behaviour happen? was msdosfs (m$-driver disk). One person mailed me off list to say that they too had done this once as well. thanks, =derek Monster By Mistake Inc > 'digital plumber' http://www.interlog.com/~drek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 2:19:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 317AF1533D; Thu, 13 Jan 2000 02:19:13 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id LAA18007; Thu, 13 Jan 2000 11:18:59 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <20000109042111.D0285A80F@kendra.ne.mediaone.net> References: <20000109042111.D0285A80F@kendra.ne.mediaone.net> Date: Thu, 13 Jan 2000 10:19:35 +0100 To: root@kew.com (Snuffles on Sonata), chat@freebsd.org From: Brad Knowles Subject: Re: 4.4 BSD forever? Cc: stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:21 PM -0500 2000/1/8, Snuffles on Sonata wrote: > Some of us remember 4.1 and 4.2 as well. :-) Some of us remember 2.9BSD on a PDP 11/70 with two banks of 64KB RAM. ;-) And some of remember the day we saw a 15% performance increase on that machine, when one of the local hacker/admins installed a new kernel where the machine code (not assembly) had been hand-tuned. ;-) ;-) Of course, I'm sure that some of us remember much further back than that. Me, I can only go back so far as my freshman year of 1984. Also, this no longer has anything to do with -stable. This thread should either be killed or moved to -chat. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 2:45:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C666815676; Thu, 13 Jan 2000 02:45:21 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA84771; Thu, 13 Jan 2000 11:45:16 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: cjclark@home.com Cc: adam@algroup.co.uk (Adam Laurie), stable@freebsd.org Subject: Re: console disappears after reboot References: <200001121933.OAA11492@cc942873-a.ewndsr1.nj.home.com> From: Dag-Erling Smorgrav Date: 13 Jan 2000 11:45:15 +0100 In-Reply-To: "Crist J. Clark"'s message of "Wed, 12 Jan 2000 14:33:04 -0500 (EST)" Message-ID: Lines: 25 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -stable from -security] "Crist J. Clark" writes: > Adam Laurie wrote, > > Crist J. Clark wrote: > > > > Anyway, to cut a long story short, I would prefer to simply do something > > > > in /etc/rc.local to force the console back to local kb/vga, or disable > > > > the serial console in the kernel itself... so my question is: what? Is > > > > there such a command/setting? > > > If a console has "died," you should [HUP init] > > Unfortunately not. I assume it only tries to refresh the serial console. > I don't think so. Is the getty(8) for the device (I assume ttyv0) still > in the ps(1) output? If it is, perhaps kill it. Either kill it dead > and SIGHUP init(8) to start the new one, or maybe some signal (a HUP?) > refreshes a getty. You're totally off the track. His problem is that the kernel (or the boot loader) decides that there is no built-in console and uses a serial console instead. This has nothing to do with init(8). I guess the right person to answer this kind of question would be Mike Smith or Daniel Sobral. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 2:56: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybercable.tm.fr (mail.cybercable.tm.fr [195.132.0.194]) by hub.freebsd.org (Postfix) with SMTP id 7B9E215001 for ; Thu, 13 Jan 2000 02:55:59 -0800 (PST) (envelope-from dbera@cybercable.tm.fr) Received: (qmail 6655145 invoked by uid 502); 13 Jan 2000 10:57:55 -0000 Received: from r22m148.cybercable.tm.fr (HELO cybercable.tm.fr) (195.132.22.148) by mail.cybercable.tm.fr with SMTP; 13 Jan 2000 10:57:55 -0000 Message-ID: <387DAF03.DFFDCE1@cybercable.tm.fr> Date: Thu, 13 Jan 2000 11:54:59 +0100 From: David Berard X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I want to thanks people that answer me : Trond Endretol, Vivek Khera, Michel Talon and Gert-Jan Vons They proposed to me 2 solutions : 1. make a "lptcontrol -p" before using the printer, to configure the parallel port in poll mode. 2. modify the ppc entry in the kernel config file, and build a new kernel --- device ppc0 at isa? port? flags 0x40 net irq 7 +++ device ppc0 at isa? port? flags 0x40 tty irq 7 this 2 solutions work correctly with the lpt driver. best regards. -- David Berard wrote: ... > For example, if I try to print one of the postscript examples (tiger.ps) > from de ghostscript port (gs 5.50), I obtain more or less the picture, > but with some incorrect lines, and some garbages (cabalistic > characters), and sometime unattended formfeed. > > I think lpt0 (ex nlpt0 device) is the problem, because if I change in > the BIOS the mode of the parallel port (SPP, EPP 1.7, EPP 1.9, EPP+ECP), > I don't obtain the same results. > > I also try to play with the flags of ppc device in the kernel config > file, but with no luck. ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 3: 9:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from unix.sim.com.pl (unix.sim.com.pl [195.117.85.26]) by hub.freebsd.org (Postfix) with ESMTP id F407215016 for ; Thu, 13 Jan 2000 03:09:27 -0800 (PST) (envelope-from gawel@sim.com.pl) Received: from sim.com.pl (pawel [192.168.1.20]) by unix.sim.com.pl (8.9.3/8.9.3) with ESMTP id MAA19350 for ; Thu, 13 Jan 2000 12:07:53 +0100 (CET) (envelope-from gawel@sim.com.pl) Message-ID: <387DB3BB.8D85E624@sim.com.pl> Date: Thu, 13 Jan 2000 12:15:07 +0100 From: Gawel X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: portmap Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I 've got it several times: portmap[16116]: connect from 195.31.252.2 to dump(): request from unauthorized host. It is harmless but annoying. Is there any way to prevent portman listening requests on a NIC, ip, etc. besides using hosts.allow? Thanks, Gawel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 3:16:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id A5923150E0 for ; Thu, 13 Jan 2000 03:16:35 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id LAA45239; Thu, 13 Jan 2000 11:16:44 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <387DAF03.DFFDCE1@cybercable.tm.fr> Date: Thu, 13 Jan 2000 11:16:44 -0000 (GMT) From: "Steve O'Hara-Smith" To: David Berard Subject: Re: parallel printer & nlpt0 Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-00 David Berard wrote: > 1. make a "lptcontrol -p" before using the printer, to configure the > parallel port in poll mode. > > 2. modify the ppc entry in the kernel config file, and build a new > kernel > --- device ppc0 at isa? port? flags 0x40 net irq 7 > +++ device ppc0 at isa? port? flags 0x40 tty irq 7 > > this 2 solutions work correctly with the lpt driver. Just for the sake of clarity is that both in combination or will either solution work alone ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 3:27:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybercable.tm.fr (mail.cybercable.tm.fr [195.132.0.194]) by hub.freebsd.org (Postfix) with SMTP id 03DA314EFA for ; Thu, 13 Jan 2000 03:27:11 -0800 (PST) (envelope-from dbera@cybercable.tm.fr) Received: (qmail 6691762 invoked by uid 502); 13 Jan 2000 11:29:07 -0000 Received: from r22m148.cybercable.tm.fr (HELO cybercable.tm.fr) (195.132.22.148) by mail.cybercable.tm.fr with SMTP; 13 Jan 2000 11:29:07 -0000 Message-ID: <387DB653.534B009@cybercable.tm.fr> Date: Thu, 13 Jan 2000 12:26:11 +0100 From: David Berard X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Steve O'Hara-Smith Cc: freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the 2 solutions are not bound. You can use one or the other. Steve O'Hara-Smith wrote: > > On 13-Jan-00 David Berard wrote: > > 1. make a "lptcontrol -p" before using the printer, to configure the > > parallel port in poll mode. > > > > 2. modify the ppc entry in the kernel config file, and build a new > > kernel > > --- device ppc0 at isa? port? flags 0x40 net irq 7 > > +++ device ppc0 at isa? port? flags 0x40 tty irq 7 > > > > this 2 solutions work correctly with the lpt driver. > > Just for the sake of clarity is that both in combination or will either > solution work alone ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 3:51:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles544.castles.com [208.214.165.108]) by hub.freebsd.org (Postfix) with ESMTP id 6DA3D14A0A for ; Thu, 13 Jan 2000 03:51:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA01817; Thu, 13 Jan 2000 03:58:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001131158.DAA01817@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dag-Erling Smorgrav Cc: cjclark@home.com, adam@algroup.co.uk (Adam Laurie), stable@freebsd.org Subject: Re: console disappears after reboot In-reply-to: Your message of "13 Jan 2000 11:45:15 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Jan 2000 03:58:10 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [moved to -stable from -security] > > "Crist J. Clark" writes: > > Adam Laurie wrote, > > > Crist J. Clark wrote: > > > > > Anyway, to cut a long story short, I would prefer to simply do something > > > > > in /etc/rc.local to force the console back to local kb/vga, or disable > > > > > the serial console in the kernel itself... so my question is: what? Is > > > > > there such a command/setting? > > > > If a console has "died," you should [HUP init] > > > Unfortunately not. I assume it only tries to refresh the serial console. > > I don't think so. Is the getty(8) for the device (I assume ttyv0) still > > in the ps(1) output? If it is, perhaps kill it. Either kill it dead > > and SIGHUP init(8) to start the new one, or maybe some signal (a HUP?) > > refreshes a getty. > > You're totally off the track. His problem is that the kernel (or the > boot loader) decides that there is no built-in console and uses a > serial console instead. This has nothing to do with init(8). I guess > the right person to answer this kind of question would be Mike Smith > or Daniel Sobral. I don't have any context for this, so it's a bit hard to be sure. The decision as to which console to use is normally made by boot2; it will use the video and keyboard BIOS unless: a) the -h flag is supplied in /boot.config b) the -P flag is supplied in /boot.config AND the BIOS has not set the 'extended keyboard present' flag. This decision can be overridden with a setting in /boot/loader.conf which can cause the loader to switch to another console, and it can be overridden again by flags set on an sio device. So in summary; there's nothing that will "decide there is no built-in console" unless you explicitly tell it to go look for itself. Anything that's causing the system to talk to a serial console is at the admin's request. At this point in time, there is no way to force a change of console once the system is up and running. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 3:59:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from netcom.com (netcom13.netcom.com [199.183.9.113]) by hub.freebsd.org (Postfix) with ESMTP id E493E1559B for ; Thu, 13 Jan 2000 03:59:30 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id DAA09342 for freebsd-stable@freebsd.org; Thu, 13 Jan 2000 03:59:25 -0800 (PST) From: Stan Brown Message-Id: <200001131159.DAA09342@netcom.com> Subject: IP Tunneling, is it possible? To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Thu, 13 Jan 2000 06:59:24 -0500 (EST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have 2 physicaly seperate segments of the same subnet that I need to connect logicaly. I have a FreeBSD gateway/firewall machine on both of the subnets conected to the corporate network. Specificaly, I have an existing network 170.85.106.* netmask 255.255.255.128 which connects to the corporate 170.85.113.* network this is then is routed to 170.85.109.* Now I have in my office some more machines that I need to set up for the 170.85.106 net. Is there a way to encapsulate packets on the 2 parts of the 170.85.105 network, and send them to the other part, where they would be unencapsulated? I think this is called IP Tunneling and Linux appears to support it, but I would rather not change the 2 gateway/firewall machines over to Linux, if I don't have to. I regert if you jave seen this request before, I have submited it on questions, and networking, but the only response I got was a flame about my typing. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 4: 0:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtppzh.pzh.nl (webshield.pzh.nl [194.178.168.50]) by hub.freebsd.org (Postfix) with SMTP id 5D35A155E2 for ; Thu, 13 Jan 2000 04:00:46 -0800 (PST) (envelope-from MULHUIJZEN@PZH.NL) Received: FROM smtp.pzh.nl BY smtppzh.pzh.nl ; Thu Jan 13 12:59:43 2000 0000 Received: from PZH40-1-Message_Server by smtp.pzh.nl with Novell_GroupWise; Thu, 13 Jan 2000 12:59:46 +0100 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Thu, 13 Jan 2000 12:59:23 +0100 From: "ROGIER MULHUIJZEN" To: , Subject: Re: portmap Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sure, have a look at /etc/rc.firewall and/or 'man 8 ipfw' You just configure IPFW to drop incoming packets for the portmap port. And if you want certain hosts to be able to use portmap, you add rules with a higher priority that allow those same packets if they come from a certain host. DocWilco >>> Gawel 01/13 12:15 PM >>> Hello, I 've got it several times: portmap[16116]: connect from 195.31.252.2 to dump(): request from unauthorized host. It is harmless but annoying. Is there any way to prevent portman listening requests on a NIC, ip, etc. besides using hosts.allow? Thanks, Gawel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 4: 9:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 10F3B155AB for ; Thu, 13 Jan 2000 04:09:37 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA13414; Thu, 13 Jan 2000 13:09:16 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <387DB3BB.8D85E624@sim.com.pl> References: <387DB3BB.8D85E624@sim.com.pl> Date: Thu, 13 Jan 2000 13:07:54 +0100 To: Gawel , "freebsd-stable@FreeBSD.ORG" From: Brad Knowles Subject: Re: portmap Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:15 PM +0100 2000/1/13, Gawel wrote: > I 've got it several times: > portmap[16116]: connect from 195.31.252.2 to dump(): request from > unauthorized host. > It is harmless but annoying. > Is there any way to prevent portman listening requests on a NIC, ip, > etc. besides using hosts.allow? My understanding is that portmap uses UDP, which TCP-Wrappers doesn't protect. You can get an improved version of portmap that makes explicit use of wraplib (I'd suggest starting with Wietse Venema's version). I'd go to and start from there. Or you can make use of kernel-level firewalling to prevent anyone from successfully getting packets through to a particular port on your machine, unless you want to let them through. Look at "man ipfw" for starters. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 4:47:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtppzh.pzh.nl (webshield.pzh.nl [194.178.168.50]) by hub.freebsd.org (Postfix) with SMTP id D14A715135 for ; Thu, 13 Jan 2000 04:47:13 -0800 (PST) (envelope-from MULHUIJZEN@PZH.NL) Received: FROM smtp.pzh.nl BY smtppzh.pzh.nl ; Thu Jan 13 13:46:35 2000 0000 Received: from PZH40-1-Message_Server by smtp.pzh.nl with Novell_GroupWise; Thu, 13 Jan 2000 13:46:38 +0100 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Thu, 13 Jan 2000 13:46:33 +0100 From: "ROGIER MULHUIJZEN" To: , Subject: Re: IP Tunneling, is it possible? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe http://vtun.netpedia.net/ is something you might be looking for. It provides all sorts of tunneling over IP, even Ethernet, and does encryption too if you want it too. You can download the source, but they also have Linux, FreeBSD (which is what you want =) ) and Solaris packages. If that doesn't fit your bill, try searching www.freshmeat.net. It is my main searchengine for Unix software.... DocWilco >>> Stan Brown 01/13 12:59 PM >>> I have 2 physicaly seperate segments of the same subnet that I need to connect logicaly. I have a FreeBSD gateway/firewall machine on both of the subnets conected to the corporate network. Specificaly, I have an existing network 170.85.106.* netmask 255.255.255.128 which connects to the corporate 170.85.113.* network this is then is routed to 170.85.109.* Now I have in my office some more machines that I need to set up for the 170.85.106 net. Is there a way to encapsulate packets on the 2 parts of the 170.85.105 network, and send them to the other part, where they would be unencapsulated? I think this is called IP Tunneling and Linux appears to support it, but I would rather not change the 2 gateway/firewall machines over to Linux, if I don't have to. I regert if you jave seen this request before, I have submited it on questions, and networking, but the only response I got was a flame about my typing. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 6: 0:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C79B115715 for ; Thu, 13 Jan 2000 06:00:26 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id NAA20058; Thu, 13 Jan 2000 13:59:31 GMT (envelope-from rb) Message-Id: <3.0.6.32.20000113135723.007e3700@gid.co.uk> X-Sender: rbmail@gid.co.uk X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 13 Jan 2000 13:57:23 +0000 To: Stan Brown From: Bob Bishop Subject: Re: IP Tunneling, is it possible? Cc: freebsd-stable@FreeBSD.ORG (FreeBSD Stable List) In-Reply-To: <200001131159.DAA09342@netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 06:59 AM 1/13/00 -0500, Stan Brown wrote: [...] > Is there a way to encapsulate packets on the 2 parts of the 170.85.105 > network, and send them to the other part, where they would be > unencapsulated? I think this is called IP Tunneling and Linux appears > to support it, but I would rather not change the 2 gateway/firewall > machines over to Linux, if I don't have to. pipsecd (in ports/security) works well. -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 6:15:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 8D348156EC for ; Thu, 13 Jan 2000 06:15:21 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id JAA41262; Thu, 13 Jan 2000 09:15:13 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id JAA05663; Thu, 13 Jan 2000 09:15:12 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001131415.JAA05663@rtfm.newton> Subject: Re: IP Tunneling, is it possible? In-Reply-To: <200001131159.DAA09342@netcom.com> from Stan Brown at "Jan 13, 2000 06:59:24 am" To: Stan Brown Date: Thu, 13 Jan 2000 09:15:12 -0500 (EST) Cc: stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Date: Thu, 13 Jan 2000 14:18:40 +0000 From: Adam Laurie Organization: A.L. Group plc X-Mailer: Mozilla 4.07 [en] (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: Dag-Erling Smorgrav , cjclark@home.com, stable@freebsd.org Subject: Re: console disappears after reboot References: <200001131158.DAA01817@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > [moved to -stable from -security] I'm not subscribed to -stable, so please copy me on any responses. > > > > "Crist J. Clark" writes: > > > Adam Laurie wrote, > > > > Crist J. Clark wrote: > > > > > > Anyway, to cut a long story short, I would prefer to simply do something > > > > > > in /etc/rc.local to force the console back to local kb/vga, or disable > > > > > > the serial console in the kernel itself... so my question is: what? Is > > > > > > there such a command/setting? > > > > > If a console has "died," you should [HUP init] > > > > Unfortunately not. I assume it only tries to refresh the serial console. > > > I don't think so. Is the getty(8) for the device (I assume ttyv0) still > > > in the ps(1) output? If it is, perhaps kill it. Either kill it dead > > > and SIGHUP init(8) to start the new one, or maybe some signal (a HUP?) > > > refreshes a getty. > > > > You're totally off the track. His problem is that the kernel (or the > > boot loader) decides that there is no built-in console and uses a > > serial console instead. This has nothing to do with init(8). I guess > > the right person to answer this kind of question would be Mike Smith > > or Daniel Sobral. > > I don't have any context for this, so it's a bit hard to be sure. > > The decision as to which console to use is normally made by boot2; it will > use the video and keyboard BIOS unless: > > a) the -h flag is supplied in /boot.config > b) the -P flag is supplied in /boot.config AND the BIOS has not set the > 'extended keyboard present' flag. > > This decision can be overridden with a setting in /boot/loader.conf which > can cause the loader to switch to another console, and it can be > overridden again by flags set on an sio device. > > So in summary; there's nothing that will "decide there is no built-in > console" unless you explicitly tell it to go look for itself. Anything > that's causing the system to talk to a serial console is at the admin's > request. At this point in time, there is no way to force a change of > console once the system is up and running. Unfortunately experience tells us otherwise. If we boot with no VGA plugged in, we can't plug one in later and expect to see a console. The admin has not requested a serial console, in fact we've tried disabling it in the kernel config. We also have a problem with using /boot/loader.conf (it can't be found if it's outside cylinder 1023, even though the boot itself still works). Here's my original post to give you the full context: I am working at a facility that has a locked server room with an annexe just outside where you can access the servers without being in the cold/noise. For security reasons, the vga/keyboard switch that feeds the annexe is switched off when there's no-one there. This setup has worked fine for a number of years. However, we are now installing some new servers and we've found that if they get rebooted when the switch is off, the console gets changed to a serial device. This means we've lost the machine(s) until we log in remotely and reboot again. Not good. It seems that FreeBSD 3.1+ scans for a console, and if it can't find kb / vga it switches to serial. The old machines all work fine as they are 3.0 or less. I know I can set the console device in /boot/loader.conf, but this leads to other problems (possibly a bug here): on some machines we get a "/boot/loader not found - Disk error 0x1", and we suspect that this is to do with the boot partition not being constrained to the first 1024 cylinders. Anyway, to cut a long story short, I would prefer to simply do something in /etc/rc.local to force the console back to local kb/vga, or disable the serial console in the kernel itself... so my question is: what? Is there such a command/setting? cheers, Adam -- Adam Laurie Tel: +44 (181) 742 0755 A.L. Digital Ltd. Fax: +44 (181) 742 5995 Voysey House Barley Mow Passage http://www.aldigital.co.uk London W4 4GB mailto:adam@algroup.co.uk UNITED KINGDOM PGP key on keyservers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 6:21: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.rz.tu-clausthal.de (merlin.rz.tu-clausthal.de [139.174.1.23]) by hub.freebsd.org (Postfix) with ESMTP id 718D6155F9 for ; Thu, 13 Jan 2000 06:20:54 -0800 (PST) (envelope-from rk@merlin.rz.tu-clausthal.de) Received: (from rk@localhost) by merlin.rz.tu-clausthal.de (8.9.3/8.9.3) id PAA77929; Thu, 13 Jan 2000 15:20:49 +0100 (CET) Date: Thu, 13 Jan 2000 15:20:49 +0100 (CET) Message-Id: <200001131420.PAA77929@merlin.rz.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Linux Emulation v6.1 From: Ronald Kuehn X-Newsreader: NN version 6.5.0 CURRENT #120 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Coleman Kane once stated: > =Hi, I have now noticed that I can no longer play Quake3 under the new > =linux emulation, v6.1. It dies with invalid system call and dumps the > =core. Is this a problem of mine, or has anyone else experienced crashes > =from the new linux libs? > I can no longer use the earlier installed StarOffice-5.1 with the same > symptoms and can not reinstall it :( > -mi As a workaround you can downgrade to linux_base-5.2. That doesn't seem to use the rt_sigsuspend system call. Bye, Ronald -- Give a man a fish, and you feed him for a day. Tell him he should learn how to fish himself, and he'll hate you for a lifetime. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 6:39:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id E245315002; Thu, 13 Jan 2000 06:39:23 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id JAA41307; Thu, 13 Jan 2000 09:39:16 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id JAA05854; Thu, 13 Jan 2000 09:39:16 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001131439.JAA05854@rtfm.newton> Subject: Re: Linux Emulation v6.1 In-Reply-To: <200001131420.PAA77929@merlin.rz.tu-clausthal.de> from Ronald Kuehn at "Jan 13, 2000 03:20:49 pm" To: Ronald Kuehn Date: Thu, 13 Jan 2000 09:39:16 -0500 (EST) Cc: freebsd-stable@freebsd.org, ports@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Coleman Kane once stated: = => =Hi, I have now noticed that I can no longer play Quake3 under the => =new linux emulation, v6.1. It dies with invalid system call and => =dumps the core. Is this a problem of mine, or has anyone else => =experienced crashes from the new linux libs? = => I can no longer use the earlier installed StarOffice-5.1 with the => same symptoms and can not reinstall it :( = =As a workaround you can downgrade to linux_base-5.2. That doesn't seem =to use the rt_sigsuspend system call. So, is there an active work in progress, or should the port be marked broken on -stable? Should we have another port emulatores/linux_base5? Is a formal PR needed? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 6:39:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 769911552C for ; Thu, 13 Jan 2000 06:39:31 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA04682; Thu, 13 Jan 2000 06:39:22 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda04680; Thu Jan 13 06:39:15 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA49551; Thu, 13 Jan 2000 06:39:15 -0800 (PST) Message-Id: <200001131439.GAA49551@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdB49546; Thu Jan 13 06:39:09 2000 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Mailer: MH 6.8.4, Exmh 2.1.1 X-Sender: cschuber To: obrien@NUXI.com Cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG Subject: Re: Next release should be called 5.0 (was:4.4 BSD forever?) In-reply-to: Your message of "Wed, 12 Jan 2000 21:23:12 PST." <20000112212312.F17687@dragon.nuxi.com> Date: Thu, 13 Jan 2000 06:39:09 -0800 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000112212312.F17687@dragon.nuxi.com>, "David O'Brien" writes: > On Tue, Jan 11, 2000 at 08:48:08AM -0800, Cy Schubert - ITSD Open Systems Gro > up wrote: > > > > UCB and AT&T had agreed that there were to be no new releases of BSD > > and that 4BSD was the final release. 4.1BSD - 4.4BSD were named such > > because they were "officially" only modifications to 4BSD and as such > > were not full releases. In fact they contained more new features than > > previous releases and were modifications to 4BSD in name only. > > This is a quote from McKusick on a previous post. It doesn't seem to > back up your statements. > > > As I understood it, 4BSD was to be the last release based on 32V > > and AT&T wouldn't license anything newer on agreeable terms, so > > Berkeley released 4.1. 4.1c (later renamed to 4.2) was released to > > fullfil their contractual obligation to DARPA. At least that's the > > scuttlebutt at the time, which likely suffered from at least some > > "telephone game" syndrome. > > AT&T kept wanting Berkeley to move forward to a newer license, but > we resisted because the newer licenses were considerably more > expensive. That had nothing to do with the naming. The 4.1 release > was called that because AT&T was concerned that there would be > confusion in the marketplace if there were System V and 5BSD, so > we agreed to call it 4.1 instead of 5.0. The 4.1c release was never > renamed 4.2. The 4.2 release followed 4.1c. The 4.1c release was > what would probably be called an alpha release of 4.2 today. > > > > It's all in Kirk's book the Design and Implementation of 4.4BSD. > > What page numbers? Rereading the first 17 pages where Kirk discusses BSD history, he doesn't even mention any licensing issues between UCB and AT&T until 4.4BSD. As a matter of fact page 9 discusses 4BSD as a project which had a number of releases. I obvously stand corrected. It's been a while since I read the book. If I've fogotten this much, I should read it again. > > -- > -- David (obrien@NUXI.com) You argue like Tom Leykis. Because of that you've earned my respect. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 6:50:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F342515002 for ; Thu, 13 Jan 2000 06:50:09 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Jan 2000 14:49:47 +0000 (GMT) Date: Thu, 13 Jan 2000 14:49:46 +0000 From: David Malone To: Brad Knowles Cc: Gawel , "freebsd-stable@FreeBSD.ORG" Subject: Re: portmap Message-ID: <20000113144946.A84064@walton.maths.tcd.ie> References: <387DB3BB.8D85E624@sim.com.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Thu, Jan 13, 2000 at 01:07:54PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 01:07:54PM +0100, Brad Knowles wrote: > My understanding is that portmap uses UDP, which TCP-Wrappers > doesn't protect. tcpd has no problem protecting the first connection to UDP applications run from inetd. TCP wait services are a problem though. Programs which use libwrap directly don't have this restriction. > You can get an improved version of portmap that makes explicit > use of wraplib (I'd suggest starting with Wietse Venema's version). > I'd go to and start from there. FreeBSD's portmapper uses libwrap and so should have all the access controls Wietse's version has. (Infact, I think it uses his code). In response to the original posers problem of not wanting to see the log messages when connections are denied, one option would be to use the "severity" option in hosts.allow to log the messages at a different level/facility. > Or you can make use of kernel-level firewalling to prevent anyone > from successfully getting packets through to a particular port on > your machine, unless you want to let them through. Look at "man > ipfw" for starters. This is probably a more general solution to unwanted connections though. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 7:24:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tetron02.tetronsoftware.com (ftp.tetronsoftware.com [208.236.46.106]) by hub.freebsd.org (Postfix) with ESMTP id 965BE154B7 for ; Thu, 13 Jan 2000 07:24:36 -0800 (PST) (envelope-from zeus@tetronsoftware.com) Received: from tetron02.tetronsoftware.com (tetron02.tetronsoftware.com [208.236.46.106]) by tetron02.tetronsoftware.com (8.9.3/8.9.3) with ESMTP id JAA28399; Thu, 13 Jan 2000 09:27:57 -0600 (CST) (envelope-from zeus@tetronsoftware.com) Date: Thu, 13 Jan 2000 09:27:57 -0600 (CST) From: Gene Harris To: Gawel Cc: freebsd-stable@FreeBSD.ORG Subject: Re: portmap In-Reply-To: <387DB3BB.8D85E624@sim.com.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Gawel wrote: > Hello, > I 've got it several times: > portmap[16116]: connect from 195.31.252.2 to dump(): request from > unauthorized host. > It is harmless but annoying. > Is there any way to prevent portman listening requests on a NIC, ip, > etc. besides using hosts.allow? > > Thanks, > Gawel > > I hate to sound gummy, but do you want to stop the logging messages to the console, or do you want to stop portmapper from listening on your external NIC? If you want to stop the logging, try something like portmap: 10.0.0.0 : severity auth.crit : deny Then change your syslog.conf to not log auth.crit. I generally just use the following in my syslog.conf: auth.* /var/log/auth.log to redirect all auth logging to auth.log instead of messages. You'll need to adjust your syslog.conf to your tastes to determine what ends up on your console. If you want to just block port 111, then use ipfw, something like ipfw 10000 add unreachable host-unknown from any to xx.yy.zz.aa 111 via nic setup should do the trick. You'll need to change the xx.yy.zz.aa to your ip and nic to your external NIC. This little nasty sends a surprising ICMP 3,7 back to whomever is attempting to setup a connection to your portmapper. I hope this helps you solve your issue, *==========================================================* *Gene Harris http://www.tetronsoftware.com* *FreeBSD Novice * *==========================================================* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 7:39:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by hub.freebsd.org (Postfix) with ESMTP id A81EE14D2C; Thu, 13 Jan 2000 07:39:16 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 1579D1BE2; Thu, 13 Jan 2000 10:39:36 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14461.61878.761130.281219@anarcat.dyndns.org> Date: Thu, 13 Jan 2000 10:39:34 -0500 (EST) To: chad@DCFinc.com Cc: melange@yip.org (Bob K), msmith@FreeBSD.ORG, boing@boing.com, freebsd-stable@FreeBSD.ORG Subject: Re: [OT] DOS-in-ROM (was Re: fbsdboot.exe can't load elf kernels) References: <200001130128.SAA03644@freeway.dcfinc.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Reply-To: beaupran@iro.umontreal.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same here.. :)) I tried to run it as an X terminal, but the libs filled up the drive.. :)) The worst part is that I needed PicoBSD to install FreeBSD, as the install floppies/kernel were too big... --- Big Brother told Chad R. Larson to write, at 18:28 of January 12: > As I recall, Bob K wrote: > > Just as an aside, I spent all day today using an 80286 laptop with > > DOS-in-ROM (running TeleMate off a floppy). Now this has got me wondering > > if PicoBSD would run on that thing... > > Don't think so. The FreeBSD kernel needs 80386 hardware registers > and memory management at the minimum. > > On the other hand, I bought (flea market, $25) a Compaq 386/20 > laptop with an 80Mb hard drive and 4Mb of RAM. It boots and runs > FreeBSD. > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.net > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 9: 2:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by hub.freebsd.org (Postfix) with SMTP id DE9F114DBE for ; Thu, 13 Jan 2000 09:02:48 -0800 (PST) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 21485 invoked by alias); 13 Jan 2000 17:02:32 -0000 Received: (qmail 21479 invoked from network); 13 Jan 2000 17:02:32 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by amalthea.salford.ac.uk with SMTP; 13 Jan 2000 17:02:32 -0000 Received: (qmail 1017 invoked by uid 141); 13 Jan 2000 17:02:07 -0000 Date: Thu, 13 Jan 2000 17:02:07 +0000 (GMT) From: Mark Powell To: freebsd-stable@freebsd.org Subject: handle_workitem_freefile bug? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Setting up a new box as a mail server. Installed 3.4-R on it a couple of days ago. cvsupped to 3.4-S yesterday. Made world and kernel. Stress tested it and it seems stable. I have soft-updates turned on in the root fs. Was trying to copy it to another machine. Using tar in the root. However, just before I removed all the work directories from ports to make the tar file smaller: /usr/ports # find . -name work > /tmp/z I checked the file here /usr/ports # xargs rm -rf < /tmp/z This reduced the fs from 2.6GB to 800MB / # tar cvfl all.tar / interruped this and changed the flags / # tar cvpfl all.tar / This produced loads of: handle_workitem_freefile: got error 5 while accessing filesystem up the console. I interrupted the tar and tried to look at the fs. 'ls' produced a display which seemed similar to having the -R flag and, but I was just doing "ls -al". i.e. it recursed dirs, with complaints of I/O errors on lots of the directories. CTRL-ALT-DEL wouldn't bring the machine down, so I had to reset it. After the boot-up fsck all seemed okay. Any ideas what that was? Softupdate problems? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 9:51:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id C334214F16; Thu, 13 Jan 2000 09:51:26 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id JAA18465; Thu, 13 Jan 2000 09:47:05 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id JAA05236; Thu, 13 Jan 2000 09:46:59 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id JAA23621; Thu, 13 Jan 2000 09:45:47 -0800 (PST) Message-ID: <387E1075.6ADE62A5@softweyr.com> Date: Thu, 13 Jan 2000 10:50:45 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Marcin Cieslak Cc: Warner Losh , "Forrest W. Christian" , Mike Smith , Geff Hanoian , freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels (flash cards off topic) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcin Cieslak wrote: > > On Wed, 12 Jan 2000, Warner Losh wrote: > > > The linear flash cards don't have an ata interface, > > so PAO and soon -current won't recognize them. > > They don't have and we don't need it. > Once can easily read them with low-level pccardc interface. > In general, flash cards are not meant to be written too often, > so I belive we won't put a real filesystem on them. > Just a kernel and mfsroot image perhaps? Modern flash chips support on the order of 1,000,000 write cycles, so this is not such a concern anymore. There is no reason why we shouldn't put a filesystem on a flash card. A better choice might be the flash disk cards from SanDisk and others, since they do have an ATA interface and look like a small ATA drive to the pccard code. Unless the linear flash cards are a LOT less expensive, there isn't a lot of reason to do all the extra work. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 9:51:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 4CE3D15587; Thu, 13 Jan 2000 09:51:39 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 583C51C2B; Thu, 13 Jan 2000 12:49:13 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 539F23819; Thu, 13 Jan 2000 12:49:13 -0500 (EST) Date: Thu, 13 Jan 2000 12:49:13 -0500 (EST) From: Bill Fumerola To: Mikhail Teterin Cc: Stan Brown , stable@freebsd.org, brian@FreeBSD.org Subject: Re: IP Tunneling, is it possible? In-Reply-To: <200001131415.JAA05663@rtfm.newton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Mikhail Teterin wrote: > I love my PPP over SSH connection. Basicly, ppp on one machine invokes > ssh to login to the other side and start ``ppp -direct'' there. Once the > connection is up, both ends can route packets to/from the newly created > tun-interfaces enabling other machines on the LANs to see it all. ppp+ssh has some flaws to it. Performance can be choppy and the reason (If I'm pulling out of my memory banks what Brian told me at FreeBSDcon properly) is that there are so many layer, each with its own error correction, compression, etc that wierd bursts and such can happen. > This works perfect to get a normal connection through a one-way firewall > too, BTW. Which is the only reason I use it. An example of the wierdness. if I do a 'ls -l' in a large directory a certain amount of files will be displayed and then display will stop if I lay on the space bar, they'll start moving again. This is not a $PAGER issue (before anyone sends me the man page from more(1)), I believe it is a queueing bogon when you use so many layers. HTH, -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 10: 0:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 65C0014EFD; Thu, 13 Jan 2000 10:00:37 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id MAA52224; Thu, 13 Jan 2000 12:58:56 -0500 (EST) (envelope-from mi) Message-Id: <200001131758.MAA52224@misha.cisco.com> Subject: Re: IP Tunneling, is it possible? In-Reply-To: from Bill Fumerola at "Jan 13, 2000 12:49:13 pm" To: Bill Fumerola Date: Thu, 13 Jan 2000 12:58:56 -0500 (EST) Cc: Mikhail Teterin , Stan Brown , stable@freebsd.org, brian@freebsd.org Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola once wrote: > On Thu, 13 Jan 2000, Mikhail Teterin wrote: > > > I love my PPP over SSH connection. Basicly, ppp on one machine > > invokes ssh to login to the other side and start ``ppp -direct'' > > there. Once the connection is up, both ends can route packets > > to/from the newly created tun-interfaces enabling other machines on > > the LANs to see it all. > > ppp+ssh has some flaws to it. Performance can be choppy and the reason > (If I'm pulling out of my memory banks what Brian told me at > FreeBSDcon properly) is that there are so many layer, each with its > own error correction, compression, etc that wierd bursts and such can > happen. This is true. I enable compression in ssh, but disable it in PPP. Still, I suppose, it is imperfect. I'm wondering if changing the MTU/MRU will help (and in what direction). It does, however, completely emulate the net interface -- I can ftp, rsh, run X, etc. over such connection -- even rwhod works (must be started after the connction is established). > > This works perfect to get a normal connection through a one-way > > firewall too, BTW. > > Which is the only reason I use it. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 10:15:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 7DA1514E76 for ; Thu, 13 Jan 2000 10:15:35 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 128omQ-0002aP-00 for stable@freebsd.org; Thu, 13 Jan 2000 18:15:30 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id TAA36852 for ; Thu, 13 Jan 2000 19:15:27 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <387E163E.16722C62@scc.nl> Date: Thu, 13 Jan 2000 19:15:26 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: list.freebsd.emulation Cc: stable@freebsd.org Subject: Problems with linux_base-6.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Applies to: FreeBSD-stable I've gotten a number of reports of breakages caused by installing linux_base-6.1. The problem is not in the port itself, but in the linux kernel module and more specifically in the absent of the rt_sigsuspend syscall (syscall #179). I've just committed an implementation for the syscall. Please update your sources on the next suitable moment and recompile the kernel and/or linux kernel module. If there are still problems caused by using linux_base-6.1 instead of linux_base-5.2, post a description (as detailed as possible) of the problem to emulation@FreeBSD.org. Thanks, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 10:33:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B839A14F0C; Thu, 13 Jan 2000 10:33:01 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA44836; Thu, 13 Jan 2000 11:09:09 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA22848; Thu, 13 Jan 2000 11:09:36 -0700 (MST) Message-Id: <200001131809.LAA22848@harmony.village.org> To: Wes Peters Subject: Re: fbsdboot.exe can't load elf kernels (flash cards off topic) Cc: Marcin Cieslak , "Forrest W. Christian" , Mike Smith , Geff Hanoian , freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 13 Jan 2000 10:50:45 MST." <387E1075.6ADE62A5@softweyr.com> References: <387E1075.6ADE62A5@softweyr.com> Date: Thu, 13 Jan 2000 11:09:36 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <387E1075.6ADE62A5@softweyr.com> Wes Peters writes: : Modern flash chips support on the order of 1,000,000 write cycles, so this : is not such a concern anymore. There is no reason why we shouldn't put : a filesystem on a flash card. We weren't talking about modern flash cards :-). These flash cards have 10,000 to 100,000 write cycles per page. : A better choice might be the flash disk cards from SanDisk and others, : since they do have an ATA interface and look like a small ATA drive : to the pccard code. Unless the linear flash cards are a LOT less : expensive, there isn't a lot of reason to do all the extra work. That's why I've done support for the ata flash cards, but haven't yet done the linear flash cards. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 10:57:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B8F315002 for ; Thu, 13 Jan 2000 10:57:12 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 83B86E89D; Thu, 13 Jan 2000 13:57:10 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id NAA00539; Thu, 13 Jan 2000 13:57:10 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14462.8198.226435.916326@onceler.kcilink.com> Date: Thu, 13 Jan 2000 13:57:10 -0500 (EST) To: David Berard Cc: freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 In-Reply-To: <387DAF03.DFFDCE1@cybercable.tm.fr> References: <387DAF03.DFFDCE1@cybercable.tm.fr> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DB" == David Berard writes: DB> 2. modify the ppc entry in the kernel config file, and build a new DB> kernel DB> --- device ppc0 at isa? port? flags 0x40 net irq 7 DB> +++ device ppc0 at isa? port? flags 0x40 tty irq 7 Wow... this one does the trick for me! I no longer user the lptcontrol -p method. I was soooo close to buying a jet-direct card to drive this printer! It seems to me that the GENERIC file should have this updated, as that's the base from which I built my own config file. The LINT file has "tty" rather than "net", so someone must have forgotten to propagate the change. Has anyone filed a pr for this or should I do it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 11:37:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from math.udel.edu (math.udel.edu [128.175.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 6A3781529B for ; Thu, 13 Jan 2000 11:37:34 -0800 (PST) (envelope-from schwenk@math.udel.edu) Received: from math.udel.edu (sisyphus.math.udel.edu [128.175.16.167]) by math.udel.edu (8.9.3+Sun/8.9.1) with ESMTP id OAA16036; Thu, 13 Jan 2000 14:37:04 -0500 (EST) Message-ID: <387E2960.DDC1871C@math.udel.edu> Date: Thu, 13 Jan 2000 14:37:04 -0500 From: Peter Schwenk Organization: University of Delaware X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en, fr, de, ko MIME-Version: 1.0 To: Vivek Khera Cc: David Berard , freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 References: <387DAF03.DFFDCE1@cybercable.tm.fr> <14462.8198.226435.916326@onceler.kcilink.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same printing problem myself, and the reason I heard that they have the GENERIC kernel with 'net' on the ppc0 line is because it's needed for PLIP to work. The FreeBSD people want PLIP to work during installation. It would be nice if they could slip in an alternative kernel during the installation that didn't have 'net' compiled in. Or if the net vs. tty could be toggled with a sysctl command, that would be nice. Vivek Khera wrote: > >>>>> "DB" == David Berard writes: > > DB> 2. modify the ppc entry in the kernel config file, and build a new > DB> kernel > DB> --- device ppc0 at isa? port? flags 0x40 net irq 7 > DB> +++ device ppc0 at isa? port? flags 0x40 tty irq 7 > > Wow... this one does the trick for me! I no longer user the > lptcontrol -p method. I was soooo close to buying a jet-direct card > to drive this printer! > > It seems to me that the GENERIC file should have this updated, as > that's the base from which I built my own config file. The LINT file > has "tty" rather than "net", so someone must have forgotten to > propagate the change. > > Has anyone filed a pr for this or should I do it? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- PETER SCHWENK | UNIX System Administrator Department of Mathematical Sciences | University of Delaware schwenk@math.udel.edu | (302)831-0437 <-NEW!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 11:46:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id E0BC914FF1 for ; Thu, 13 Jan 2000 11:46:51 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 2E022E89D; Thu, 13 Jan 2000 14:46:51 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id OAA00871; Thu, 13 Jan 2000 14:46:51 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14462.11179.75027.675592@onceler.kcilink.com> Date: Thu, 13 Jan 2000 14:46:51 -0500 (EST) To: Peter Schwenk Cc: David Berard , freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 In-Reply-To: <387E2960.DDC1871C@math.udel.edu> References: <387DAF03.DFFDCE1@cybercable.tm.fr> <14462.8198.226435.916326@onceler.kcilink.com> <387E2960.DDC1871C@math.udel.edu> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "PS" == Peter Schwenk writes: PS> I had the same printing problem myself, and the reason I heard that they PS> have the GENERIC kernel with 'net' on the ppc0 line is because it's PS> needed for PLIP to work. The FreeBSD people want PLIP to work during PS> installation. It would be nice if they could slip in an alternative PS> kernel during the installation that didn't have 'net' compiled in. Or if PS> the net vs. tty could be toggled with a sysctl command, that would be PS> nice. A comment in GENERIC would also suffice, I think. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 13:21:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from node11a94.a2000.nl (node11a94.a2000.nl [24.132.26.148]) by hub.freebsd.org (Postfix) with SMTP id 963F614EFD for ; Thu, 13 Jan 2000 13:21:39 -0800 (PST) (envelope-from ronald@node11a94.a2000.nl) Received: (qmail 77626 invoked from network); 13 Jan 2000 21:21:33 -0000 Received: from dlanor.evertsen.nl (10.0.0.3) by node11a94.a2000.nl with SMTP; 13 Jan 2000 21:21:33 -0000 Date: Thu, 13 Jan 2000 22:21:32 +0100 (CET) From: Ronald Klop To: Vivek Khera Cc: Peter Schwenk , David Berard , freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 In-Reply-To: <14462.11179.75027.675592@onceler.kcilink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Vivek Khera wrote: > A comment in GENERIC would also suffice, I think. Hello, Maybe it's good to make an update of the man pages also. Man lpt gives the info about the old lpt device (before ppbus was introduced). Man nlpt gives info about the current (3.x-STABLE) lpt device. Everything discussed in this thread is explained in that page. Also that you should use 'controller ppc0 at isa? port? tty' in stead of 'controller ppc0 at isa? port? tty irq 7' for polled ports. With the first one you wil get messages about 'stray irq 7' is my experience. The old lpt device is now called olpt. Greetings, Ronald. PS: I had the trouble of interrupt-driven/polled ports with a HP LaserJet III a few months ago. -- Ronald Klop http://node11a94.a2000.nl/~ronald/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 13:28: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id CD37F150E2 for ; Thu, 13 Jan 2000 13:27:46 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 7140 invoked from network); 13 Jan 2000 21:27:44 -0000 Received: from userak75.uk.uudial.com (HELO marder-1.) (62.188.134.49) by smtp.dial.pipex.com with SMTP; 13 Jan 2000 21:27:44 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id VAA00535; Thu, 13 Jan 2000 21:27:42 GMT (envelope-from mark) Date: Thu, 13 Jan 2000 21:27:42 +0000 From: Mark Ovens To: stable@freebsd.org Cc: emulation@FreeBSD.org Subject: Re: Problems with linux_base-6.1 Message-ID: <20000113212742.A361@marder-1> References: <387E163E.16722C62@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <387E163E.16722C62@scc.nl> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 07:15:26PM +0100, Marcel Moolenaar wrote: > Applies to: FreeBSD-stable > > I've gotten a number of reports of breakages caused by installing > linux_base-6.1. The problem is not in the port itself, but in the linux > kernel module and more specifically in the absent of the rt_sigsuspend > syscall (syscall #179). I've just committed an implementation for the > syscall. Please update your sources on the next suitable moment and > recompile the kernel and/or linux kernel module. If there are still > problems caused by using linux_base-6.1 instead of linux_base-5.2, post > a description (as detailed as possible) of the problem to > emulation@FreeBSD.org. > I cvsup'd the sources and re-built my kernel *and* linux.ko. Now StarOffice5.1 segfaults rather than dying with "Invalid system call": Jan 13 21:19:25 marder-1 /kernel: pid 461 (soffice.bin), uid 0: exited on signal 11 (core dumped) > Thanks, > > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 13:30: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A1881559F for ; Thu, 13 Jan 2000 13:30:01 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 0F376E89D; Thu, 13 Jan 2000 16:30:00 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id QAA01907; Thu, 13 Jan 2000 16:30:00 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14462.17367.949655.971736@onceler.kcilink.com> Date: Thu, 13 Jan 2000 16:29:59 -0500 (EST) To: Ronald Klop Cc: freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 In-Reply-To: References: <14462.11179.75027.675592@onceler.kcilink.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "RK" == Ronald Klop writes: RK> On Thu, 13 Jan 2000, Vivek Khera wrote: >> A comment in GENERIC would also suffice, I think. RK> Hello, RK> Maybe it's good to make an update of the man pages also. RK> Man lpt gives the info about the old lpt device (before ppbus was RK> introduced). Man nlpt gives info about the current (3.x-STABLE) lpt RK> device. Everything discussed in this thread is explained in that page. Actually, I was looking at the man page for ppc and it says nothing about using "net" instead of "tty", so that probably could use an update as well. The synopsis actually only lists the "tty" variant. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 13:50:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from node11a94.a2000.nl (node11a94.a2000.nl [24.132.26.148]) by hub.freebsd.org (Postfix) with SMTP id 2DE6514E6D for ; Thu, 13 Jan 2000 13:50:44 -0800 (PST) (envelope-from ronald@node11a94.a2000.nl) Received: (qmail 77720 invoked from network); 13 Jan 2000 21:50:42 -0000 Received: from dlanor.evertsen.nl (10.0.0.3) by node11a94.a2000.nl with SMTP; 13 Jan 2000 21:50:42 -0000 Date: Thu, 13 Jan 2000 22:50:41 +0100 (CET) From: Ronald Klop To: Vivek Khera Cc: freebsd-stable@freebsd.org Subject: Re: parallel printer & nlpt0 In-Reply-To: <14462.17367.949655.971736@onceler.kcilink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Vivek Khera wrote: > >>>>> "RK" == Ronald Klop writes: > > RK> On Thu, 13 Jan 2000, Vivek Khera wrote: > > >> A comment in GENERIC would also suffice, I think. > > RK> Hello, > > RK> Maybe it's good to make an update of the man pages also. > RK> Man lpt gives the info about the old lpt device (before ppbus was > RK> introduced). Man nlpt gives info about the current (3.x-STABLE) lpt > RK> device. Everything discussed in this thread is explained in that page. > > Actually, I was looking at the man page for ppc and it says nothing > about using "net" instead of "tty", so that probably could use an > update as well. The synopsis actually only lists the "tty" variant. > But looking at 'man plip' wil show you the net option. But I agree, net is an option to ppc, so it should also be mentioned in that man page. Greetings, Ronald. -- Ronald Klop http://node11a94.a2000.nl/~ronald/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 15:40:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id D6049156DB for ; Thu, 13 Jan 2000 15:40:16 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA45681; Fri, 14 Jan 2000 10:40:05 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA24234; Fri, 14 Jan 2000 10:40:04 +1100 (EST) Message-Id: <200001132340.KAA24234@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Marcel Moolenaar Cc: stable@FreeBSD.ORG Subject: Re: Problems with linux_base-6.1 In-reply-to: Your message of Thu, 13 Jan 2000 19:15:26 +0100. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 10:40:04 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > kernel module and more specifically in the absent of the rt_sigsuspend > syscall (syscall #179). I've just committed an implementation for the > syscall. Which, btw, should be enough to run the Linux version of Railroad Tycoon II! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 15:45:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 05E5B14C3C; Thu, 13 Jan 2000 15:45:34 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id SAA13451; Thu, 13 Jan 2000 18:45:39 -0500 (EST) Date: Thu, 13 Jan 2000 18:45:39 -0500 (EST) From: "Mr. K." To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: process hung in ttywri Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I figured out how to reproduce the ttywri hang at will (I'm sure there are other ways, but this works for me 100%): 1) using SecureCRT and ssh2, ssh into your machine 2) run "find /" 3) click your mouse in the window and hold down. the scrolling will stop. hold this down for a few seconds. 4) let go of the mouse button, the buffer will flush and then the process will hang in ttywri: 2847 anthony 4 0 936K 620K ttywri 0:00 0.00% 0.00% find Since I can reproduce this at will, on both stable and current, if anyone wants me to reproduce it and give the results of something, let me know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 15:55:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 34F8C14DE2 for ; Thu, 13 Jan 2000 15:55:45 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000113235331.OQQN28811.mail.rdc3.on.home.com@tristan.net>; Thu, 13 Jan 2000 15:53:31 -0800 Content-Length: 1084 Message-ID: X-Mailer: XFMail 1.4.2 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, 13 Jan 2000 18:52:18 -0500 (EST) From: Colin To: Agent Drek Subject: Re: access floppy rw to lock system Cc: freebsd-stable@FreeBSD.ORG, "Chad R. Larson" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-2000 Agent Drek wrote: > On Wed, 12 Jan 2000, Chad R. Larson wrote: > >|As I recall, Agent Drek wrote: >|> >|> I have a repeatable problem on my FreeBSD-3.4Stable workstation. If >|> the floppy disk is physically tabbed as read-only and I mount it rw I >|> can then 'lock' the system up by using vim (to read a text-file on the >|> disk ... less had the same problem). Is this expected behaviour? I >|> did this from the console and could still between the virtual >|> consoles. The only way to get going again was to reboot. After that >|> happened twice I tabbed the disk writable and things were fine. >| >|I'd start by asking, "Why would you do that?" There are, oddly enough, occasionally reaons for things like floppies. That one could slip, unnoticed, into the drive write-protected...see where this is going? This is where I get concerned. Failure writing to a floppy shouldn't hang the system. That it does would imply a problem with the driver at the very least. Or am I failing to trip on the blatantly obvious here? cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 17:44:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 5AC6A14ED4 for ; Thu, 13 Jan 2000 17:44:30 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA07443; Thu, 13 Jan 2000 18:44:23 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001140144.SAA07443@freeway.dcfinc.com> Subject: Re: access floppy rw to lock system In-Reply-To: from Colin at "Jan 13, 0 06:52:18 pm" To: cwass99@home.com (Colin) Date: Thu, 13 Jan 2000 18:44:23 -0700 (MST) Cc: drek@MonsterByMistake.Com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Colin wrote: > > On 13-Jan-2000 Agent Drek wrote: > > On Wed, 12 Jan 2000, Chad R. Larson wrote: > > > >|As I recall, Agent Drek wrote: > >|> > >|> I have a repeatable problem on my FreeBSD-3.4Stable workstation. If > >|> the floppy disk is physically tabbed as read-only and I mount it rw I > >|> can then 'lock' the system up by using vim (to read a text-file on the > >|> disk ... less had the same problem). Is this expected behaviour? I > >|> did this from the console and could still between the virtual > >|> consoles. The only way to get going again was to reboot. After that > >|> happened twice I tabbed the disk writable and things were fine. > >| > >|I'd start by asking, "Why would you do that?" > > There are, oddly enough, occasionally reaons for things like floppies. > That one could slip, unnoticed, into the drive write-protected...see where this > is going? > This is where I get concerned. Failure writing to a floppy shouldn't hang > the system. That it does would imply a problem with the driver at the very > least. Or am I failing to trip on the blatantly obvious here? Well, I was protesting the logic of doing a read/write mount of read-only media. Mount it R/O and there is no issue. You wouldn't mount a CD-ROM read/write, would you? And, it would have to be "unnoticed" by someone with root permissions, or it can't be mounted at all (or written to, either). You don't let anyone other than the administrator(s) have root, do you? And you don't do day-to-day work as root, do you? But I will concede that doing that approximately silly thing shouldn't hang the system. I'd probably vote that the driver should test for write protect, and the mount(2) call should act as though "MT_RDONLY" had been specified. Either that, or fail with a EPERM or ENODEV. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 17:56:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-7-63.adsl.one.net [216.23.15.63]) by hub.freebsd.org (Postfix) with ESMTP id C5D9E14FB5 for ; Thu, 13 Jan 2000 17:56:18 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id UAA02529; Thu, 13 Jan 2000 20:59:00 -0500 (EST) (envelope-from cokane) Date: Thu, 13 Jan 2000 20:58:25 -0500 From: Coleman Kane To: Marcel Moolenaar Cc: freebsd-stable@freebsd.org Subject: Re: Problems with linux_base-6.1 Message-ID: <20000113205825.A2513@evil.2y.net> References: <387E163E.16722C62@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387E163E.16722C62@scc.nl>; from marcel@scc.nl on Thu, Jan 13, 2000 at 01:23:16PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, UnrealTournament plays now, but crashes out soon after loading a map, trynig to call non-present sched_setscheduler. Also, ptrace() is not listed as existing, so gdb won't work either. Quake3 still crashes, and doesn't do anything. --cokane Marcel Moolenaar had the audacity to say: > Applies to: FreeBSD-stable > > I've gotten a number of reports of breakages caused by installing > linux_base-6.1. The problem is not in the port itself, but in the linux > kernel module and more specifically in the absent of the rt_sigsuspend > syscall (syscall #179). I've just committed an implementation for the > syscall. Please update your sources on the next suitable moment and > recompile the kernel and/or linux kernel module. If there are still > problems caused by using linux_base-6.1 instead of linux_base-5.2, post > a description (as detailed as possible) of the problem to > emulation@FreeBSD.org. > > Thanks, > > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 18: 8:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wit401310.student.utwente.nl (wit401310.student.utwente.nl [130.89.236.150]) by hub.freebsd.org (Postfix) with ESMTP id BBE3414C40 for ; Thu, 13 Jan 2000 18:08:36 -0800 (PST) (envelope-from dalroi@wit401310.student.utwente.nl) Received: from wit401310.student.utwente.nl (localhost [127.0.0.1]) by wit401310.student.utwente.nl (Postfix) with ESMTP id 2B4481ECF; Fri, 14 Jan 2000 03:08:38 +0100 (CET) Date: Fri, 14 Jan 2000 03:08:37 +0100 (CET) From: Alban Hertroys Subject: Re: Problems with linux_base-6.1 To: Coleman Kane Cc: Marcel Moolenaar , freebsd-stable@freebsd.org In-Reply-To: <20000113205825.A2513@evil.2y.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20000114020838.2B4481ECF@wit401310.student.utwente.nl> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Jan, Coleman Kane wrote: > Hi, UnrealTournament plays now, but crashes out soon after loading a map, trynig > to call non-present sched_setscheduler. Also, ptrace() is not listed as > existing, so gdb won't work either. Quake3 still crashes, and doesn't do > anything. > --cokane Enable the POSIX thread support in your kernel. That supports sched_setscheduler AFAIK. -- Alban Hertroys http://wit401310.student.utwente.nl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This person has performed an illegal operation and will be shot down. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 18:47: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id BFB271505E for ; Thu, 13 Jan 2000 18:47:01 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with SMTP id TAA03994; Thu, 13 Jan 2000 19:44:20 -0700 (MST) Date: Thu, 13 Jan 2000 19:44:20 -0700 (MST) From: "Forrest W. Christian" To: "Chad R. Larson" Cc: Colin , drek@MonsterByMistake.Com, freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system In-Reply-To: <200001140144.SAA07443@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Chad R. Larson wrote: > Well, I was protesting the logic of doing a read/write mount of read-only > media. Mount it R/O and there is no issue. > And, it would have to be "unnoticed" by someone with root > permissions, or it can't be mounted at all (or written to, either). I don't know about you, but I'm not sure how many times I've tried to write to a write-protected disk, or in other words, didn't realize the disk was write protected. It's just not one of the things I normally check when I put a disk in a drive.B > But I will concede that doing that approximately silly thing > shouldn't hang the system. I'd probably vote that the driver should > test for write protect, and the mount(2) call should act as though > "MT_RDONLY" had been specified. Exactly. If it's read-only media, it should fail when being mounted read-write, or default to ro. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 18:59:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 37E8414EE1; Thu, 13 Jan 2000 18:59:03 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id VAA44565; Thu, 13 Jan 2000 21:58:59 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id VAA07298; Thu, 13 Jan 2000 21:58:58 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001140258.VAA07298@rtfm.newton> Subject: Re: Problems with linux_base-6.1 In-Reply-To: <20000114020838.2B4481ECF@wit401310.student.utwente.nl> from Alban Hertroys at "Jan 14, 2000 03:08:37 am" To: Alban Hertroys Date: Thu, 13 Jan 2000 21:58:58 -0500 (EST) Cc: Coleman Kane , Marcel Moolenaar , freebsd-stable@freebsd.org, ports@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Hi, UnrealTournament plays now, but crashes out soon after loading a => map, trynig to call non-present sched_setscheduler. Also, ptrace() is => not listed as existing, so gdb won't work either. Quake3 still => crashes, and doesn't do anything. Meanwhile, the existing linux_base port should be renamed to linux_base-6 and modified to test for the OS version and declare itself broken if there is no support for the features it uses. The earlier version should be restored under the default name of linux_base, for that's what will work with much earlier releases. That's my humble opinion. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 20:26:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.monsterbymistake.com (monsterbymistake.com [205.207.163.17]) by hub.freebsd.org (Postfix) with ESMTP id C5ED714EBA for ; Thu, 13 Jan 2000 20:26:20 -0800 (PST) (envelope-from drek@MonsterByMistake.Com) Received: from bunny.monsterbymistake.com([205.207.163.17]) (1956 bytes) by mail.monsterbymistake.com via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Thu, 13 Jan 2000 23:26:52 -0500 (EST) (Smail-3.2.0.107 1999-Sep-8 #1 built 1999-Sep-11) Date: Thu, 13 Jan 2000 23:26:51 -0500 (EST) From: Agent Drek To: "Forrest W. Christian" Cc: "Chad R. Larson" , Colin , freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Forrest W. Christian wrote: |> But I will concede that doing that approximately silly thing |> shouldn't hang the system. I'd probably vote that the driver should |> test for write protect, and the mount(2) call should act as though |> "MT_RDONLY" had been specified. | |Exactly. If it's read-only media, it should fail when being mounted |read-write, or default to ro. | |- Forrest W. Christian (forrestc@imach.com) KD7EHZ |---------------------------------------------------------------------- |iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com |Solutions for your high-tech problems. (406)-442-6648 |---------------------------------------------------------------------- | This is what I thought would have been 'correct' behaviour and which is why I asked on this list (my feeble mail list searches turned up nothing) FYI: I have been informed that this is no longer an issue in 4.0 due to a rewrite of the driver. Cheers to all who code those things! P. doctor it hurts bad when I do this! D. don't do that then ... next please. thanks, =derek Monster By Mistake Inc > 'digital plumber' http://www.interlog.com/~drek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 20:27:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 7D96814EBA for ; Thu, 13 Jan 2000 20:27:13 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 128yKO-000GP2-00 for freebsd-stable@freebsd.org; Thu, 13 Jan 2000 20:27:12 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: user mode ppp error with windoze Message-Id: Date: Thu, 13 Jan 2000 20:27:12 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anyone recognize the two warnings? Jan 13 17:30:37 ppp[20059]: Phase: Using interface: tun0 Jan 13 17:30:37 ppp[20059]: Phase: deflink: Created in closed state Jan 13 17:30:37 ppp[20059]: Warning: timeout: Invalid command Jan 13 17:30:37 ppp[20059]: Warning: timeout: Failed 1 Jan 13 17:30:37 ppp[20059]: Phase: PPP Started (direct mode). Jan 13 17:30:37 ppp[20059]: Phase: bundle: Establish it's an inbound ppp from a win98 system, and they get a loong, like one minute, pause. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 20:41:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-7-22.adsl.one.net [216.23.15.22]) by hub.freebsd.org (Postfix) with ESMTP id 222C014DCB for ; Thu, 13 Jan 2000 20:41:15 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id XAA00421; Thu, 13 Jan 2000 23:43:59 -0500 (EST) (envelope-from cokane) Date: Thu, 13 Jan 2000 23:43:54 -0500 From: Coleman Kane To: Alban Hertroys Cc: Coleman Kane , Marcel Moolenaar , freebsd-stable@freebsd.org Subject: Re: Problems with linux_base-6.1 Message-ID: <20000113234354.A405@evil.2y.net> References: <20000113205825.A2513@evil.2y.net> <20000114020838.2B4481ECF@wit401310.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000114020838.2B4481ECF@wit401310.student.utwente.nl>; from dalroi@wit401310.student.utwente.nl on Thu, Jan 13, 2000 at 09:09:44PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is that the POSIX scheduling and all the POSIX_* options in LINT? I just did that, and it still crashes, but this time it doesn't give me the undefined func. message. --cokane Alban Hertroys had the audacity to say: > > On 13 Jan, Coleman Kane wrote: > > Hi, UnrealTournament plays now, but crashes out soon after loading a map, trynig > > to call non-present sched_setscheduler. Also, ptrace() is not listed as > > existing, so gdb won't work either. Quake3 still crashes, and doesn't do > > anything. > > --cokane > > Enable the POSIX thread support in your kernel. That supports > sched_setscheduler AFAIK. > > -- > Alban Hertroys http://wit401310.student.utwente.nl > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > This person has performed an illegal operation > and will be shot down. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 21: 5:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 7AAA5151B6 for ; Thu, 13 Jan 2000 21:05:10 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA47046; Fri, 14 Jan 2000 16:05:02 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA07620; Fri, 14 Jan 2000 16:05:01 +1100 (EST) Message-Id: <200001140505.QAA07620@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Agent Drek Cc: "Forrest W. Christian" , "Chad R. Larson" , Colin , freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system In-reply-to: Your message of Thu, 13 Jan 2000 23:26:51 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 16:05:01 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > |Exactly. If it's read-only media, it should fail when being mounted > |read-write, or default to ro. Even this is not enough. PC floppy hardware doesn't have a "lock media" function, so you can get the same panic by changing a floppy for a write-protected one while it is mounted. I suspect that this hardware-induced inability to usefully cover all the bases, along with some more fundamental structural changes that are happening in -CURRENT, are why this hasn't been solved more gracefully for -STABLE yet. Until then: "Don't do that!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 13 21:49:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 284DB14D68 for ; Thu, 13 Jan 2000 21:49:54 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id WAA08193; Thu, 13 Jan 2000 22:49:36 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001140549.WAA08193@freeway.dcfinc.com> Subject: Re: access floppy rw to lock system In-Reply-To: <200001140505.QAA07620@lightning.itga.com.au> from Gregory Bond at "Jan 14, 0 04:05:01 pm" To: gnb@itga.com.au (Gregory Bond) Date: Thu, 13 Jan 2000 22:49:36 -0700 (MST) Cc: drek@MonsterByMistake.Com, forrestc@iMach.com, cwass99@home.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Gregory Bond wrote: >> Exactly. If it's read-only media, it should fail when being mounted >> read-write, or default to ro. > > Even this is not enough. PC floppy hardware doesn't have a "lock > media" function, so you can get the same panic by changing a floppy > for a write-protected one while it is mounted. But PC floppy hardware =does= have a "media changed" function. So, same deal. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 0: 5:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from borg-cube.com (226-193.adsl2.avtel.net [207.71.226.193]) by hub.freebsd.org (Postfix) with ESMTP id 25F34151BB; Fri, 14 Jan 2000 00:05:21 -0800 (PST) (envelope-from dburr@pobox.com) Received: from locutus.collective.borg-cube.com (dburr@locutus.collective.borg-cube.com [192.168.0.1]) by borg-cube.com (8.9.3/8.9.3) with ESMTP id AAA34848; Fri, 14 Jan 2000 00:05:20 -0800 (PST) (envelope-from dburr@pobox.com) Date: Fri, 14 Jan 2000 00:05:11 -0800 (PST) From: Donald Burr To: FreeBSD Questions Cc: FreeBSD Stable Subject: Any chance at supporting writing to ATAPI CD-R/RW at >2X? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running FreeBSD 3.4-STABLE on a Dual PII/400, Tyan Tiger 100A S1833DL motherboard, 256MB RAM, 2 x IBM DDRS-39130D 9.1 GB Ultra2 LVD SCSI HD. CD-RW is ATAPI, HP CD-Writer Plus 8210i I noticed while browsing through the wormcontrol(8) man page that the 'prepdisk' command takes arguments 'single' or 'double', meaning that you can only write disks in 1x and 2x speeds. Is there any chance of getting support for >2X CD-R/RW's? I have a HP 8210i which writes and rewrites at 4x, and I would really love to have the extra writing speed. And 8X writers are getting cheaper and cheaper... Thanks! -- Donald Burr Resistance is Futile! | FreeBSD: The WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 1:51:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id CD52414D8B; Fri, 14 Jan 2000 01:51:36 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id LAA75735; Fri, 14 Jan 2000 11:55:56 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 14 Jan 2000 11:55:55 +0200 (EET) From: Adrian Penisoara To: Sheldon Hearn Cc: Trond Endrestol , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <9039.947589746@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, 11 Jan 2000, Sheldon Hearn wrote: > Not until someone can explain how making /var/tmp a symlink to /tmp is > sensible, given that /var/tmp is documented as containing "temporary > files that are kept between system reboots" (see hier(7)). > > So basically, no. :-) Then let's get the other way around (change in /etc/rc): # Recover vi editor files. -find /var/tmp/vi.recover ! -type f -a ! -type d -delete +if [ -d /var/tmp/vi.recover ]; then + find /var/tmp/vi.recover ! -type f -a ! -type d -delete +fi vibackup=`echo /var/tmp/vi.recover/vi.*` if [ "$vibackup" != '/var/tmp/vi.recover/vi.*' ]; then echo 'Recovering vi editor sessions' And don't worry about loosing /var/tmp/vi.recover every time you reboot (unless you really care about loosing the abillity to recover vi edits between reboots) -- the first time you run vi it will recreate this directory. And let me notice that the original script assumes existence of this directory whereas if I don't run vi I won't get one... I use this small hack to get around the ugly error message I get every time I boot with MFS mounted /var/tmp -- suited me well until now. > > Ciao, > Sheldon. > Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 1:57:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F62715145 for ; Fri, 14 Jan 2000 01:57:19 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id LAA75808; Fri, 14 Jan 2000 11:59:47 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 14 Jan 2000 11:59:46 +0200 (EET) From: Adrian Penisoara To: Alexander Langer Cc: Sheldon Hearn , Uwe Laverenz , freebsd-stable@FreeBSD.ORG Subject: Re: 3.x to current not possible? In-Reply-To: <20000111172310.B8348@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, 11 Jan 2000, Alexander Langer wrote: > Thus spake Sheldon Hearn (sheldonh@uunet.co.za): > > > Perhaps you'd like to post the actual error messages you get when > > you try to upgrade to CURRENT? If so, please post them to the > > freebsd-current mailing list. > > Also, he should read /usr/src/UPGRADING Which, last I knew, it's no longer maintained and is empty right now (at least for RELENG_3 branch). Anyone care to take the job ? I might take it, but I know myself to be rather busy most of the time... > > > Alex > > -- > I doubt, therefore I might be. > Or maybe not ;-) Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 1:59:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 8CC041512A; Fri, 14 Jan 2000 01:59:29 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1293VK-0000Om-00; Fri, 14 Jan 2000 11:58:50 +0200 From: Sheldon Hearn To: Adrian Penisoara Cc: Trond Endrestol , FreeBSD stable , FreeBSD current Reply-To: freebsd-chat@freebsd.org Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Fri, 14 Jan 2000 11:55:55 +0200." Date: Fri, 14 Jan 2000 11:58:50 +0200 Message-ID: <1535.947843930@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let's try not to cross-post this any more, eh? On Fri, 14 Jan 2000 11:55:55 +0200, Adrian Penisoara wrote: > Then let's get the other way around (change in /etc/rc): No, you're missing the point. /var/tmp is expected to survive reboots. That's its definition according to the hier(7) manual page. If you choose to break that functionality, don't expect anyone to make gratuitous changes to the FreeBSD startup scripts to support your oddball configuration. :-) > And let me notice that the original script assumes existence of this > directory whereas if I don't run vi I won't get one... It does so because of the definition of /var/tmp . > I use this small hack to get around the ugly error message I get every > time I boot with MFS mounted /var/tmp -- suited me well until now. You shouldn't be mounting /var/tmp in MFS, because a memory file system does not survive a reboot -- that's where you've gone wrong. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 2: 2: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3302.mail.yahoo.com (web3302.mail.yahoo.com [204.71.201.25]) by hub.freebsd.org (Postfix) with SMTP id A80E814D11 for ; Fri, 14 Jan 2000 02:02:07 -0800 (PST) (envelope-from xu_xiao_hui@yahoo.com) Message-ID: <20000114100207.12217.qmail@web3302.mail.yahoo.com> Received: from [202.101.31.155] by web3302.mail.yahoo.com; Fri, 14 Jan 2000 02:02:07 PST Date: Fri, 14 Jan 2000 02:02:07 -0800 (PST) From: Xiaohui Xu To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 5b975154 subscribe freebsd-stable xu_xiao_hui@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 2: 7:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 44BEB14A13; Fri, 14 Jan 2000 02:07:36 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id LAA20279; Fri, 14 Jan 2000 11:07:24 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Fri, 14 Jan 2000 11:07:23 +0100 (CET) From: Trond Endrestol To: Sheldon Hearn Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Sheldon Hearn wrote: > Not until someone can explain how making /var/tmp a symlink to /tmp is > sensible, given that /var/tmp is documented as containing "temporary > files that are kept between system reboots" (see hier(7)). > > So basically, no. :-) I chose to use MFS for /tmp and symlinking /var/tmp and /usr/tmp to /tmp for sake of speed. No disk activity is involved when the temporary files on the MFS are in use. (This slightly false if the MFS is paged out or swapped out completely.) If I want something preserved between reboots, I'll use /var/otmp which is the original /var/tmp or my own ~/tmp directory. ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.4 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 2:10:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 512C9155A4; Fri, 14 Jan 2000 02:10:14 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1293g3-0000T7-00; Fri, 14 Jan 2000 12:09:55 +0200 From: Sheldon Hearn To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Reply-To: chat@FreeBSD.org Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Fri, 14 Jan 2000 11:07:23 +0100." Date: Fri, 14 Jan 2000 12:09:55 +0200 Message-ID: <1804.947844595@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000 11:07:23 +0100, Trond Endrestol wrote: > If I want something preserved between reboots, I'll use /var/otmp > which is the original /var/tmp or my own ~/tmp directory. Do whatever grooves your plumes, just don't expect the startup scripts to be hacked around to support your disregard for the hier(7) manual page. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 3:16:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from eastwood.aldigital.algroup.co.uk (eastwood.aldigital.algroup.co.uk [194.128.162.193]) by hub.freebsd.org (Postfix) with ESMTP id 65FCA14EFC; Fri, 14 Jan 2000 03:16:20 -0800 (PST) (envelope-from adam@algroup.co.uk) Received: from algroup.co.uk ([193.195.56.225]) by eastwood.aldigital.algroup.co.uk (8.8.8/8.6.12) with ESMTP id LAA00304; Fri, 14 Jan 2000 11:16:12 GMT Message-ID: <387F057A.1B111CC5@algroup.co.uk> Date: Fri, 14 Jan 2000 11:16:10 +0000 From: Adam Laurie Organization: A.L. Group plc X-Mailer: Mozilla 4.07 [en] (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: Dag-Erling Smorgrav , cjclark@home.com, stable@freebsd.org Subject: Re: console disappears after reboot References: <200001131158.DAA01817@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > So in summary; there's nothing that will "decide there is no built-in > console" unless you explicitly tell it to go look for itself. Anything > that's causing the system to talk to a serial console is at the admin's > request. At this point in time, there is no way to force a change of > console once the system is up and running. *, Thanks for all helpful suggestions... It turns out to be a mobo thing - the SBCs we are now using act like notebooks and switch off the VGA port, not the O/S... Apologies for waste of [insert unit of geek here]... cheers, Adam -- Adam Laurie Tel: +44 (181) 742 0755 A.L. Digital Ltd. Fax: +44 (181) 742 5995 Voysey House Barley Mow Passage http://www.aldigital.co.uk London W4 4GB mailto:adam@algroup.co.uk UNITED KINGDOM PGP key on keyservers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 3:23:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 9651715208 for ; Fri, 14 Jan 2000 03:23:52 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id DAA19987; Fri, 14 Jan 2000 03:23:43 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA78188; Fri, 14 Jan 2000 03:23:24 -0800 (PST) To: Marcel Moolenaar Cc: stable@freebsd.org Subject: Re: Problems with linux_base-6.1 References: <387E163E.16722C62@scc.nl> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 14 Jan 2000 03:23:21 -0800 In-Reply-To: Marcel Moolenaar's message of "Thu, 13 Jan 2000 19:15:26 +0100" Message-ID: Lines: 18 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Marcel Moolenaar * I've gotten a number of reports of breakages caused by installing * linux_base-6.1. The problem is not in the port itself, but in the linux * kernel module and more specifically in the absent of the rt_sigsuspend * syscall (syscall #179). I've just committed an implementation for the * syscall. Please update your sources on the next suitable moment and * recompile the kernel and/or linux kernel module. If there are still * problems caused by using linux_base-6.1 instead of linux_base-5.2, post * a description (as detailed as possible) of the problem to * emulation@FreeBSD.org. I don't assume the kernel can be safely loaded on older release kernels to get the desired effect? In that case, I can't put them in the upgrade kits, can you modify the port to check ${OSVERSION} and exit with a message if the user's system is too old? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 4:20: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 3A3DA155A4 for ; Fri, 14 Jan 2000 04:19:58 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/2000011400) with ESMTP id NAA19827 for ; Fri, 14 Jan 2000 13:19:55 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id NAA10096 for ; Fri, 14 Jan 2000 13:19:53 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:R+iHD76L9LzU3qHps1uJEFCJ199AigD2@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/8.9.1/wjp-SVR4/1998063000) with ESMTP id NAA26003 for ; Fri, 14 Jan 2000 13:19:51 +0100 (CET) Message-Id: <200001141219.NAA26003@wurzelausix.cs.uni-sb.de> Date: Fri, 14 Jan 2000 13:19:47 +0100 (CET) From: Alexander Leidinger Subject: dmesg broken after update? To: stable@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've cvsup-ed today around 8:40 CET from 3.3 to 3.4, made world, kernel, mergemastered and rebooted. Now I get: ---snip--- (114) root@ttyp0 # dmesg dmesg: namelist: msgbufp not found ---snip--- I didn't see any other strange behavior (at the moment), but I have a bad feeling about this dmesg thing. Does somebody else sees this? Should I be concerned about it or is this just a harmless "cvsup in the middle of a not very important commit"? Bye, Alexander. -- Actually, a more important date is January 1, 2000, when many computer programs across the world could break. Richard W. Stevens, Advanced Programming in the UNIX Environment, _1993_ http://netchild.home.pages.de A.Leidinger @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 4:40:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 945A1155E4 for ; Fri, 14 Jan 2000 04:40:02 -0800 (PST) (envelope-from talon@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.9.3/jtpda-5.3.2) with ESMTP id NAA75023 for ; Fri, 14 Jan 2000 13:39:55 +0100 (CET) Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id NAA21143 for ; Fri, 14 Jan 2000 13:39:55 +0100 (MET) Received: from (talon@localhost) by niobe.lpthe.jussieu.fr (8.9.3/jtpda-5.3.1) id NAA97366 for freebsd-stable@FreeBSD.ORG; Fri, 14 Jan 2000 13:39:54 +0100 (CET) Date: Fri, 14 Jan 2000 13:39:54 +0100 From: Michel TALON To: freebsd-stable@FreeBSD.ORG Subject: Re: parallel printer & nlpt0 Message-ID: <20000114133954.A96965@lpthe.jussieu.fr> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <14462.17367.949655.971736@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from ronald@node11a94.a2000.nl on Thu, Jan 13, 2000 at 10:50:41PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 10:50:41PM +0100, Ronald Klop wrote: > On Thu, 13 Jan 2000, Vivek Khera wrote: > > > >>>>> "RK" == Ronald Klop writes: > > > > RK> On Thu, 13 Jan 2000, Vivek Khera wrote: > > > > >> A comment in GENERIC would also suffice, I think. > > > > RK> Hello, > > > > RK> Maybe it's good to make an update of the man pages also. > > RK> Man lpt gives the info about the old lpt device (before ppbus was > > RK> introduced). Man nlpt gives info about the current (3.x-STABLE) lpt > > RK> device. Everything discussed in this thread is explained in that page. > > > > Actually, I was looking at the man page for ppc and it says nothing > > about using "net" instead of "tty", so that probably could use an > > update as well. The synopsis actually only lists the "tty" variant. > > > > But looking at 'man plip' wil show you the net option. But I agree, net > is an option to ppc, so it should also be mentioned in that man page. And moreover the significance of the flags tty and net is explained in man splnet. A reference to that page would be nice in man ppbus. -- Michel TALON To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 5:17:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hermes.mixx.net (concorde.mixx.net [212.84.196.2]) by hub.freebsd.org (Postfix) with ESMTP id C96C314EFD for ; Fri, 14 Jan 2000 05:17:12 -0800 (PST) (envelope-from news-list.freebsd.stable@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (Postfix) with ESMTP id 5710F16D804 for ; Fri, 14 Jan 2000 14:16:10 +0100 (CET) Received: by mate.bln.innominate.de (Postfix, from userid 9) id B8B502CA6B; Fri, 14 Jan 2000 13:48:17 +0100 (CET) From: news-list.freebsd.stable@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.stable Subject: Re: vinum problem Date: 14 Jan 2000 12:48:14 GMT Organization: innominate AG, Berlin, Germany Lines: 17 Message-ID: References: <20000110111833.E83528@enteract.com> Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 947854094 12175 10.0.0.13 (14 Jan 2000 12:48:14 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/pre-1.4-19990805 ("Preacher Man") (UNIX) (FreeBSD/4.0-CURRENT (i386)) To: stable@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jim C. Nasby" wrote: > Which devices is it complaining about? I found it very easy to accidentally > refer to the character/block devices (ie: /dev/vinum/raid0) at times during > vinum setup instead of the raw devices (ie: /dev/vinum/rraid0). This will > definitely cause some odd problems. I don't remember the step offhand where > you have to use the raw device (newfs?), but if you used the block device > instead you'll have to rebuild your vinum setup. no - that it was'nt t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 6:46:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id DCF3E14D4C; Fri, 14 Jan 2000 06:46:23 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id QAA81980; Fri, 14 Jan 2000 16:51:31 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 14 Jan 2000 16:51:31 +0200 (EET) From: Adrian Penisoara To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <1535.947843930@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 14 Jan 2000, Sheldon Hearn wrote: > > > Let's try not to cross-post this any more, eh? I believe the suggested change interests both branches; -chat removed. > > On Fri, 14 Jan 2000 11:55:55 +0200, Adrian Penisoara wrote: > > > Then let's get the other way around (change in /etc/rc): > > No, you're missing the point. /var/tmp is expected to survive reboots. > That's its definition according to the hier(7) manual page. If you > choose to break that functionality, don't expect anyone to make > gratuitous changes to the FreeBSD startup scripts to support your > oddball configuration. :-) > > > And let me notice that the original script assumes existence of this > > directory whereas if I don't run vi I won't get one... > > It does so because of the definition of /var/tmp . > > > I use this small hack to get around the ugly error message I get every > > time I boot with MFS mounted /var/tmp -- suited me well until now. > > You shouldn't be mounting /var/tmp in MFS, because a memory file system > does not survive a reboot -- that's where you've gone wrong. I'm not discussing the definition of /var/tmp ! I just recognise that lots of people (including me) step over this rule (as they don't need those bits to survive reboots, for example) and they MFS mount /var/tmp (at least) for the sake of optimizing compile times (cc uses /var/tmp for temporary files). So that makes us otlaws but this doesn't change the facts... All I want is not to assume existence of /var/tmp/vi.recover in /etc/rc. Because this is a simple hack that by _no chance_ breakes any set rules I believe it to be very good commit candidate. Anyone care to do it ? > > Ciao, > Sheldon. > Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 7: 2:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 39D6A14F6E; Fri, 14 Jan 2000 07:02:42 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id RAA82346; Fri, 14 Jan 2000 17:07:52 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 14 Jan 2000 17:07:51 +0200 (EET) From: Adrian Penisoara To: Trond Endrestol Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <1804.947844595@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 14 Jan 2000, Sheldon Hearn wrote: > > > On Fri, 14 Jan 2000 11:07:23 +0100, Trond Endrestol wrote: > > > If I want something preserved between reboots, I'll use /var/otmp > > which is the original /var/tmp or my own ~/tmp directory. > > Do whatever grooves your plumes, just don't expect the startup scripts > to be hacked around to support your disregard for the hier(7) manual > page. :-) Like I said, my hack doesn't contradict what hier(7) sais. It's 100% compatible ;-) ! Seriously now, I don't see why you hate so much the ideea of making some (most ?) people's life easier without breaking what's already been set... If it would really break things up then I would agree with you (indeed, the inital proposed chage, symlinking /var/tmp, is just a dirty workaround). > > Ciao, > Sheldon. > Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 7:13: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 2AB1F14C40; Fri, 14 Jan 2000 07:12:59 -0800 (PST) (envelope-from khera@kciLink.com) Received: by kci.kciLink.com (Postfix, from userid 100) id 6F6D3E89D; Fri, 14 Jan 2000 10:12:54 -0500 (EST) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14463.15606.393166.953233@kci.kciLink.com> Date: Fri, 14 Jan 2000 10:12:54 -0500 (EST) To: Trond Endrestol Cc: Sheldon Hearn , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 7) "Biscayne" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "TE" == Trond Endrestol writes: TE> I chose to use MFS for /tmp and symlinking /var/tmp and /usr/tmp to TE> /tmp for sake of speed. TE> No disk activity is involved when the temporary files on the MFS are TE> in use. (This slightly false if the MFS is paged out or swapped out TE> completely.) If vi.recover is not going to survive a reboot, why bother having it at all? That's is sole purpose for existing. If you don't like the warning, just delete the recovery procedure rather than creating the directory. It does no good for you to try to recover something that will never be there. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 7:20:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2D5B614E30; Fri, 14 Jan 2000 07:20:09 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1298VX-0001pa-00; Fri, 14 Jan 2000 17:19:23 +0200 From: Sheldon Hearn To: Vivek Khera Cc: Adrian Penisoara , Trond Endrestol , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-reply-to: Your message of "Fri, 14 Jan 2000 10:12:54 EST." <14463.15606.393166.953233@kci.kciLink.com> Date: Fri, 14 Jan 2000 17:19:23 +0200 Message-ID: <7041.947863163@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000 10:12:54 EST, Vivek Khera wrote: > If you don't like the warning, just delete the recovery procedure > rather than creating the directory. It does no good for you to try to > recover something that will never be there. Exactly. The only thing that comes out of this patch is we support an administrative mistake that leads naive users to believe that vi recovery on reboot is going to work as expected. This is a stupid idea. I wish the person who came up with it would just acknowledge that he's doing something inappropriate and move on, rather than insisting that the rest of us introduce a bad idea into our systems to support his bad practice. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 7:44:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from p1fed3.frb.org (p1fed3.frb.org [151.198.183.196]) by hub.freebsd.org (Postfix) with ESMTP id 5AE1414CF1 for ; Fri, 14 Jan 2000 07:44:09 -0800 (PST) (envelope-from seth@freebie.dp.ny.frb.org) Received: by p1fed3.frb.org; id KAA19058; Fri, 14 Jan 2000 10:43:40 -0500 (EST) Message-Id: <200001141543.KAA19058@p1fed3.frb.org> Received: from (10.0.0.1) by p1fed3.frb.org via smap (3.2) id xma019025; Fri, 14 Jan 00 10:43:20 -0500 Received: by relay2.frb.org; Fri, 14 Jan 2000 10:43:19 -0500 (EST) Received: by relay.frb.org; Fri, 14 Jan 00 10:43:09 -0500 Received: by mail.frb.org; Fri, 14 Jan 2000 10:42:16 -0500 (EST) Date: Fri, 14 Jan 2000 10:43:01 -0500 From: Seth Subject: Re: 3.x to current not possible? In-reply-to: <200001140958.DAA20490@p3smtp.frb.org>; from ady@warpnet.ro on Fri, Jan 14, 2000 at 11:59:46AM +0200 To: Adrian Penisoara Cc: Alexander Langer , Sheldon Hearn , Uwe Laverenz , freebsd-stable@FreeBSD.ORG, saper@system.pl MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000111172310.B8348@cichlids.cichlids.com> <200001140958.DAA20490@p3smtp.frb.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're working on it. Marcin Cieslak and I are collaborating in an effort to keep -STABLE's UPDATING file up-to-date. Details are still being worked out at this time, though. Stay tuned. Note that this doesn't help -CURRENT yet... but I'm not even sure it has an issue. Seth. On Fri, Jan 14, 2000 at 11:59:46AM +0200, Adrian Penisoara wrote: > Hi, > > On Tue, 11 Jan 2000, Alexander Langer wrote: > > > Thus spake Sheldon Hearn (sheldonh@uunet.co.za): > > > > > Perhaps you'd like to post the actual error messages you get when > > > you try to upgrade to CURRENT? If so, please post them to the > > > freebsd-current mailing list. > > > > Also, he should read /usr/src/UPGRADING > > Which, last I knew, it's no longer maintained and is empty right now (at > least for RELENG_3 branch). Anyone care to take the job ? I might take it, > but I know myself to be rather busy most of the time... > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 8: 3:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id DDCEB14E8C; Fri, 14 Jan 2000 08:03:30 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id LAA51996; Fri, 14 Jan 2000 11:02:58 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001141602.LAA51996@blackhelicopters.org> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <7041.947863163@axl.noc.iafrica.com> from Sheldon Hearn at "Jan 14, 2000 5:19:23 pm" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Fri, 14 Jan 2000 11:02:58 -0500 (EST) Cc: khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A *lot* of us have local administration procedures that are inappropriate elsewhere, but are proper in a local context (or are wrong, but they want or need to do anyway). My laptop, for example, has a lot of o+rw permissions in /dev, /mnt owned by mwlucas... you get the idea. I don't want to become root to mount a CD or hotsync my pilot, and my laptop isn't sitting behind a T1. Ditto for my desktop system. I'm not going to suggest to the Project that they run /dev/MAKEDEV with a nightmare umask just so I personally don't have to "chmod 666 /dev/cuaa0" after every make world. The point is that system administrators, whether on big-ass systems or little boxes, have to have local procedures to deal with local quirks. I have shell scripts to handle these changes for me. Simple shell scripts, easy-to-write shell scripts, that handle my localizations. FreeBSD's wdc driver does not support CD-Rom configured as a slave without a primary. This is because it is a violation of the IDE specs. This strikes me as more of the same. Now please, can we let this die? We all make suggestions that make people go "bleah". ==ml > On Fri, 14 Jan 2000 10:12:54 EST, Vivek Khera wrote: > > > If you don't like the warning, just delete the recovery procedure > > rather than creating the directory. It does no good for you to try to > > recover something that will never be there. > > Exactly. The only thing that comes out of this patch is we support > an administrative mistake that leads naive users to believe that vi > recovery on reboot is going to work as expected. > > This is a stupid idea. I wish the person who came up with it would just > acknowledge that he's doing something inappropriate and move on, rather > than insisting that the rest of us introduce a bad idea into our systems > to support his bad practice. > > Ciao, > Sheldon. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 10:10:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from home.com (c97217-a.plstn1.sfba.home.com [24.1.83.85]) by hub.freebsd.org (Postfix) with ESMTP id 3E9EC15140 for ; Fri, 14 Jan 2000 09:51:41 -0800 (PST) (envelope-from jerry@home.com) Received: (from jerry@localhost) by home.com (8.9.3/8.9.3) id JAA80878 for freebsd-stable@FreeBSD.ORG; Fri, 14 Jan 2000 09:51:40 -0800 (PST) (envelope-from jerry) Date: Fri, 14 Jan 2000 09:51:40 -0800 From: Jerry Gardner To: freebsd-stable@FreeBSD.ORG Subject: [chad@DCFinc.com: Re: access floppy rw to lock system] Message-ID: <20000114095140.A80621@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chad R. Larson wrote: >Well, I was protesting the logic of doing a read/write mount of read-only >media. Mount it R/O and there is no issue. > >You wouldn't mount a CD-ROM read/write, would you? No, I wouldn't, but I wouldn't expect that doing so would hang or panic the machine either. There is definately a bug in the floppy code, and it's been there for some time now. Hangs and crashes after improperly accessing a floppy do not occur with any other operating system I use, so why should it happen with FreeBSD? Hell, even Windows doesn't crash under these circumstances! -- Jerry Gardner | "Bill Clinton has all the steely resolve w6uv@home.com | of a kamakaze pilot on his 37th mission." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 10:34:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 91E4915B95; Fri, 14 Jan 2000 10:21:32 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA09947; Fri, 14 Jan 2000 11:20:40 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001141820.LAA09947@freeway.dcfinc.com> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: from Adrian Penisoara at "Jan 14, 0 04:51:31 pm" To: ady@warpnet.ro (Adrian Penisoara) Date: Fri, 14 Jan 2000 11:20:40 -0700 (MST) Cc: trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Adrian Penisoara wrote: > I'm not discussing the definition of /var/tmp! I just recognise that > lots of people (including me) step over this rule (as they don't need > those bits to survive reboots, for example) and they MFS mount > /var/tmp (at least) for the sake of optimizing compile times (cc uses > /var/tmp for temporary files). Use "-pipe" in your CFLAGS. You'll get even more speed than making /var/tmp a MFS. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 10:34:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 229EB15B7E; Fri, 14 Jan 2000 10:19:44 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id NAA04478; Fri, 14 Jan 2000 13:17:52 -0500 (EST) From: Brian Hechinger Message-Id: <200001141817.NAA04478@entropy.tmok.com> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <200001141602.LAA51996@blackhelicopters.org> from Michael Lucas at "Jan 14, 2000 11: 2:58 am" To: mwlucas@blackhelicopters.org (Michael Lucas) Date: Fri, 14 Jan 2000 13:17:52 -0500 (EST) Cc: sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas drunkenly mumbled... > A *lot* of us have local administration procedures that are > inappropriate elsewhere, but are proper in a local context (or are > wrong, but they want or need to do anyway). i'm sorry for not letting this die, however.... while it is true that a lot of people have a lot of administration procedures that exist solely for our local setup there are sometimes better solutions than the ones we are using. for example, we'll go with this current thread. /var/tmp on MFS makes cc go faster, but breaks vi.recovery so if we look at the problem we should not be trying to change the vi recovery system, but rather cc. if making a change for ANY reason breaks something else you shouldn't fix the thing you broke, but the thing you are changing. make /var/mfs_tmp and have cc use it for it's temporary storage. if cc doesn't support that then fix cc since being able to specify where your compiler stores it's temp files is a Good Idea(TM) now cc is faster and vi.recovery isn't broken. maybe we should spend less time discussing the technical merits of an action and rather spend our time look for better solutions. -brian -- Brian Hechinger UNIX System Administrator Half.com brian@half.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 11: 6:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E243B156F8; Fri, 14 Jan 2000 11:01:32 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA29741; Fri, 14 Jan 2000 11:00:08 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200001141900.LAA29741@troutmask.apl.washington.edu> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <200001141817.NAA04478@entropy.tmok.com> from Brian Hechinger at "Jan 14, 2000 01:17:52 pm" To: wonko@entropy.tmok.com Date: Fri, 14 Jan 2000 11:00:07 -0800 (PST) Cc: Michael Lucas , sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Hechinger wrote: > > /var/tmp on MFS makes cc go faster, but breaks vi.recovery > so if we look at the problem we should not be trying to change the vi recovery > system, but rather cc. if making a change for ANY reason breaks something > else you shouldn't fix the thing you broke, but the thing you are changing. > > make /var/mfs_tmp and have cc use it for it's temporary storage. if cc doesn't > support that then fix cc since being able to specify where your compiler > stores it's temp files is a Good Idea(TM) > *sigh* man gcc Either use -pipe or set the environmental variable TMPDIR. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 11:24: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 7B96114F57; Fri, 14 Jan 2000 11:23:11 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 129BYJ-000GpM-00; Fri, 14 Jan 2000 18:34:27 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #1) id 129BYJ-00045l-00; Fri, 14 Jan 2000 18:34:27 +0000 Date: Fri, 14 Jan 2000 18:34:27 +0000 From: Ben Smithurst To: Adrian Penisoara Cc: Trond Endrestol , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot Message-ID: <20000114183427.A15678@strontium.scientia.demon.co.uk> References: <1535.947843930@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Penisoara wrote: > (cc uses /var/tmp for > temporary files) so do "TMPDIR=/tmp; export TMPDIR", problem solved. (Or just use -pipe when compiling.) -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 11:53: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id CDE6114A2A for ; Fri, 14 Jan 2000 11:52:59 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id NAA13580 for ; Fri, 14 Jan 2000 13:07:24 -0600 (CST) Date: Fri, 14 Jan 2000 13:07:24 -0600 (CST) From: "Jeffrey J. Libman" To: stable@freebsd.org Subject: re: make installworld of today's cvsup fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i did a cvsup stable-supfile today to move from 3.3stable to the latest stable. make buildworld ran fine. make installworld produced the following error: install -c -o root -g wheel -m 444 pam.8.gz /usr/share/man/man8 /usr/share/man/man3/pam_close_session.3.gz -> /usr/share/man/man3/pam_open_sessi on.3.gz ln: /usr/share/man/man3/pam_open_session.3.gz: No such file or directory *** Error code 1 cd /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam_misc; install -C - o root -g wheel -m 444 pam_misc.h /usr/include/security cd /usr/src/lib/libpam/libpam; install -C -o root -g wheel -m 444 pam_mod_misc .h /usr/include/security 1 error *** Error code 2 any help? thanks in advance. cheers, jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 12:17:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.gmx.net (mail2.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id 2786E14EBC for ; Fri, 14 Jan 2000 12:17:41 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 10578 invoked by uid 0); 14 Jan 2000 20:17:38 -0000 Received: from p3e9d5159.dip.t-dialin.net (HELO speedy.gsinet) (62.157.81.89) by mail2.gmx.net with SMTP; 14 Jan 2000 20:17:38 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA14320 for freebsd-stable@FreeBSD.ORG; Fri, 14 Jan 2000 18:26:57 +0100 Date: Fri, 14 Jan 2000 18:26:57 +0100 From: Gerhard Sittig To: freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system Message-ID: <20000114182657.S7734@speedy.gsinet> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <200001140505.QAA07620@lightning.itga.com.au> <200001140549.WAA08193@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001140549.WAA08193@freeway.dcfinc.com>; from chad@DCFinc.com on Thu, Jan 13, 2000 at 10:49:36PM -0700 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 22:49 -0700, Chad R. Larson wrote: > As I recall, Gregory Bond wrote: > >> Exactly. If it's read-only media, it should fail when being > >> mounted read-write, or default to ro. > > > > Even this is not enough. PC floppy hardware doesn't have a > > "lock media" function, so you can get the same panic by > > changing a floppy for a write-protected one while it is > > mounted. > > But PC floppy hardware =does= have a "media changed" function. > So, same deal. But you only learn "it's too late". You don't have a chance to sync or umount or do something. The only thing one can do about this is to keep the floppy inside and eject it ONLY when all the administrativa are done. That's exactly the point where it isn't the above mentioned "PC floppy" any longer (see Macs and Sparcs for the opposite, but not the latest cheap clones). virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 12:19:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id E3DDD1508D for ; Fri, 14 Jan 2000 12:19:47 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id OAA14037 for ; Fri, 14 Jan 2000 14:19:46 -0600 (CST) Date: Fri, 14 Jan 2000 14:19:45 -0600 (CST) From: "Jeffrey J. Libman" To: stable@FreeBSD.ORG Subject: re: make installworld of today's cvsup fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok...not sure what happened...went into the dir there and did a make install...then backed out and re-ran the make installworld...all went fine. jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ On Fri, 14 Jan 2000, Jeffrey J. Libman wrote: > i did a cvsup stable-supfile today to move from 3.3stable to the latest > stable. > > make buildworld ran fine. > > make installworld produced the following error: > > install -c -o root -g wheel -m 444 pam.8.gz /usr/share/man/man8 > /usr/share/man/man3/pam_close_session.3.gz -> > /usr/share/man/man3/pam_open_sessi > on.3.gz > ln: /usr/share/man/man3/pam_open_session.3.gz: No such file or directory > *** Error code 1 > cd > /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam_misc; install > -C - > o root -g wheel -m 444 pam_misc.h /usr/include/security > cd /usr/src/lib/libpam/libpam; install -C -o root -g wheel -m 444 > pam_mod_misc > .h /usr/include/security > 1 error > *** Error code 2 > > any help? > > thanks in advance. > > cheers, > jeff > > -- > | > |\ +------------------------------+ > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > Wantabe, Inc. |__\ +------------------------------+ > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 12:37:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from knock.econ.vt.edu (knock.econ.vt.edu [128.173.172.240]) by hub.freebsd.org (Postfix) with ESMTP id 7DD0B1511A for ; Fri, 14 Jan 2000 12:37:41 -0800 (PST) (envelope-from rdmurphy@knock.econ.vt.edu) Received: (from rdmurphy@localhost) by knock.econ.vt.edu (8.9.3/8.9.3) id PAA35816; Fri, 14 Jan 2000 15:37:36 -0500 (EST) (envelope-from rdmurphy) From: "Russell D. Murphy Jr." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 14 Jan 2000 15:37:36 -0500 (EST) To: "Jeffrey J. Libman" Cc: stable@FreeBSD.ORG Subject: re: make installworld of today's cvsup fails In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14463.34759.349604.80327@knock.econ.vt.edu> Reply-To: rdmurphy@vt.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Three machines here are fine (cvsup, buildworld, installworld, kernel) as of: system-update began at Fri Jan 14 04:00:00 EST 2000 and ended at Fri Jan 14 07:44:16 EST 2000. system-update began at Fri Jan 14 04:30:01 EST 2000 and ended at Fri Jan 14 06:23:04 EST 2000. system-update began at Fri Jan 14 05:30:00 EST 2000 and ended at Fri Jan 14 07:29:37 EST 2000. RDM According to Jeffrey J. Libman (January 14, 2000): | i did a cvsup stable-supfile today to move from 3.3stable to the latest | stable. | | make installworld produced the following error: | | install -c -o root -g wheel -m 444 pam.8.gz /usr/share/man/man8 | /usr/share/man/man3/pam_close_session.3.gz -> | /usr/share/man/man3/pam_open_sessi | on.3.gz | ln: /usr/share/man/man3/pam_open_session.3.gz: No such file or directory | *** Error code 1 | | any help? | | thanks in advance. | | cheers, | jeff | ----- Russell D. Murphy Department of Economics Virginia Polytechnic Institute and State University 3034 Pamplin Hall Blacksburg, Virginia 24061-0316 (540) 231-4537 rdmurphy@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 13:15:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from malasada.lava.net (malasada.lava.net [199.222.42.2]) by hub.freebsd.org (Postfix) with ESMTP id 259D314CFC for ; Fri, 14 Jan 2000 13:15:40 -0800 (PST) (envelope-from cliftonr@lava.net) Received: from localhost (1296 bytes) by malasada.lava.net via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Fri, 14 Jan 2000 11:15:37 -1000 (HST) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Dec-7) Date: Fri, 14 Jan 2000 11:15:37 -1000 From: Clifton Royston To: freebsd-stable@freebsd.org Subject: Bind version in 3.3RELEASE Message-ID: <20000114111536.E8127@lava.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed 3.3Release, which I installed recently, is running Bind 8.2.1 which has known security vulnerabilities including a possible root compromise exploit. I did not see this mentioned in the errata page for 3.3 at The ISC recommends running Bind 8.2.2P5. Is Bind 8.2.2P5 incorporated into the latest -stable build, so that I'll get it if I start doing CTM or CVS updates? Or is it preferable to grab the sources direct from ISC? -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net "An absolute monarch would be absolutely wise and good. But no man is strong enough to have no interest. Therefore the best king would be Pure Chance. It is Pure Chance that rules the Universe; therefore, and only therefore, life is good." - AC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 13:26:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id B30FB14DAC for ; Fri, 14 Jan 2000 13:26:12 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.18 2000/01/07 21:56:55 dmccart Exp $) with ESMTP id OAA05681; Fri, 14 Jan 2000 14:25:49 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id OAA25658; Fri, 14 Jan 2000 14:25:48 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id QAA16339; Fri, 14 Jan 2000 16:25:49 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14463.37980.761454.800353@hip186.ch.intel.com> Date: Fri, 14 Jan 2000 14:25:48 -0700 (MST) To: Clifton Royston Cc: freebsd-stable@freebsd.org Subject: Re: Bind version in 3.3RELEASE In-Reply-To: <20000114111536.E8127@lava.net> References: <20000114111536.E8127@lava.net> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Friday, January 14, Clifton Royston wrote: ] > I noticed 3.3Release, which I installed recently, is running Bind > 8.2.1 which has known security vulnerabilities including a possible root > compromise exploit. > > I did not see this mentioned in the errata page for 3.3 at > > > The ISC recommends running Bind 8.2.2P5. Is Bind 8.2.2P5 > incorporated into the latest -stable build, so that I'll get it if I > start doing CTM or CVS updates? Or is it preferable to grab the > sources direct from ISC? > > -- Clifton > from my messages file: Jan 11 23:21:22 dolphin named[2991]: starting. named 8.2.2-P5-NOESW Fri Jan... Running 3.4-STABLE CVSup'ed last week. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 13:34:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2736D14C33 for ; Fri, 14 Jan 2000 13:34:46 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id NAA02189; Fri, 14 Jan 2000 13:57:03 -0800 (PST) Date: Fri, 14 Jan 2000 13:57:03 -0800 From: Alfred Perlstein To: Clifton Royston Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bind version in 3.3RELEASE Message-ID: <20000114135702.E508@fw.wintelcom.net> References: <20000114111536.E8127@lava.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000114111536.E8127@lava.net>; from cliftonr@lava.net on Fri, Jan 14, 2000 at 11:15:37AM -1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Clifton Royston [000114 13:39] wrote: > I noticed 3.3Release, which I installed recently, is running Bind > 8.2.1 which has known security vulnerabilities including a possible root > compromise exploit. > > I did not see this mentioned in the errata page for 3.3 at > > > The ISC recommends running Bind 8.2.2P5. Is Bind 8.2.2P5 > incorporated into the latest -stable build, so that I'll get it if I > start doing CTM or CVS updates? Or is it preferable to grab the > sources direct from ISC? 2 options: a) upgrade entire system to 3-stable, it's pretty easy: pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz read: http://www.freebsd.org/handbook/makeworld.html b) get the latest bind port: pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz cd /usr/ports/net/bind8/ && make install I would choose 'A' if the server is not yet in production, or 'B' if your uptime is more valuable than a fresher system. good luck, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 13:36:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [208.44.193.69]) by hub.freebsd.org (Postfix) with ESMTP id 4B86B14D8E for ; Fri, 14 Jan 2000 13:36:37 -0800 (PST) (envelope-from jan@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.9.3/ignatz) with ESMTP id NAA57273; Fri, 14 Jan 2000 13:36:50 -0800 (PST) Date: Fri, 14 Jan 2000 13:36:50 -0800 (PST) From: "f.johan.beisser" To: Clifton Royston Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bind version in 3.3RELEASE In-Reply-To: <20000114111536.E8127@lava.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG generally, if you're going to run bind, you should update it from the ports collection (rather than updating the entire OS). the ports version (i believe) installs to /usr/local/sbin, rather than /usr/sbin. you'll have to change teh named entry in your /etc/rc.conf to reflect the use of a different named. also, if you're using the "installed named" you could simply update the sources and build it from there. -- jan (PS - the current version of "stable" is freebsd 3.4) On Fri, 14 Jan 2000, Clifton Royston wrote: > I noticed 3.3Release, which I installed recently, is running Bind > 8.2.1 which has known security vulnerabilities including a possible root > compromise exploit. > > I did not see this mentioned in the errata page for 3.3 at > > > The ISC recommends running Bind 8.2.2P5. Is Bind 8.2.2P5 > incorporated into the latest -stable build, so that I'll get it if I > start doing CTM or CVS updates? Or is it preferable to grab the > sources direct from ISC? > > -- Clifton > > -- > Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net > "An absolute monarch would be absolutely wise and good. > But no man is strong enough to have no interest. > Therefore the best king would be Pure Chance. > It is Pure Chance that rules the Universe; > therefore, and only therefore, life is good." - AC > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > +-----// f. johan beisser //------------------------------+ email: jan[at]caustic.org web: http://www.caustic.org/~jan "knowledge is power. power corrupts. study hard, be evil." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 13:37:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id DBB9C15140 for ; Fri, 14 Jan 2000 13:37:07 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id OAA06166; Fri, 14 Jan 2000 14:36:30 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Fri, 14 Jan 2000 14:36:30 -0700 (MST) From: Doug Russell To: Randy Bush Cc: FreeBSD Stable Subject: Re: user mode ppp error with windoze In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Jan 2000, Randy Bush wrote: > anyone recognize the two warnings? > > Jan 13 17:30:37 ppp[20059]: Phase: Using interface: tun0 > Jan 13 17:30:37 ppp[20059]: Phase: deflink: Created in closed state > Jan 13 17:30:37 ppp[20059]: Warning: timeout: Invalid command > Jan 13 17:30:37 ppp[20059]: Warning: timeout: Failed 1 > Jan 13 17:30:37 ppp[20059]: Phase: PPP Started (direct mode). > Jan 13 17:30:37 ppp[20059]: Phase: bundle: Establish > > it's an inbound ppp from a win98 system, and they get a loong, like one > minute, pause. Uncheck the "Log On To Network" in the dial-up networking entry. Microsoft made 98 sit and wait trying to Microsoft Networking logon. Of course, there would be no delay on an NT server... BLECH.. Typical M$ Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 13:46:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id 4DD1614D5C for ; Fri, 14 Jan 2000 13:46:49 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id PAA00494 for ; Fri, 14 Jan 2000 15:46:41 -0600 (CST) Date: Fri, 14 Jan 2000 15:46:39 -0600 (CST) From: "Jeffrey J. Libman" To: stable@freeBSD.org Subject: re: today's build Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok...this is the easiest o/s upgrade i've yet done. i cvsup stable-supfile this morning. make buildworld. make installworld. config and build kernel. copied some rc* files to /etc rebooted...no problems. well...not much: dmesg gets: dmesg: namelist: msgbufp not found what's up with that? cheers, jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 13:49:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from malasada.lava.net (malasada.lava.net [199.222.42.2]) by hub.freebsd.org (Postfix) with ESMTP id 587F115156 for ; Fri, 14 Jan 2000 13:49:21 -0800 (PST) (envelope-from cliftonr@lava.net) Received: from localhost (1539 bytes) by malasada.lava.net via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Fri, 14 Jan 2000 11:49:19 -1000 (HST) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Dec-7) Date: Fri, 14 Jan 2000 11:49:19 -1000 From: Clifton Royston To: Alfred Perlstein Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bind version in 3.3RELEASE Message-ID: <20000114114919.F8127@lava.net> References: <20000114111536.E8127@lava.net> <20000114135702.E508@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000114135702.E508@fw.wintelcom.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 14, 2000 at 01:57:03PM -0800, Alfred Perlstein wrote: > 2 options: > > a) upgrade entire system to 3-stable, it's pretty easy: > pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz > read: http://www.freebsd.org/handbook/makeworld.html > > b) get the latest bind port: > pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz > cd /usr/ports/net/bind8/ && make install > > I would choose 'A' if the server is not yet in production, or > 'B' if your uptime is more valuable than a fresher system. Many thanks for all the rapid answers! Clearly a good list! -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net "An absolute monarch would be absolutely wise and good. But no man is strong enough to have no interest. Therefore the best king would be Pure Chance. It is Pure Chance that rules the Universe; therefore, and only therefore, life is good." - AC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 14:21:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 3D7AB150F7; Fri, 14 Jan 2000 14:20:55 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.236.249] (dialup1679.brussels.skynet.be [194.78.234.143]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA24237; Fri, 14 Jan 2000 23:19:34 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001141900.LAA29741@troutmask.apl.washington.edu> References: <200001141900.LAA29741@troutmask.apl.washington.edu> Date: Fri, 14 Jan 2000 22:57:52 +0100 To: Steve Kargl , wonko@entropy.tmok.com From: Brad Knowles Subject: Re: Making sure /var/tmp/vi.recover exists during reboot Cc: Michael Lucas , sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:00 AM -0800 2000/1/14, Steve Kargl wrote: > Either use -pipe or set the environmental variable TMPDIR. Thank you. I was wondering when someone was going to mention this. Double sigh..... -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 15:14:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-22.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.150]) by hub.freebsd.org (Postfix) with ESMTP id EAC9D14FFF for ; Fri, 14 Jan 2000 15:14:29 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA42646; Fri, 14 Jan 2000 23:14:23 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA00330; Fri, 14 Jan 2000 20:27:29 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001142027.UAA00330@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Randy Bush Cc: FreeBSD Stable , brian@hak.lan.Awfulhak.org Subject: Re: user mode ppp error with windoze In-Reply-To: Message from Randy Bush of "Thu, 13 Jan 2000 20:27:12 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 20:27:29 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > anyone recognize the two warnings? > > Jan 13 17:30:37 ppp[20059]: Phase: Using interface: tun0 > Jan 13 17:30:37 ppp[20059]: Phase: deflink: Created in closed state > Jan 13 17:30:37 ppp[20059]: Warning: timeout: Invalid command > Jan 13 17:30:37 ppp[20059]: Warning: timeout: Failed 1 > Jan 13 17:30:37 ppp[20059]: Phase: PPP Started (direct mode). > Jan 13 17:30:37 ppp[20059]: Phase: bundle: Establish > > it's an inbound ppp from a win98 system, and they get a loong, like one > minute, pause. Try enabling command logging. It looks like an invalid command is being executed to me. WRT the long pause, try experimenting with ``set log +debug''. > randy -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 15:14:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-22.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.150]) by hub.freebsd.org (Postfix) with ESMTP id 1259E14FFF; Fri, 14 Jan 2000 15:14:38 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA42670; Fri, 14 Jan 2000 23:14:26 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00906; Fri, 14 Jan 2000 08:58:10 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001140858.IAA00906@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: mi@aldan.algebra.com Cc: Bill Fumerola , Mikhail Teterin , Stan Brown , stable@freebsd.org, brian@freebsd.org, brian@hak.lan.Awfulhak.org Subject: Re: IP Tunneling, is it possible? In-Reply-To: Message from Mikhail Teterin of "Thu, 13 Jan 2000 12:58:56 EST." <200001131758.MAA52224@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 08:58:10 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bill Fumerola once wrote: > > > On Thu, 13 Jan 2000, Mikhail Teterin wrote: > > > > > I love my PPP over SSH connection. Basicly, ppp on one machine > > > invokes ssh to login to the other side and start ``ppp -direct'' > > > there. Once the connection is up, both ends can route packets > > > to/from the newly created tun-interfaces enabling other machines on > > > the LANs to see it all. > > > > ppp+ssh has some flaws to it. Performance can be choppy and the reason > > (If I'm pulling out of my memory banks what Brian told me at > > FreeBSDcon properly) is that there are so many layer, each with its > > own error correction, compression, etc that wierd bursts and such can > > happen. > > This is true. I enable compression in ssh, but disable it in PPP. Still, > I suppose, it is imperfect. I'm wondering if changing the MTU/MRU will > help (and in what direction). It does, however, completely emulate the > net interface -- I can ftp, rsh, run X, etc. over such connection -- > even rwhod works (must be started after the connction is established). > > > > This works perfect to get a normal connection through a one-way > > > firewall too, BTW. > > > > Which is the only reason I use it. I think the only way to defeat the double-tcp-retransmit mess is if it were somehow possible to tell the higher level of TCP that your transport is reliable. This is quite an interesting thought - it also applies to ISDN for example - I'd like to tell the tcp stack that this particular interface address uses a reliable transport and that it should not try to retransmit. Unfortunately, I know nothing about the tcp stack :-( > -mi -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 15:25:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from adara.lcs.mit.edu (adara.lcs.mit.edu [18.111.14.1]) by hub.freebsd.org (Postfix) with ESMTP id BA37115155 for ; Fri, 14 Jan 2000 15:25:51 -0800 (PST) (envelope-from beng@adara.lcs.mit.edu) Received: from adara.lcs.mit.edu (localhost [127.0.0.1]) by adara.lcs.mit.edu (8.9.3/8.9.3) with ESMTP id SAA39744; Fri, 14 Jan 2000 18:25:40 -0500 (EST) (envelope-from beng@adara.lcs.mit.edu) Message-Id: <200001142325.SAA39744@adara.lcs.mit.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: Stan Brown Cc: freebsd-stable@freebsd.org (FreeBSD Stable List) Subject: Re: IP Tunneling, is it possible? In-reply-to: Your message of "Thu, 13 Jan 2000 06:59:24 EST." <200001131159.DAA09342@netcom.com> From: Benjamin Greenwald X-Sender: beng@lcs.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 18:25:40 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you don't need encryption (which is sounds like you don't) take a look at nos-tun(8) which is part of FreeBSD. -Ben Greenwald > I have 2 physicaly seperate segments of the same subnet that I need to > connect logicaly. I have a FreeBSD gateway/firewall machine on both of > the subnets conected to the corporate network. > > Specificaly, I have an existing network 170.85.106.* netmask > 255.255.255.128 which connects to the corporate 170.85.113.* network th is > is then is routed to 170.85.109.* Now I have in my office some more > machines that I need to set up for the 170.85.106 net. > > Is there a way to encapsulate packets on the 2 parts of the 170.85.105 > network, and send them to the other part, where they would be > unencapsulated? I think this is called IP Tunneling and Linux appears > to support it, but I would rather not change the 2 gateway/firewall > machines over to Linux, if I don't have to. > > I regert if you jave seen this request before, I have submited it on > questions, and networking, but the only response I got was a flame > about my typing. > > -- > Stan Brown stanb@netcom.com 404-996-69 55 > Factory Automation Systems > Atlanta Ga. > -- > Look, look, see Windows 95. Buy, lemmings, buy! > Pay no attention to that cliff ahead... Henry Spencer > (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 15:35:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id F0FEB156F1; Fri, 14 Jan 2000 15:34:48 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id SAA07115; Fri, 14 Jan 2000 18:36:19 -0500 (EST) From: Brian Hechinger Message-Id: <200001142336.SAA07115@entropy.tmok.com> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <200001141900.LAA29741@troutmask.apl.washington.edu> from Steve Kargl at "Jan 14, 2000 11: 0: 7 am" To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Fri, 14 Jan 2000 18:36:19 -0500 (EST) Cc: mwlucas@blackhelicopters.org, sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl drunkenly mumbled... > > *sigh* > > man gcc > > Either use -pipe or set the environmental variable TMPDIR. ok, maybe i didn't say that right. this i know, i was trying to use gcc and vi.recovery as examples. but then my question is... why didn't you speak up earlier and save us all from this thread? -me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 17:54:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id 0DA3615156 for ; Fri, 14 Jan 2000 17:54:37 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id TAA01897 for ; Fri, 14 Jan 2000 19:54:30 -0600 (CST) Date: Fri, 14 Jan 2000 19:54:30 -0600 (CST) From: "Jeffrey J. Libman" To: stable@freeBSD.org Subject: re: today's build - now 2 programs faile to run Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i reported earlier that i cvsup'd and built and installed and config'd my kernel on this morning's stable. i also reported that dmesg gets: dmesg: namelist: msgbufp not found now if find a similar error trying to run top: ~$ top top: nlist failed any help? cheers, jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 18:28:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 630E414E1D for ; Fri, 14 Jan 2000 18:28:30 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 129Iwu-000PYN-00; Fri, 14 Jan 2000 18:28:20 -0800 Date: Fri, 14 Jan 2000 18:28:15 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Jeffrey J. Libman" Cc: stable@freeBSD.org Subject: re: today's build - now 2 programs faile to run In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jan 2000, Jeffrey J. Libman wrote: > i reported earlier that i cvsup'd and built and installed and config'd my > kernel on this morning's stable. > > i also reported that dmesg gets: > > dmesg: namelist: msgbufp not found > > now if find a similar error trying to run top: > > ~$ top > top: nlist failed > > any help? > > cheers, > jeff FAQ. Programs that access internal kernel structures may stop working if they are not updated at the same time as the kernel. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 19: 9:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 06F2714EA3; Fri, 14 Jan 2000 19:09:46 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id EAA09384; Sat, 15 Jan 2000 04:05:37 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id DAA28337; Sat, 15 Jan 2000 03:04:07 +0100 (CET) Date: Sat, 15 Jan 2000 03:04:07 +0100 (CET) From: Juergen Lock Message-Id: <200001150204.DAA28337@saturn.kn-bremen.de> To: msmith@FreeBSD.ORG Subject: Re: fbsdboot.exe can't load elf kernels X-Newsgroups: local.list.freebsd.stable In-Reply-To: <200001121739.JAA02551@mass.cdrom.com> References: <20000112170704.A5073@lindt.urgle.com> Organization: home Cc: Mike Bristow , Mike Smith , R Joseph Wright , freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001121739.JAA02551@mass.cdrom.com> you write: >> I still maintain that the /right/ solution is for the BIOS to have >> a ``while booting shovel data out COM1 and accept data from COM1 as if >> it were my keyboard'' option. >> >> I've seen them on (I think) NCR boxes. > >Intel do this on their server boxes, to the extent that if you have a >colour ANSI terminal you can run fullscreen expansion BIOS tools like eg. >Adaptec's. I'm reasonably sure that it's just an extra-price option from >the major BIOS vendors. Compaq has something like this too, only better. i recently configured a Proliant 1600 server box that has a `integraded remote console' that could even drive a modem (unless its a `win'modem, obviously) and have it accept calls to `log in' to the console. it lets you construct any key combination thru special character sequences, force a reset remotely, capture NT's blue screen of death, etc. probably _very_ useful for the poor guys trying to depend on `server OS'es less stable than unix... :) (unfortunately i didn't get around actually playing with it, and when i just wanted to configure it to use a serial console the `usual' way i had to use -h in boot.config because -P didn't work as it believed it always had a keyboard.) And in case anyone else comes around such a machine... you have to run the setup CD that comes with it first, otherwise the BIOS doesn't even know how much RAM it has, and the SCSI controller(s) apparently don't get properly initialized causing the BOOTMFS kernel to panic. (i may even still have the actual place where in the ncr driver it died in case that interests anyone...) The setup CD installs a DOS partition that can be used to do configurations later (apparently it doesn't have any configuration screens in the BIOS itself?), and after that the BIOS still didn't seem to report the amount of RAM properly, the kernel still only saw 16MB until i added VM86. Oh and the on-board `tl'-type NIC caused a panic once, so we installed an fxp. (i got the crashdump and mailed wpaul a backtrace but ne needed me to do more tests which i didn't find the time for, sorry. I only managed to update it to the latest -stable before it got installed in order to get the sym driver...) Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 19:38:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fever.semiotek.com (H253.C225.tor.velocet.net [216.126.82.253]) by hub.freebsd.org (Postfix) with ESMTP id C978214E1D for ; Fri, 14 Jan 2000 19:38:10 -0800 (PST) (envelope-from jread@fever.semiotek.com) Received: (from jread@localhost) by fever.semiotek.com (8.9.3/8.9.3) id WAA57605 for freebsd-stable@freebsd.org; Fri, 14 Jan 2000 22:37:18 -0500 (EST) (envelope-from jread) Date: Fri, 14 Jan 2000 22:37:18 -0500 From: Justin Wells To: freebsd-stable@freebsd.org Subject: cannot buildworld with securelevel turned on Message-ID: <20000114223717.A57576@semiotek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is what happens when I try to do a buildworld: install -C -c -o root -g wheel -m 444 -fschg libdescrypt.so.2 /usr/obj/usr/src/tmp/usr/lib install: /usr/obj/usr/src/tmp/usr/lib/libdescrypt.so.2: chown/chgrp: Operation not permitted *** Error code 71 The problem is that I am running with securelevel turned on. My plan was to do the "buildworld" with the server up, then drop to single user mode, run the "installworld", and hopefully bring it back up again without being down for too long. Now I will require an extra reboot just to clear the securelevel flag. Is it really necessary to mark the stuff in /usr/obj with schg? I guess someone could modify the stuff in there, and then wait for me to upgrade my system or something. But they could equally well modify the source files in /usr/src, so I'm not sure how much security this adds. I think the schg flag should not be set here. Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 21:40:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 05E25150EE for ; Fri, 14 Jan 2000 21:40:52 -0800 (PST) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2ive6gq.dialup.mindspring.com [165.247.26.26]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA27542; Sat, 15 Jan 2000 00:39:48 -0500 (EST) Message-ID: <388007F2.54557D1A@confusion.net> Date: Sat, 15 Jan 2000 00:38:58 -0500 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jeffrey J. Libman" Cc: stable@FreeBSD.ORG Subject: Re: today's build - now 2 programs faile to run References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rebuild the kernel and it should work, these are programs that access things in the kernel structures, so the programs need to be in sync with the kernel to work. "Jeffrey J. Libman" wrote: > > i reported earlier that i cvsup'd and built and installed and config'd my > kernel on this morning's stable. > > i also reported that dmesg gets: > > dmesg: namelist: msgbufp not found > > now if find a similar error trying to run top: > > ~$ top > top: nlist failed > > any help? > > cheers, > jeff > > -- > | > |\ +------------------------------+ > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > Wantabe, Inc. |__\ +------------------------------+ > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Laurence Berland, Stuyvesant HS Debate <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 2000 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 14 23:14:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from io.dreamscape.com (io.dreamscape.com [206.64.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 72FA914F35 for ; Fri, 14 Jan 2000 23:14:26 -0800 (PST) (envelope-from krentel@dreamscape.com) Received: from dreamscape.com (sA17-p15.dreamscape.com [209.217.195.206]) by io.dreamscape.com (8.9.3/8.8.4) with ESMTP id CAA04032 for ; Sat, 15 Jan 2000 02:09:40 -0500 (EST) X-Dreamscape-Track-A: sA17-p15.dreamscape.com [209.217.195.206] X-Dreamscape-Track-B: Sat, 15 Jan 2000 02:09:40 -0500 (EST) Received: (from krentel@localhost) by dreamscape.com (8.9.3/8.9.3) id CAA11205 for freebsd-stable@freebsd.org; Sat, 15 Jan 2000 02:09:49 -0500 (EST) (envelope-from krentel) Date: Sat, 15 Jan 2000 02:09:49 -0500 (EST) From: "Mark W. Krentel" Message-Id: <200001150709.CAA11205@dreamscape.com> To: freebsd-stable@freebsd.org Subject: fstat's use of device numbers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question about fstat's treatment of the high-order bits in a device's minor number. My /etc/fstab includes: # Device Mountpoint FStype Options Dump Pass /dev/da0s2f /usr ufs rw 2 2 /dev/da0s3f /home ufs rw 2 2 That is, /usr and /home are both the "f" partition on different slices of the same disk. As a result, these two partitions are confused by fstat(1) with the -f flag (restrict to open files on the same file system as the -f argument). % fstat -f /home USER CMD PID FD MOUNT INUM MODE SZ|DV R/W krentel fstat 10702 wd /home 315401 drwxr-xr-x 2048 r krentel fstat 10702 text /usr 7946 -r-xr-sr-x 10160 r ... That is, I asked for files on /home, but I also got /usr, a separate partition. In general, this will happen whenever there are two partitions with the same letter on different slices of the same disk. The /dev entries are: % ls -l /dev/da0*f brw-r----- 1 root operator 4, 5 Dec 24 20:06 /dev/da0f brw-r----- 1 root operator 4, 0x00030005 Jul 1 1999 /dev/da0s2f brw-r----- 1 root operator 4, 0x00040005 Jul 1 1999 /dev/da0s3f Looking through the fstat.c source, in the ufs_filestat procedure, the file system id is computed as: int ufs_filestat(vp, fsp) struct vnode *vp; struct filestat *fsp; { struct inode inode; if (!KVM_READ(VTOI(vp), &inode, sizeof (inode))) { dprintf(stderr, "can't read inode at %p for pid %d\n", (void *)VTOI(vp), Pid); return 0; } fsp->fsid = inode.i_dev & 0xffff; That is, the 0xffff mask erases the high-order bits of the major/minor number packing and makes da0f, da0s2f, and da0s3f appear to be the same partition. Is this right? Now, I don't know enough about Freebsd's treatment of minor numbers. Is this a simple bug, fixable by removing the 0xffff mask? I tried that, and it seems to work. Or, is the issue more complicated? Or, should I just avoid creating Freebsd partitions on two slices of the same disk? --Mark Krentel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 1: 5:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id A895714F40; Sat, 15 Jan 2000 01:05:51 -0800 (PST) (envelope-from marcel@scc.nl) Received: from scc.nl (dweezil [192.168.3.2]) by mail.scc.nl (8.9.3/8.9.3) with ESMTP id KAA62741; Sat, 15 Jan 2000 10:05:50 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3880386E.A83AB6BA@scc.nl> Date: Sat, 15 Jan 2000 10:05:50 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Satoshi - Ports Wraith - Asami Cc: stable@freebsd.org Subject: Re: Problems with linux_base-6.1 References: <387E163E.16722C62@scc.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi - Ports Wraith - Asami wrote: > > I don't assume the kernel can be safely loaded on older release > kernels to get the desired effect? I don't want to promote that. People should upgrade the complete kernel source at a minimum, IMO. Since I specifically noted that the mail applies to FreeBSD-stable, I assume they know how to update sources (otherwise they wouldn't be running -stable). > In that case, I can't put them in > the upgrade kits, can you modify the port to check ${OSVERSION} and > exit with a message if the user's system is too old? Is that necessary? The ports collection isn't designed for older systems. Most of the ports will work anyway, but some of them don't. linux_base-6.1 will work on 3.3-RELEASE as well IIRC, that doesn't mean that the linux kernel module is up to it; but that the story of the its life :-) I deliberately waited until well after 3.4 to upgrade the port, so that it will be in 4.0 and we have enough time to fix any problems on -stable for 3.5. People running into problems now should be running -stable, not 3.4 release or older, right? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 4:31:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 3875614C3B; Sat, 15 Jan 2000 04:31:07 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id HAA55389; Sat, 15 Jan 2000 07:31:05 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id HAA13501; Sat, 15 Jan 2000 07:31:05 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200001151231.HAA13501@rtfm.newton> Subject: Re: Problems with linux_base-6.1 In-Reply-To: <3880386E.A83AB6BA@scc.nl> from Marcel Moolenaar at "Jan 15, 2000 10:05:50 am" To: Marcel Moolenaar Date: Sat, 15 Jan 2000 07:31:05 -0500 (EST) Cc: Satoshi - Ports Wraith - Asami , stable@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" => In that case, I can't put them in the upgrade kits, can you modify => the port to check ${OSVERSION} and exit with a message if the user's => system is too old? = =Is that necessary? The ports collection isn't designed for older =systems. Most of the ports will work anyway, but some of them don't. AFAIU, since we have a single ports collection, a port is supposed to work on every version (not sure about 2.2.x) or, if it can not -- say so. In this case, IMHO, there should be two ports -- linux_base (with the 5.x) and linux_base6 -- for the latest stuff. That's the user's twi pennies. -mi =People running into problems now should be running -stable, not 3.4 =release or older, right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 4:41:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 7758C14C3B for ; Sat, 15 Jan 2000 04:41:30 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id EAA90794; Sat, 15 Jan 2000 04:41:27 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id EAA83400; Sat, 15 Jan 2000 04:41:22 -0800 (PST) To: Marcel Moolenaar Cc: stable@freebsd.org Subject: Re: Problems with linux_base-6.1 References: <387E163E.16722C62@scc.nl> <3880386E.A83AB6BA@scc.nl> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 15 Jan 2000 04:41:19 -0800 In-Reply-To: Marcel Moolenaar's message of "Sat, 15 Jan 2000 10:05:50 +0100" Message-ID: Lines: 42 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Marcel Moolenaar * > I don't assume the kernel can be safely loaded on older release * > kernels to get the desired effect? * * I don't want to promote that. People should upgrade the complete kernel * source at a minimum, IMO. Since I specifically noted that the mail * applies to FreeBSD-stable, I assume they know how to update sources * (otherwise they wouldn't be running -stable). Yes, that's what I figured. (Just checking.) * > In that case, I can't put them in * > the upgrade kits, can you modify the port to check ${OSVERSION} and * > exit with a message if the user's system is too old? * * Is that necessary? The ports collection isn't designed for older * systems. Most of the ports will work anyway, but some of them don't. No. There are millions out there who want to run the latest ports with release systems. That's why I make "upgrade kits" to help them. * linux_base-6.1 will work on 3.3-RELEASE as well IIRC, that doesn't mean * that the linux kernel module is up to it; but that the story of the its * life :-) * * I deliberately waited until well after 3.4 to upgrade the port, so that * it will be in 4.0 and we have enough time to fix any problems on -stable * for 3.5. * * People running into problems now should be running -stable, not 3.4 * release or older, right? I'm not sure what you mean here, do people with 3.3R and 3.4R run into problems with linux_base? Or are you saying they shouldn't be running linux_base from ports-current? If it's the latter, please add the check, given the nature of your work I understand that it is impossible to make it work on older releases, but those who try need to get a easy-to-understand message. -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 5: 5:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id 9076414D3F for ; Sat, 15 Jan 2000 05:05:34 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 3333 invoked from network); 15 Jan 2000 13:05:32 -0000 Received: from userbg76.uk.uudial.com (HELO marder-1.) (62.188.142.196) by smtp.dial.pipex.com with SMTP; 15 Jan 2000 13:05:32 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id NAA00386 for stable@freebsd.org; Sat, 15 Jan 2000 13:05:02 GMT (envelope-from mark) Date: Sat, 15 Jan 2000 13:05:01 +0000 From: Mark Ovens To: stable@freebsd.org Subject: Y2K wierdness?? Message-ID: <20000115130501.A336@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, just noticed this (note the dates): marder-1# ls -ld /drvc /ntfs drwxrwxrwx 1 root wheel 16384 Jan 1 1980 /drvc drwxr-xr-x 1 root wheel 0 Apr 22 2009 /ntfs marder-1# umount -a umount: /pcfs: not currently mounted umount: /cdrom: not currently mounted umount: unmount of /usr failed: Device busy marder-1# !ls ls -ld /drvc /ntfs drwxrwxrwx 2 root wheel 512 Jan 13 15:03 /drvc drwxr-xr-x 2 root wheel 512 Jan 13 20:24 /ntfs Anyone got any idea what the cause is? marder-1# cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/da0s3b none swap sw 0 0 /dev/da0s3a / ufs rw 1 1 /dev/da1s1e /usr ufs rw 2 2 # /dev/da0s3e /var ufs rw 2 2 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 /dev/da0s1 /drvc msdos rw 0 0 /dev/fd0 /pcfs msdos rw,noauto 0 0 /dev/da0s5 /ntfs ntfs ro 0 0 marder-1# marder-1# uname -a FreeBSD marder-1 3.4-STABLE FreeBSD 3.4-STABLE #1: Thu Jan 13 19:19:35 GMT 2000 mark@marder-1:/usr/src/sys/compile/MARDER-1 i386 marder-1# -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 9:36:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.218.52.143]) by hub.freebsd.org (Postfix) with ESMTP id 62B0514C8B for ; Sat, 15 Jan 2000 09:36:51 -0800 (PST) (envelope-from ahd@kew.com) Received: from kew.com (kendra-dock.hh.kew.com [192.168.203.132]) by kendra.ne.mediaone.net (Postfix) with ESMTP id E49B5A811; Sat, 15 Jan 2000 12:36:45 -0500 (EST) Message-ID: <3880B02D.14E26676@kew.com> Date: Sat, 15 Jan 2000 12:36:45 -0500 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: tmp files (was Re: Making sure /var/tmp/vi.recover exists during reboot) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... they MFS mount /var/tmp > (at least) for the sake of optimizing compile times (cc uses /var/tmp for > > temporary files). On a reasonably fast system, I prefer using the gcc -pipe option myself. However, if you love MFS temporary files, I offer this from the gcc (1) manual page on FreeBSD 3.4: > TMPDIR comes from the environment variable TMPDIR (default > /usr/tmp if available, else /tmp). > I unsure why you think gcc uses /var/tmp. In any case, assuming /tmp is MFS, a simple update to login.conf for TMPDIR would negate the need to mount the /var/tmp as MFS as well. -ahd- -- Drew Derbyshire Internet: ahd+sig@kew.com Kendra Electronic Wonderworks Voice: 1-781-279-9812 Who me? I just wander from room to room. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 13:20:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-1-169.adsl.one.net [216.23.20.169]) by hub.freebsd.org (Postfix) with ESMTP id 86102150D4; Sat, 15 Jan 2000 13:20:06 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id QAA76429; Sat, 15 Jan 2000 16:22:03 -0500 (EST) (envelope-from cokane) Date: Sat, 15 Jan 2000 16:22:03 -0500 From: Coleman Kane To: Marcel Moolenaar Cc: Satoshi - Ports Wraith - Asami , stable@freebsd.org Subject: Re: Problems with linux_base-6.1 Message-ID: <20000115162203.A76413@evil.2y.net> References: <387E163E.16722C62@scc.nl> <3880386E.A83AB6BA@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3880386E.A83AB6BA@scc.nl>; from marcel@scc.nl on Sat, Jan 15, 2000 at 04:06:55AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar had the audacity to say: > People running into problems now should be running -stable, not 3.4 > release or older, right? > Yes, I am. Upgraded my source tree last week. --cokane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 13:56:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 42D8914E7E for ; Sat, 15 Jan 2000 13:56:30 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000115215413.YAF15357.mail.rdc3.on.home.com@tristan.net>; Sat, 15 Jan 2000 13:54:13 -0800 Content-Length: 1255 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001140144.SAA07443@freeway.dcfinc.com> Date: Sat, 15 Jan 2000 16:52:59 -0500 (EST) From: Colin To: "Chad R. Larson" Subject: Re: access floppy rw to lock system Cc: freebsd-stable@FreeBSD.ORG, drek@MonsterByMistake.Com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Jan-2000 Chad R. Larson wrote: > > Well, I was protesting the logic of doing a read/write mount of read-only > media. Mount it R/O and there is no issue. > > You wouldn't mount a CD-ROM read/write, would you? > Of course not ;) My point was if you inserted the floppy with the intent of writing to it (eg to create a set of boot disks to do another FreeBSD install ;)) and forgot to check the location of the tab your next step will be a reboot. > And, it would have to be "unnoticed" by someone with root > permissions, or it can't be mounted at all (or written to, either). > I didn't realize "root" access automagically bestowed an inability to make mistakes ;) I agree root needs to be paying a lot more attention than a normal user, but as my kid so eloquently puts it, "stuff happens" ;) > But I will concede that doing that approximately silly thing > shouldn't hang the system. I'd probably vote that the driver should > test for write protect, and the mount(2) call should act as though > "MT_RDONLY" had been specified. > > Either that, or fail with a EPERM or ENODEV. > I guess, from this last bit, we basically agree that there is a problem here, we just don't view it's importance the same ;) cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 15 16:22:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 53D6214CBE for ; Sat, 15 Jan 2000 16:22:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id QAA46762; Sat, 15 Jan 2000 16:22:26 -0800 (PST) (envelope-from obrien) Date: Sat, 15 Jan 2000 16:22:26 -0800 From: "David O'Brien" To: wonko@entropy.tmok.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Making sure /var/tmp/vi.recover exists during reboot Message-ID: <20000115162226.B46715@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001141602.LAA51996@blackhelicopters.org> <200001141817.NAA04478@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <200001141817.NAA04478@entropy.tmok.com> X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 14, 2000 at 01:17:52PM -0500, Brian Hechinger wrote: > > /var/tmp on MFS makes cc go faster, Then fix src/contrib/gcc/ and send me a patch. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message