From owner-freebsd-stable Sun Jul 26 02:36:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00130 for freebsd-stable-outgoing; Sun, 26 Jul 1998 02:36:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obsidian.noc.dfn.de (obsidian.noc.dfn.de [193.174.247.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00123 for ; Sun, 26 Jul 1998 02:36:06 -0700 (PDT) (envelope-from schweikh@obsidian.noc.dfn.de) Received: (from schweikh@localhost) by obsidian.noc.dfn.de (8.8.7/8.8.7) id LAA03891; Sun, 26 Jul 1998 11:35:25 +0200 (MET DST) From: Jens Schweikhardt Message-Id: <199807260935.LAA03891@obsidian.noc.dfn.de> Subject: Re: FreeBSD 2.2.7-RELEASE CDs To: oski@pacbell.net (Michael Oski) Date: Sun, 26 Jul 1998 11:35:25 +0200 (MET DST) Cc: damascus@eden.rutgers.edu, freebsd-stable@FreeBSD.ORG In-Reply-To: <35BA2789.D4522822@pacbell.net> from "Michael Oski" at Jul 25, 98 11:44:25 am Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # # Carroll Kong wrote: # # > .... (and no... I do not really want to buy the CD since I have a # > cd-burner and FreeBSD is free. ) :) # # That's not the only purpose of buying the CD. Many people pay the (relatively) minor # cost as (another?) way of supporting the project. # # MO! Right. Carroll, how many hours have you frobbed your CDROM contents by now? Is this worth about 30 bucks? On the other hand, 2.2.7 is a 4 CD set and when you want to customize your own smaller set, maybe just a 2 CD set, then I think you can't copy only two of the 2.2.7R CDs. The install CD and the ports distfiles required at least 3 discs for 2.2.6. Regards, -- Jens Schweikhardt http://www.shuttle.de/schweikh/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 04:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12147 for freebsd-stable-outgoing; Sun, 26 Jul 1998 04:09:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from socko.cdnow.com (socko.cdnow.com [209.83.166.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12138 for ; Sun, 26 Jul 1998 04:09:26 -0700 (PDT) (envelope-from heller@daria.cdnow.com) Received: from daria.cdnow.com (daria.cdnow.com [209.83.166.60]) by socko.cdnow.com (8.9.0/8.9.0) with ESMTP id HAA27688; Sun, 26 Jul 1998 07:08:59 -0400 (EDT) Received: (from heller@localhost) by daria.cdnow.com (8.8.8/8.8.8) id HAA12407; Sun, 26 Jul 1998 07:06:26 -0400 (EDT) From: "A. Karl Heller" Message-Id: <199807261106.HAA12407@daria.cdnow.com> Subject: Re: MX CNAME To: pajarola@cybertime.ch (Rico Pajarola) Date: Sun, 26 Jul 1998 07:06:25 -0400 (EDT) Cc: kpielorz@tdx.co.uk, freebsd-stable@FreeBSD.ORG Reply-To: heller@cdnow.com In-Reply-To: <3.0.32.19980726062451.00742df8@www.dlc.cybertime.ch> from "Rico Pajarola" at Jul 26, 98 06:26:38 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, the sendmail book says that you should not ( ie. can't ) use CNAMEs in MX records. I ran into problems with this a while back but can't remember what. DNS should also not be a CNAME. One way of doing it as sugested below is to create a virtual host. That way you can move the dns ip around to other machines when the time comes. pop and smtp hosts for pop clients are CNAMED to the dns machines real hostname. Karl > At 11:35 24.07.98 +0100, you wrote: > >I am a little confused now... > so was I when I first encountered this problem ;) > >Imagine we have a DNS server, which runs on a machine called > >'skyhawk.domain.com', we think we're being clever by setting up a CNAME > which is > >'dns0.domain.com' which in turn points to 'skyhawk.domain.com'. > > > >Why do this? - So that when/if we move our DNS server all our Internic > records > >which point to 'dns0.domain.com' can be moved easily (by changing the CNAME). > I did this some time ago, and it didn't work very well, ie, nothing > complained, but it dind't work for some clients, and murphy's law says that > it's your paying (and not very patient) customer who finds out first :) > The difference between a NS reference to a CNAME and two A records pointing > to the same IP address is that the error with the 2 A records only shows up > if you're doing additional database consistency checks (which aren't > necessary for looking up the data), while an NS -> CNAME is plain wrong, > and some broken clients (eg some M$ products) just can't resolve them. > >I don't mind using 'IN A' records for this - but isn't this going to muck up? > >e.g. > > > >$ORIGIN = "domain.com" > >skyhawk IN A 192.168.100.1 > >dns0 IN A 192.168.100.1 > > > >Isn't this going to muckup people who do reverse DNS queries? If they resolve > >'dns0.domain.com' they will get '192.168.100.1' which reverse to > >'skyhawk.domain.com' - which isn't going to please too many paranoid > >wrappers?/people? > > > >The only other choice is to put 'skyhawk.domain.com' in the Internic records, > >and hope that machine's role never changes? > I don't think that a lot of people will do reverse lookups on your DNS > server (at least not when doing queries), but the best way to go (if you > have an ip address to waste) would be to make an alias ip (using ifconfig > alias) and using this for your dns server, and if > you're using bind 8.x, you can limit your dns to use this address > exclusively. If the machine's role ever changes, you don't even have to > change any DNS database files, you just take down the alias (ifconfig > delete), set up the same alias on the new machine, > fire up the dns server (or send it a HUP signal to recognize the new > address), and there you are, you moved your nameserver to another machine, > and don't even have DNS cache problems (which can be very nasty, as bad old > DNS data can stay in caches for weeks, if you didn't change the ttl values > early enough) > Another method would be to make dns0 the A record, and skyhawk the CNAME > (not very beautiful though) > >Maybe I'm just getting confused? (Hence the mail, you seem to know what your > >talking about... ) > I learnt it by doing it wrong first 8-> > Everything clear now? > Rico Pajarola > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- A. Karl Heller - Senior Systems Engineer - heller@cdnow.com ----------------------------------------------------------------------------- An unbreakable toy is useful for breaking other toys. Do something unusual today. Accomplish work on the computer. >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 05:02:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17416 for freebsd-stable-outgoing; Sun, 26 Jul 1998 05:02:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17405 for ; Sun, 26 Jul 1998 05:02:34 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id OAA23274; Sun, 26 Jul 1998 14:02:06 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 26 Jul 1998 14:02:06 +0200 (MET DST) Mime-Version: 1.0 To: Matt White Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation in 2.2.7? References: <19980725175847.15249@oakwood.k12.oh.us> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 26 Jul 1998 14:02:05 +0200 In-Reply-To: Matt White's message of "Sat, 25 Jul 1998 17:58:47 -0400" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA17412 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt White writes: > I did a bulidworld/installworld combo, and as far as I can tell everything > else is working okay. You didn't forget to recompile your kernel now, did you? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 06:40:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24730 for freebsd-stable-outgoing; Sun, 26 Jul 1998 06:40:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from oak.oakwood.k12.oh.us (mwhite@oak.oakwood.k12.oh.us [156.63.171.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24720 for ; Sun, 26 Jul 1998 06:40:25 -0700 (PDT) (envelope-from mwhite@oak.oakwood.k12.oh.us) Received: (from mwhite@localhost) by oak.oakwood.k12.oh.us (8.8.8/8.8.7) id JAA02397; Sun, 26 Jul 1998 09:39:29 -0400 (EDT) (envelope-from mwhite) Message-ID: <19980726093928.02110@oakwood.k12.oh.us> Date: Sun, 26 Jul 1998 09:39:28 -0400 From: Matt White To: unsafe at any speed Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation in 2.2.7? References: <19980725175847.15249@oakwood.k12.oh.us> <19980725225507.37554@oakwood.k12.oh.us> <35BAA49D.E2102342@compecon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <35BAA49D.E2102342@compecon.com>; from unsafe at any speed on Sun, Jul 26, 1998 at 03:38:05AM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 03:38:05AM +0000, unsafe at any speed wrote: > Are you sure you cvsup'ed your LKM source along with everything else? I have > heard of screwy problems like this when the kernel and LKMs (in this case, > the > linux one) get out of sync. I supped src-all, and ports-all. Is there something else I need to sup? -- Matt White me.homepage[0] = "http://www.oakwood.k12.oh.us/staff/mwhite"; me.homepage[1] = "http://www.bunnynet.org"; me.email[0] = "mwhite@oakwood.k12.oh.us"; me.email[1] = "mwhite@donet.com"; me.email[2] = "s012mrw@discover.wright.edu"; me.email[3] = "bunny@bunnynet.org"; me.email[4] = "matt-white@usa.net"; The message was brought to you by the letters B, S and D. Linux: The choice of a GNUtered generation! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 06:41:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24784 for freebsd-stable-outgoing; Sun, 26 Jul 1998 06:41:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from oak.oakwood.k12.oh.us (mwhite@oak.oakwood.k12.oh.us [156.63.171.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24777 for ; Sun, 26 Jul 1998 06:41:11 -0700 (PDT) (envelope-from mwhite@oak.oakwood.k12.oh.us) Received: (from mwhite@localhost) by oak.oakwood.k12.oh.us (8.8.8/8.8.7) id JAA02442; Sun, 26 Jul 1998 09:40:45 -0400 (EDT) (envelope-from mwhite) Message-ID: <19980726094045.09239@oakwood.k12.oh.us> Date: Sun, 26 Jul 1998 09:40:45 -0400 From: Matt White To: mikeg Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation in 2.2.7? References: <19980725175847.15249@oakwood.k12.oh.us> <35BAA5BA.52CEF4E0@hoflink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <35BAA5BA.52CEF4E0@hoflink.com>; from mikeg on Sat, Jul 25, 1998 at 11:42:50PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 25, 1998 at 11:42:50PM -0400, mikeg wrote: > I'm assuming you also re-built the kernel, if not that might be the problem. Yup. I did it a second time just to be sure. -- Matt White me.homepage[0] = "http://www.oakwood.k12.oh.us/staff/mwhite"; me.homepage[1] = "http://www.bunnynet.org"; me.email[0] = "mwhite@oakwood.k12.oh.us"; me.email[1] = "mwhite@donet.com"; me.email[2] = "s012mrw@discover.wright.edu"; me.email[3] = "bunny@bunnynet.org"; me.email[4] = "matt-white@usa.net"; The message was brought to you by the letters B, S and D. Linux: The choice of a GNUtered generation! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 12:50:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28997 for freebsd-stable-outgoing; Sun, 26 Jul 1998 12:50:21 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.cybcon.com (root@mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28977 for ; Sun, 26 Jul 1998 12:50:12 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id MAA13114 for ; Sun, 26 Jul 1998 12:49:41 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 26 Jul 1998 12:48:59 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: freebsd-stable@FreeBSD.ORG Subject: 3.0 Snap---- Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I dont know if this is the right list, but.............Would you all (those of you who are running it) consider 3.0 useable and stable to use in a work enviroment? I know it is beta but I just had to ask.... ---------------------------------- William Woods --> FreeBSD 2.2.7 <-- Date: 26-Jul-98 Time: 12:34:57 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 14:25:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09903 for freebsd-stable-outgoing; Sun, 26 Jul 1998 14:25:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09873 for ; Sun, 26 Jul 1998 14:25:25 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA16093; Sun, 26 Jul 1998 22:23:55 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807262123.WAA16093@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: bahwi@technologist.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: Modem problems In-reply-to: Your message of "Sun, 26 Jul 1998 00:13:50 CDT." <199807260522.AAA27525@cs1.cityscope.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 22:23:55 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sorry if this is a stupid question, but I'd really like to install > FreeBSD again, and this time it gets 3 gigs instead of one. > I am using the latest boot disk, got it over 30 mins ago. (midnight > central time) and get it all ready, go to media, ftp site, /dev/cuaa2 > (2.2.5 and 2.2.6 could NOT find the modem there, 2.2.7 does so I > can finally use FreeBSD again) On alt-f2(the errors area) I get a > "silo overflow" or something like that. I dial in, it seems weird, I only > get the character before last shown to me when I type, and for > newlines, nothing until I type something. I backspace it and enter > my username and password, it tells me PPP connection from blah > blah to blah blah beginning. The term switches into packet mode > on it's own, and tells me something like this(forgive my memory) > "NewPhase: Network" > "NewPhase: Authenticate" > for a bit then > "NewPhase: Terminate" > twice and then hangs up. I haven't had FreeBSD on my home > system for so long. The error may be my modem, although when it > worked with FreeBSD 2.2.5(long story) it never gave me that error, > nor when I user a terminal program in Win95 and Dos. Any > help/suggestions are appreciated. Hi, Phase diagnostics are now turned on by default at install time. From the looks of the above, your ISP is doing either chap or pap authentication and you haven't ``set authmame blah'' and ``set authkey moreblah'' - so that ppp can do it's bit. -- 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 Sun Jul 26 14:49:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13728 for freebsd-stable-outgoing; Sun, 26 Jul 1998 14:49:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from socko.cdnow.com (socko.cdnow.com [209.83.166.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13710 for ; Sun, 26 Jul 1998 14:49:31 -0700 (PDT) (envelope-from heller@daria.cdnow.com) Received: from daria.cdnow.com (daria.cdnow.com [209.83.166.60]) by socko.cdnow.com (8.9.0/8.9.0) with ESMTP id RAA22615 for ; Sun, 26 Jul 1998 17:49:03 -0400 (EDT) Received: (from heller@localhost) by daria.cdnow.com (8.8.8/8.8.8) id RAA12894 for freebsd-stable@freebsd.org; Sun, 26 Jul 1998 17:46:29 -0400 (EDT) From: "A. Karl Heller" Message-Id: <199807262146.RAA12894@daria.cdnow.com> Subject: FreeBSD-stable on Virtual PC To: freebsd-stable@FreeBSD.ORG Date: Sun, 26 Jul 1998 17:46:29 -0400 (EDT) Reply-To: heller@cdnow.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone attempted to get FreeBSD stable working on the Virtual PC emulator for the MAC? http://www.cs.mu.OZ.AU/tsa/projs/vpcbsd.html describes how to get NetBSD working and I am now running that. I would MUCH rather be running FreeBSD. Karl -- A. Karl Heller - Senior Systems Engineer - heller@cdnow.com ----------------------------------------------------------------------------- An unbreakable toy is useful for breaking other toys. Do something unusual today. Accomplish work on the computer. >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 15:48:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22140 for freebsd-stable-outgoing; Sun, 26 Jul 1998 15:48:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hoflink.com (root@hoflink.com [199.173.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22130 for ; Sun, 26 Jul 1998 15:48:46 -0700 (PDT) (envelope-from mikeg@hoflink.com) Received: from hoflink.com (ppp5.hoflink.com [199.173.65.105]) by hoflink.com (8.8.5/8.6.12) with ESMTP id SAA08774 for ; Sun, 26 Jul 1998 18:52:50 -0400 (EDT) Message-ID: <35BBB225.6EA75640@hoflink.com> Date: Sun, 26 Jul 1998 18:48:06 -0400 From: Michael Graziano X-Mailer: Mozilla 4.5b1 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Stable@FreeBSD.ORG Subject: Re: FreeBSD-stable on Virtual PC References: <199807262146.RAA12894@daria.cdnow.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A. Karl Heller wrote: > Has anyone attempted to get FreeBSD stable working on the Virtual > PC emulator for the MAC? > > http://www.cs.mu.OZ.AU/tsa/projs/vpcbsd.html describes how to get NetBSD > working and I am now running that. I would MUCH rather be running > FreeBSD. It looks possible just glancing through the modifications that were made, but it might be an awful lot of work. A cheap 386 with a 1.2 gig HDD should work fine for a basic system though. If you (manually) patch the relevant files to be somewhat like what this site suggests, I would give odds that the remaining problems (if any) could be ironed out. (Don't quote me on that, I am terrible with macintosh systems. They don't like me!) > > > > Karl > > -- > A. Karl Heller - Senior Systems Engineer - heller@cdnow.com > ----------------------------------------------------------------------------- > An unbreakable toy is useful for breaking other toys. > Do something unusual today. Accomplish work on the computer. > >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< Hmmm, my foot is an unbreakable toy, I've broken computers with that before :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 16:53:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28569 for freebsd-stable-outgoing; Sun, 26 Jul 1998 16:53:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28557 for ; Sun, 26 Jul 1998 16:53:39 -0700 (PDT) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id JAA12997; Mon, 27 Jul 1998 09:53:05 +1000 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd012995; Sun Jul 26 23:53:01 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id JAA20092; Mon, 27 Jul 1998 09:53:34 +1000 (EST) Message-Id: <199807262353.JAA20092@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Rico Pajarola Cc: Karl Pielorz , freebsd-stable@FreeBSD.ORG Subject: Re: MX CNAME In-reply-to: Your message of Sun, 26 Jul 1998 06:26:38 +0200. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 09:52:57 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A reminder about updating DNS info - the NIC needs to know both the name and the IP address of your DNS servers so that (in the common case where the nameservers for foo.com live inside foo.com) the nameserver can return a so-called "glue record" with the IP address. Otherwise, when you ask "who is the domain server for foo.com" you get told "dns.foo.com" but you can't look up the address of dns.foo.com without knowing the answer to the question you are trying to ask in the first place! The upshot is changing _either_ the name or the IP address of a listed name server requires updates to the NIC database. So tricks with cnames etc don't actually add much flexibility. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 17:06:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00583 for freebsd-stable-outgoing; Sun, 26 Jul 1998 17:06:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00560 for ; Sun, 26 Jul 1998 17:06:07 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA12722; Sun, 26 Jul 1998 17:05:11 -0700 (PDT) Message-Id: <199807270005.RAA12722@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: heller@cdnow.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD-stable on Virtual PC In-reply-to: Your message of "Sun, 26 Jul 1998 17:46:29 EDT." <199807262146.RAA12894@daria.cdnow.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 17:05:11 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Has anyone attempted to get FreeBSD stable working on the Virtual > PC emulator for the MAC? > > http://www.cs.mu.OZ.AU/tsa/projs/vpcbsd.html describes how to get NetBSD > working and I am now running that. I would MUCH rather be running > FreeBSD. Very shortly after VPC was released, a minor problem with their CPU emulation was found (and extremely promptly fixed). If your VPC is up to date (including all the fixes from Connectix) you should have no trouble at all running FreeBSD. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sun Jul 26 18:17:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12521 for freebsd-stable-outgoing; Sun, 26 Jul 1998 18:17:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gutenberg.uoregon.edu (gutenberg.uoregon.edu [128.223.56.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12513 for ; Sun, 26 Jul 1998 18:17:42 -0700 (PDT) (envelope-from sharding@gutenberg.uoregon.edu) Received: from localhost (sharding@localhost) by gutenberg.uoregon.edu (8.9.1/8.9.1) with SMTP id SAA24596; Sun, 26 Jul 1998 18:20:58 -0700 (PDT) Date: Sun, 26 Jul 1998 18:20:58 -0700 From: Sean Harding Reply-To: Sean Harding To: Mike Smith cc: heller@cdnow.com, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD-stable on Virtual PC In-Reply-To: <199807270005.RAA12722@antipodes.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 Sun, 26 Jul 1998, Mike Smith wrote: > emulation was found (and extremely promptly fixed). If your VPC is up > to date (including all the fixes from Connectix) you should have no > trouble at all running FreeBSD. Unfortunately, this turns out to be untrue. No one I know has actually been able to get it working (I've tried it with the newest release of VPC and BSD 2.2.1-2.2.6). It always crashes in the same spot... Recently at least three other people have happened to ask about this (mostly on -questions) and they all seem to have the same problem too... Sean -- Sean Harding sharding@oregon.uoregon.edu|"It's not a habit, it's cool. http://gladstone.uoregon.edu/~sharding/ | I feel alive." NeXTMail OK! | --k's Choice To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 18:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13284 for freebsd-stable-outgoing; Sun, 26 Jul 1998 18:22:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13199 for ; Sun, 26 Jul 1998 18:22:06 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA13156; Sun, 26 Jul 1998 18:20:52 -0700 (PDT) Message-Id: <199807270120.SAA13156@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Sean Harding cc: heller@cdnow.com, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD-stable on Virtual PC In-reply-to: Your message of "Sun, 26 Jul 1998 18:20:58 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 18:20:52 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 26 Jul 1998, Mike Smith wrote: > > > emulation was found (and extremely promptly fixed). If your VPC is up > > to date (including all the fixes from Connectix) you should have no > > trouble at all running FreeBSD. > > Unfortunately, this turns out to be untrue. No one I know has actually > been able to get it working (I've tried it with the newest release of VPC > and BSD 2.2.1-2.2.6). It always crashes in the same spot... > > Recently at least three other people have happened to ask about this > (mostly on -questions) and they all seem to have the same problem too... Ok, sounds like VPC has changed a bit then. 8( Where is "the same spot"? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sun Jul 26 18:50:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16825 for freebsd-stable-outgoing; Sun, 26 Jul 1998 18:50:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gutenberg.uoregon.edu (gutenberg.uoregon.edu [128.223.56.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16815 for ; Sun, 26 Jul 1998 18:50:29 -0700 (PDT) (envelope-from sharding@gutenberg.uoregon.edu) Received: from localhost (sharding@localhost) by gutenberg.uoregon.edu (8.9.1/8.9.1) with SMTP id SAA24674; Sun, 26 Jul 1998 18:53:45 -0700 (PDT) Date: Sun, 26 Jul 1998 18:53:45 -0700 From: Sean Harding Reply-To: Sean Harding To: Mike Smith cc: Sean Harding , heller@cdnow.com, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD-stable on Virtual PC In-Reply-To: <199807270120.SAA13156@antipodes.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 Sun, 26 Jul 1998, Mike Smith wrote: > Ok, sounds like VPC has changed a bit then. 8( Actually, it didn't work in the version that was supposedly fixed either. I've been trying this with every version since 1.0, and it has never worked on any machine I've tried it on :-\ > Where is "the same spot"? IIRC, it's at 9% in extracing /bin...I used to have a screen shot of it around here somewhere, but I can't find it anymore. Sean -- Sean Harding sharding@oregon.uoregon.edu|"It's not a habit, it's cool. http://gladstone.uoregon.edu/~sharding/ | I feel alive." NeXTMail OK! | --k's Choice To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 19:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18810 for freebsd-stable-outgoing; Sun, 26 Jul 1998 19:09:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18803 for ; Sun, 26 Jul 1998 19:09:27 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA13469; Sun, 26 Jul 1998 19:08:20 -0700 (PDT) Message-Id: <199807270208.TAA13469@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Sean Harding cc: Mike Smith , heller@cdnow.com, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD-stable on Virtual PC In-reply-to: Your message of "Sun, 26 Jul 1998 18:53:45 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 19:08:19 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 26 Jul 1998, Mike Smith wrote: > > > Ok, sounds like VPC has changed a bit then. 8( > > Actually, it didn't work in the version that was supposedly fixed either. > I've been trying this with every version since 1.0, and it has never > worked on any machine I've tried it on :-\ > > > Where is "the same spot"? > > IIRC, it's at 9% in extracing /bin...I used to have a screen shot of it > around here somewhere, but I can't find it anymore. That doesn't tell us very much. What is the failure mode? Details details details. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sun Jul 26 19:50:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23451 for freebsd-stable-outgoing; Sun, 26 Jul 1998 19:50:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from socko.cdnow.com (socko.cdnow.com [209.83.166.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23436 for ; Sun, 26 Jul 1998 19:50:23 -0700 (PDT) (envelope-from heller@daria.cdnow.com) Received: from daria.cdnow.com (daria.cdnow.com [209.83.166.60]) by socko.cdnow.com (8.9.0/8.9.0) with ESMTP id WAA21970; Sun, 26 Jul 1998 22:49:51 -0400 (EDT) Received: (from heller@localhost) by daria.cdnow.com (8.8.8/8.8.8) id WAA13285; Sun, 26 Jul 1998 22:47:15 -0400 (EDT) From: "A. Karl Heller" Message-Id: <199807270247.WAA13285@daria.cdnow.com> Subject: Re: FreeBSD-stable on Virtual PC To: mike@smith.net.au (Mike Smith) Date: Sun, 26 Jul 1998 22:47:15 -0400 (EDT) Cc: sharding@OREGON.UOREGON.EDU, mike@smith.net.au, heller@cdnow.com, freebsd-stable@FreeBSD.ORG Reply-To: heller@cdnow.com In-Reply-To: <199807270208.TAA13469@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 07:08:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of Apple guru's did get FreeBSD installed from a Dos partition. ( I'm so used to installing over the net now that this method was spooking. = ) On bootup from the harddisk getty kept re-spawing and lots of the deamons cored. I'd like to see FreeBSD run on VPC, heck I would like it to run on a 14CPU Sun Ultra 4000..but.. Karl > > On Sun, 26 Jul 1998, Mike Smith wrote: > > > > > Ok, sounds like VPC has changed a bit then. 8( > > > > Actually, it didn't work in the version that was supposedly fixed either. > > I've been trying this with every version since 1.0, and it has never > > worked on any machine I've tried it on :-\ > > > > > Where is "the same spot"? > > > > IIRC, it's at 9% in extracing /bin...I used to have a screen shot of it > > around here somewhere, but I can't find it anymore. > That doesn't tell us very much. What is the failure mode? Details > details details. 8) > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- A. Karl Heller - Senior Systems Engineer - heller@cdnow.com ----------------------------------------------------------------------------- An unbreakable toy is useful for breaking other toys. Do something unusual today. Accomplish work on the computer. >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 26 20:46:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00184 for freebsd-stable-outgoing; Sun, 26 Jul 1998 20:46:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gutenberg.uoregon.edu (gutenberg.uoregon.edu [128.223.56.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00177 for ; Sun, 26 Jul 1998 20:46:17 -0700 (PDT) (envelope-from sharding@gutenberg.uoregon.edu) Received: from localhost (sharding@localhost) by gutenberg.uoregon.edu (8.9.1/8.9.1) with SMTP id UAA24930; Sun, 26 Jul 1998 20:49:34 -0700 (PDT) Date: Sun, 26 Jul 1998 20:49:34 -0700 From: Sean Harding Reply-To: Sean Harding To: Mike Smith cc: Sean Harding , heller@cdnow.com, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD-stable on Virtual PC In-Reply-To: <199807270208.TAA13469@antipodes.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 Sun, 26 Jul 1998, Mike Smith wrote: > That doesn't tell us very much. What is the failure mode? Details > details details. 8) I haven't personally tried it for a while (since 2.2.6 first came out), and I haven't a whole lot of interest since I really have no desire to actually run FreeBSD in VPC...I no one else can re-produce the error, let me know and I can set my system up to try it again. But if someone else can play with it, it would be preferable because I don't have a lot of time to fight with it. Sean -- Sean Harding sharding@oregon.uoregon.edu|"It's not a habit, it's cool. http://gladstone.uoregon.edu/~sharding/ | I feel alive." NeXTMail OK! | --k's Choice To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 00:54:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25430 for freebsd-stable-outgoing; Mon, 27 Jul 1998 00:54:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.carif.asso.fr (ns.carif.asso.fr [194.98.158.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25425 for ; Mon, 27 Jul 1998 00:54:40 -0700 (PDT) (envelope-from stef@rafiki.carif.asso.fr) Received: from rafiki.carif.asso.fr (rafiki.intranet.carif.asso.fr [10.100.10.99]) by ns.carif.asso.fr (8.9.0/8.9.0) with ESMTP id JAA07791; Mon, 27 Jul 1998 09:43:52 +0200 (CEST) Received: (from stef@localhost) by rafiki.carif.asso.fr (8.9.0/8.9.0) id JAA26503; Mon, 27 Jul 1998 09:54:57 +0200 (CEST) Message-ID: <19980727095456.A26476@rafiki.intranet.carif.asso.fr> Date: Mon, 27 Jul 1998 09:54:56 +0200 From: Stephane Marzloff To: Tetsuro FURUYA , freebsd-stable@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Disk problem. References: <19980708173036.A14305@rafiki.intranet.carif.asso.fr> <199807082149.GAA01464@galois.tf.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: <199807082149.GAA01464@galois.tf.or.jp>; from Tetsuro FURUYA on Thu, Jul 09, 1998 at 06:49:32AM +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dans un message du 09 Jul à 06:49, Tetsuro FURUYA écrivait : > > > Your ide disk sector is broken. > Try > bad144 -s -v /dev/wd0 > or > badsect & fsck (This is rather difficult. So, please read man). Hello.. I'm back. So I launch the 'bad144 -s -v wd0, it run about 48H for a 4,8Go. This is the report : [18:22] root@rafiki:~ # bad144 -s -v wd0 cyl: 621, tracks: 255, secs: 63, sec/cyl: 16065, start: 0, end: 9992178 9976365 of 9992178 blocks ( 99%) bad block information at sector 9992304 in /dev/rwd0c: cartridge serial number: -1108550333(10) bt_flag=a70a(16)? bad144: /dev/rwd0c: bad flag in bad-sector table bad144: /dev/rwd0c: bad magic number bad144: cyl/trk/sect out of range in existing entry: sn=656226137, cn=40848, tn=44, sn=245 bad144: cyl/trk/sect out of range in existing entry: sn=429083853, cn=26709, tn=58, sn=114 bad144: bad sector file is out of order bad144: cyl/trk/sect out of range in existing entry: sn=55932712, cn=3481, tn=164, sn=115 bad144: cyl/trk/sect out of range in existing entry: sn=235040824, cn=14630, tn=156, sn=46 bad144: cyl/trk/sect out of range in existing entry: sn=139971565, cn=8712, tn=208, sn=181 bad144: cyl/trk/sect out of range in existing entry: sn=432373834, cn=26914, tn=4, sn=172 bad144: cyl/trk/sect out of range in existing entry: sn=1020651532, cn=63532, tn=156, sn=124 bad144: cyl/trk/sect out of range in existing entry: sn=1033067997, cn=64305, tn=129, sn=45 bad144: cyl/trk/sect out of range in existing entry: sn=774830514, cn=48230, tn=247, sn=3 bad144: cyl/trk/sect out of range in existing entry: sn=732388536, cn=45589, tn=16, sn=243 bad144: cyl/trk/sect out of range in existing entry: sn=341322798, cn=21246, tn=90, sn=138 bad144: cyl/trk/sect out of range in existing entry: sn=775992176, cn=48303, tn=70, sn=71 bad144: cyl/trk/sect out of range in existing entry: sn=660257597, cn=41099, tn=34, sn=20 bad144: cyl/trk/sect out of range in existing entry: sn=229406674, cn=14279, tn=228, sn=175 bad144: cyl/trk/sect out of range in existing entry: sn=420181306, cn=26155, tn=19, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=743786915, cn=46298, tn=148, sn=221 bad144: cyl/trk/sect out of range in existing entry: sn=364274930, cn=22675, tn=13, sn=236 bad144: cyl/trk/sect out of range in existing entry: sn=806931145, cn=50229, tn=32, sn=244 bad144: cyl/trk/sect out of range in existing entry: sn=319622456, cn=19895, tn=144, sn=209 bad144: cyl/trk/sect out of range in existing entry: sn=69786761, cn=4344, tn=6, sn=23 bad144: cyl/trk/sect out of range in existing entry: sn=878984447, cn=54714, tn=64, sn=5 bad144: cyl/trk/sect out of range in existing entry: sn=654975399, cn=40770, tn=84, sn=57 bad144: cyl/trk/sect out of range in existing entry: sn=996521633, cn=62030, tn=153, sn=44 bad144: cyl/trk/sect out of range in existing entry: sn=922585577, cn=57428, tn=75, sn=32 bad144: cyl/trk/sect out of range in existing entry: sn=959178499, cn=59706, tn=25, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=132718702, cn=8261, tn=91, sn=4 bad144: cyl/trk/sect out of range in existing entry: sn=671584852, cn=41804, tn=53, sn=253 bad144: cyl/trk/sect out of range in existing entry: sn=526881905, cn=32796, tn=221, sn=242 bad144: cyl/trk/sect out of range in existing entry: sn=718168866, cn=44703, tn=240, sn=51 bad144: cyl/trk/sect out of range in existing entry: sn=766196125, cn=47693, tn=126, sn=142 bad144: cyl/trk/sect out of range in existing entry: sn=223217715, cn=13894, tn=165, sn=210 bad144: cyl/trk/sect out of range in existing entry: sn=972505995, cn=60535, tn=177, sn=69 bad144: cyl/trk/sect out of range in existing entry: sn=415442093, cn=25860, tn=15, sn=248 bad144: cyl/trk/sect out of range in existing entry: sn=632451988, cn=39368, tn=79, sn=91 bad144: cyl/trk/sect out of range in existing entry: sn=133211312, cn=8292, tn=3, sn=143 bad144: cyl/trk/sect out of range in existing entry: sn=481501498, cn=29972, tn=20, sn=58 bad144: cyl/trk/sect out of range in existing entry: sn=969055646, cn=60320, tn=235, sn=41 bad144: cyl/trk/sect out of range in existing entry: sn=895632024, cn=55750, tn=130, sn=84 bad144: cyl/trk/sect out of range in existing entry: sn=1043419453, cn=64949, tn=215, sn=223 bad144: cyl/trk/sect out of range in existing entry: sn=914196557, cn=56906, tn=26, sn=29 bad144: cyl/trk/sect out of range in existing entry: sn=1023321330, cn=63698, tn=202, sn=234 bad144: cyl/trk/sect out of range in existing entry: sn=154024950, cn=9587, tn=153, sn=156 bad144: cyl/trk/sect out of range in existing entry: sn=17153090, cn=1067, tn=185, sn=80 bad144: cyl/trk/sect out of range in existing entry: sn=141306790, cn=8795, tn=239, sn=58 bad144: cyl/trk/sect out of range in existing entry: sn=427637130, cn=26619, tn=43, sn=186 bad144: cyl/trk/sect out of range in existing entry: sn=674534733, cn=41987, tn=212, sn=222 bad144: cyl/trk/sect out of range in existing entry: sn=190613989, cn=11865, tn=41, sn=181 bad144: cyl/trk/sect out of range in existing entry: sn=963917970, cn=60001, tn=30, sn=15 bad144: cyl/trk/sect out of range in existing entry: sn=919108812, cn=57211, tn=221, sn=174 bad144: cyl/trk/sect out of range in existing entry: sn=881383453, cn=54863, tn=148, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=1052017914, cn=65485, tn=19, sn=192 bad144: cyl/trk/sect out of range in existing entry: sn=817883596, cn=50910, tn=227, sn=145 bad144: cyl/trk/sect out of range in existing entry: sn=934650625, cn=58179, tn=77, sn=139 bad144: cyl/trk/sect out of range in existing entry: sn=286365682, cn=17825, tn=109, sn=190 bad144: cyl/trk/sect out of range in existing entry: sn=593789805, cn=36961, tn=176, sn=252 bad144: cyl/trk/sect out of range in existing entry: sn=268581566, cn=16718, tn=109, sn=29 bad144: cyl/trk/sect out of range in existing entry: sn=880244385, cn=54792, tn=171, sn=132 bad144: cyl/trk/sect out of range in existing entry: sn=672804843, cn=41880, tn=40, sn=123 bad144: cyl/trk/sect out of range in existing entry: sn=157916182, cn=9829, tn=208, sn=193 bad144: cyl/trk/sect out of range in existing entry: sn=54923655, cn=3418, tn=214, sn=3 bad144: cyl/trk/sect out of range in existing entry: sn=413300750, cn=25726, tn=197, sn=149 bad144: cyl/trk/sect out of range in existing entry: sn=83441217, cn=5193, tn=245, sn=237 bad144: cyl/trk/sect out of range in existing entry: sn=577960943, cn=35976, tn=102, sn=77 bad144: cyl/trk/sect out of range in existing entry: sn=909939418, cn=56641, tn=25, sn=178 bad144: cyl/trk/sect out of range in existing entry: sn=314340258, cn=19566, tn=194, sn=246 bad144: cyl/trk/sect out of range in existing entry: sn=590522163, cn=36758, tn=76, sn=105 bad144: cyl/trk/sect out of range in existing entry: sn=757069251, cn=47125, tn=94, sn=204 bad144: cyl/trk/sect out of range in existing entry: sn=57704950, cn=3591, tn=244, sn=163 bad144: cyl/trk/sect out of range in existing entry: sn=1031537503, cn=64210, tn=60, sn=73 bad144: cyl/trk/sect out of range in existing entry: sn=891108017, cn=55468, tn=229, sn=170 bad144: cyl/trk/sect out of range in existing entry: sn=128089615, cn=7973, tn=53, sn=31 bad144: cyl/trk/sect out of range in existing entry: sn=660723924, cn=41128, tn=38, sn=210 bad144: cyl/trk/sect out of range in existing entry: sn=329143763, cn=20488, tn=61, sn=200 bad144: cyl/trk/sect out of range in existing entry: sn=479301437, cn=29835, tn=34, sn=20 bad144: cyl/trk/sect out of range in existing entry: sn=229406674, cn=14279, tn=228, sn=175 bad144: cyl/trk/sect out of range in existing entry: sn=420181306, cn=26155, tn=19, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=743786915, cn=46298, tn=148, sn=221 bad144: cyl/trk/sect out of range in existing entry: sn=364274930, cn=22675, tn=13, sn=236 bad144: cyl/trk/sect out of range in existing entry: sn=806931145, cn=50229, tn=32, sn=244 bad144: cyl/trk/sect out of range in existing entry: sn=314340258, cn=19566, tn=194, sn=246 bad144: cyl/trk/sect out of range in existing entry: sn=590522163, cn=36758, tn=76, sn=105 bad144: cyl/trk/sect out of range in existing entry: sn=757069251, cn=47125, tn=94, sn=204 bad144: cyl/trk/sect out of range in existing entry: sn=57704950, cn=3591, tn=244, sn=163 bad144: cyl/trk/sect out of range in existing entry: sn=1031537503, cn=64210, tn=60, sn=73 bad144: cyl/trk/sect out of range in existing entry: sn=891108017, cn=55468, tn=229, sn=170 bad144: cyl/trk/sect out of range in existing entry: sn=128089615, cn=7973, tn=53, sn=31 bad144: cyl/trk/sect out of range in existing entry: sn=660723924, cn=41128, tn=38, sn=210 bad144: cyl/trk/sect out of range in existing entry: sn=329143763, cn=20488, tn=61, sn=200 bad144: cyl/trk/sect out of range in existing entry: sn=479301437, cn=29835, tn=34, sn=20 bad144: cyl/trk/sect out of range in existing entry: sn=229406674, cn=14279, tn=228, sn=175 bad144: cyl/trk/sect out of range in existing entry: sn=420181306, cn=26155, tn=19, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=743786915, cn=46298, tn=148, sn=221 bad144: cyl/trk/sect out of range in existing entry: sn=364274930, cn=22675, tn=13, sn=236 bad144: cyl/trk/sect out of range in existing entry: sn=806931145, cn=50229, tn=32, sn=244 bad144: cyl/trk/sect out of range in existing entry: sn=319622456, cn=19895, tn=144, sn=209 bad144: cyl/trk/sect out of range in existing entry: sn=69786761, cn=4344, tn=6, sn=23 bad144: cyl/trk/sect out of range in existing entry: sn=878984447, cn=54714, tn=64, sn=5 bad144: cyl/trk/sect out of range in existing entry: sn=654975399, cn=40770, tn=84, sn=57 bad144: cyl/trk/sect out of range in existing entry: sn=996521633, cn=62030, tn=153, sn=44 bad144: cyl/trk/sect out of range in existing entry: sn=922585577, cn=57428, tn=75, sn=32 bad144: cyl/trk/sect out of range in existing entry: sn=959178499, cn=59706, tn=25, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=132718702, cn=8261, tn=91, sn=4 bad144: cyl/trk/sect out of range in existing entry: sn=671584852, cn=41804, tn=53, sn=253 bad144: cyl/trk/sect out of range in existing entry: sn=526881905, cn=32796, tn=221, sn=242 bad144: cyl/trk/sect out of range in existing entry: sn=718168866, cn=44703, tn=240, sn=51 bad144: cyl/trk/sect out of range in existing entry: sn=766196125, cn=47693, tn=126, sn=142 bad144: cyl/trk/sect out of range in existing entry: sn=223217715, cn=13894, tn=165, sn=210 bad144: cyl/trk/sect out of range in existing entry: sn=972505995, cn=60535, tn=177, sn=69 bad144: cyl/trk/sect out of range in existing entry: sn=415442093, cn=25860, tn=15, sn=248 bad144: cyl/trk/sect out of range in existing entry: sn=632451988, cn=39368, tn=79, sn=91 bad144: cyl/trk/sect out of range in existing entry: sn=133211312, cn=8292, tn=3, sn=143 bad144: cyl/trk/sect out of range in existing entry: sn=481501498, cn=29972, tn=20, sn=58 bad144: cyl/trk/sect out of range in existing entry: sn=969055646, cn=60320, tn=235, sn=41 bad144: cyl/trk/sect out of range in existing entry: sn=895632024, cn=55750, tn=130, sn=84 bad144: cyl/trk/sect out of range in existing entry: sn=1043419453, cn=64949, tn=215, sn=223 bad144: cyl/trk/sect out of range in existing entry: sn=914196557, cn=56906, tn=26, sn=29 bad144: cyl/trk/sect out of range in existing entry: sn=1023321330, cn=63698, tn=202, sn=234 bad144: cyl/trk/sect out of range in existing entry: sn=154024950, cn=9587, tn=153, sn=156 bad144: cyl/trk/sect out of range in existing entry: sn=17153090, cn=1067, tn=185, sn=80 bad144: cyl/trk/sect out of range in existing entry: sn=141306790, cn=8795, tn=239, sn=58 bad144: cyl/trk/sect out of range in existing entry: sn=427637130, cn=26619, tn=43, sn=186 bad144: cyl/trk/sect out of range in existing entry: sn=674534733, cn=41987, tn=212, sn=222 bad144: cyl/trk/sect out of range in existing entry: sn=190613989, cn=11865, tn=41, sn=181 bad144: cyl/trk/sect out of range in existing entry: sn=963917970, cn=60001, tn=30, sn=15 bad144: cyl/trk/sect out of range in existing entry: sn=919108812, cn=57211, tn=221, sn=174 bad144: cyl/trk/sect out of range in existing entry: sn=881383453, cn=54863, tn=148, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=1052017914, cn=65485, tn=19, sn=192 bad144: cyl/trk/sect out of range in existing entry: sn=817883596, cn=50910, tn=227, sn=145 bad144: cyl/trk/sect out of range in existing entry: sn=934650625, cn=58179, tn=77, sn=139 bad144: cyl/trk/sect out of range in existing entry: sn=286365682, cn=17825, tn=109, sn=190 bad144: cyl/trk/sect out of range in existing entry: sn=593789805, cn=36961, tn=176, sn=252 bad144: cyl/trk/sect out of range in existing entry: sn=268581566, cn=16718, tn=109, sn=29 bad144: cyl/trk/sect out of range in existing entry: sn=880244385, cn=54792, tn=171, sn=132 bad144: cyl/trk/sect out of range in existing entry: sn=672804843, cn=41880, tn=40, sn=123 bad144: cyl/trk/sect out of range in existing entry: sn=157916182, cn=9829, tn=208, sn=193 bad144: cyl/trk/sect out of range in existing entry: sn=427637130, cn=26619, tn=43, sn=186 bad144: cyl/trk/sect out of range in existing entry: sn=674534733, cn=41987, tn=212, sn=222 bad144: cyl/trk/sect out of range in existing entry: sn=190613989, cn=11865, tn=41, sn=181 bad144: cyl/trk/sect out of range in existing entry: sn=963917970, cn=60001, tn=30, sn=15 bad144: cyl/trk/sect out of range in existing entry: sn=919108812, cn=57211, tn=221, sn=174 bad144: cyl/trk/sect out of range in existing entry: sn=881383453, cn=54863, tn=148, sn=34 bad144: cyl/trk/sect out of range in existing entry: sn=1052017914, cn=65485, tn=19, sn=192 bad144: cyl/trk/sect out of range in existing entry: sn=817883596, cn=50910, tn=227, sn=145 bad144: cyl/trk/sect out of range in existing entry: sn=934650625, cn=58179, tn=77, sn=139 bad144: cyl/trk/sect out of range in existing entry: sn=286365682, cn=17825, tn=109, sn=190 bad144: cyl/trk/sect out of range in existing entry: sn=593789805, cn=36961, tn=176, sn=252 bad144: cyl/trk/sect out of range in existing entry: sn=268581566, cn=16718, tn=109, sn=29 bad144: cyl/trk/sect out of range in existing entry: sn=880244385, cn=54792, tn=171, sn=132 bad144: cyl/trk/sect out of range in existing entry: sn=672804843, cn=41880, tn=40, sn=123 bad144: cyl/trk/sect out of range in existing entry: sn=157916182, cn=9829, tn=208, sn=193 bad144: cyl/trk/sect out of range in existing entry: sn=54923655, cn=3418, tn=214, sn=3 bad144: cyl/trk/sect out of range in existing entry: sn=413300750, cn=25726, tn=197, sn=149 bad144: cyl/trk/sect out of range in existing entry: sn=83441217, cn=5193, tn=245, sn=237 bad144: cyl/trk/sect out of range in existing entry: sn=577960943, cn=35976, tn=102, sn=77 Exit 1 # fdisk ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=622 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=622 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 9992367 (4879 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 621/ sector 63/ head 254 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: -- Stéphane Marzloff -> smarzloff@carif-idf.org (setq viper-mode t) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 07:13:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22680 for freebsd-stable-outgoing; Mon, 27 Jul 1998 07:13:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from seedlab1.cropsci.ncsu.edu (seedlab1.cropsci.ncsu.edu [152.1.88.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22675 for ; Mon, 27 Jul 1998 07:13:56 -0700 (PDT) (envelope-from bsdbob@seedlab1.cropsci.ncsu.edu) Received: (from bsdbob@localhost) by seedlab1.cropsci.ncsu.edu (8.8.8/8.8.8) id KAA22179; Mon, 27 Jul 1998 10:09:00 -0400 (EDT) (envelope-from bsdbob) From: "Robert D. Keys" Message-Id: <199807271409.KAA22179@seedlab1.cropsci.ncsu.edu> Subject: Re: 3.0 Snap---- In-Reply-To: from William Woods at "Jul 26, 98 12:48:59 pm" To: wwoods@cybcon.com Date: Mon, 27 Jul 1998 10:08:58 -0400 (EDT) Cc: freebsd-stable@FreeBSD.ORG 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 > I dont know if this is the right list, but.............Would you all (those of > you who are running it) consider 3.0 useable and stable to use in a work > enviroment? I know it is beta but I just had to ask.... That is a good question. I have been running the 523-SNAP since it came out on my office boxes, and it seems stable as a rock, for my needs. I don't do any exotic serving or crunching on them, but, do all my office mail/networking/writing/etc on them and they are fine. YMMV, of course, and I tried one of the later ones (6xx-SNAP) and it went sideways, so there are ups and downs to 3.0 SNAPS. The autoprobing was off on the later one I tried. I will port the 725-SNAP home tonight and try that, for comparisons. So far, though, the 523-SNAP has been rock solid for me. Kudos to the 3.0 crew. Bob Keys To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 07:34:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25673 for freebsd-stable-outgoing; Mon, 27 Jul 1998 07:34:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25636 for ; Mon, 27 Jul 1998 07:34:33 -0700 (PDT) (envelope-from benst@nemesis.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9265-14278>; Mon, 27 Jul 1998 16:33:49 +0200 Received: from nemesis.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.8.8/8.8.8) with UUCP id QAA10831 for stable@freebsd.org; Mon, 27 Jul 1998 16:29:17 +0200 (MET DST) (envelope-from benst@nemesis.stuyts.nl) Received: from giskard.stuyts.nl (giskard.stuyts.nl [193.78.231.1]) by nemesis.stuyts.nl (8.8.8/8.8.8) with ESMTP id QAA03995 for ; Mon, 27 Jul 1998 16:26:07 +0200 (MET DST) (envelope-from benst) Received: (from benst@localhost) by giskard.stuyts.nl (8.8.5/8.8.5) id QAA04077 for stable@freebsd.org; Mon, 27 Jul 1998 16:26:07 +0200 (MET DST) Message-Id: <199807271426.QAA04077@giskard.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Mon, 27 Jul 98 16:26:04 +0200 To: stable@FreeBSD.ORG Subject: tar to remote tape drive stopped working Reply-To: ben@stuyts.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I cvsupped/rebuilt -stable on the 23rd of july, and since then I've been having a problem using tar on a remote tape drive. I think a kernel built on the 17th of July still worked. I can reproduce it on the local machine like this. As root, using no host name in the tape file name. everything works fine: # tar tfv /dev/rst0 V--------- 0/0 0 Jul 27 05:20 1998 level 1 backup of / on nemesis at Mon Jul 27 05:20:05 MET DST 1998 Volume 1--Volume Header-- drwxr-xr-x root/wheel 250 Jul 24 11:58 1998 ./ drwxr-xr-x bin/bin 179 Jul 24 11:20 1998 ./bin/ ...etc And now using the local host's name in the tape file name: # tar tfv nemesis:/dev/rst0 tar: can't open nemesis:/dev/rst0 : Input/output error Permissions (.rhosts, etc) seem to be ok. Any idea what could be causing this? Thanks, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 10:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25101 for freebsd-stable-outgoing; Mon, 27 Jul 1998 10:26:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from admin.dircon.net (philip@admin.dircon.net [194.112.33.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25093 for ; Mon, 27 Jul 1998 10:26:53 -0700 (PDT) (envelope-from philip@admin.dircon.net) Received: (from philip@localhost) by admin.dircon.net (8.8.5/8.8.7) id SAA22760; Mon, 27 Jul 1998 18:26:09 +0100 (BST) Date: Mon, 27 Jul 1998 18:26:08 +0100 (BST) From: Philip Inglesant To: freebsd-stable@FreeBSD.ORG Subject: dump/restore and large filesystem problems 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 This problem was reported by tom@uniserve.com in April, but i haven't seen any convincing answer to it, and it is still a problem for us. I have this exact problem with a large (16GB) file system. It is nothing to do with sparse files, back tapes, networks, or anything else like that. I can dump and pipe it into a restore, and the "hole in dump" happens right away. I did some hacking in the source, and it seems that the "maps" dumped at the start of the tape can exceed TP_NINDIR (which is half a basic tape block, or 512) blocks. The significance of this is that the c_addr table, which has a non-zero value for each block in the ext part of the dump, fits in 512 bytes (look in /usr/include/protocols/dumprestore.h), and the whole header fits in a basic 1kb block. For debugging, I got restore to fprintf the value of c_count, which is the size of the next part of the dump, for which the c_addr table has to have a value for each block. On the type TS_CLRI map (that's map of inodes deleted), on this particular 16Gb file system, it showed a value of 1019. Obviously, on other file systems it would be some other value, but there's no reason at all to assume it will always be < 512. I have a hacked version of dump that puts the two initial maps (cleared inodes and the file dump list) onto tape in much the same way as the actual files - a header guaranteed to be < 1 basic tape block, followed by 512 or fewer blocks of dump, followed by another header and so on as necessary, and a hacked version of restore to read dumps done this way. It seems to work but i haven't really tested it well. Maybe someone with more knowledge of BSD dump/restore would like to comment. Philip Inglesant Direct Connection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 16:14:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03776 for freebsd-stable-outgoing; Mon, 27 Jul 1998 16:14:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (root@wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03563; Mon, 27 Jul 1998 16:13:52 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id QAA03778; Mon, 27 Jul 1998 16:12:53 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 27 Jul 1998 16:11:23 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: Support for V.90 PCI modems? Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have not been able to find evidence in the FAQs or sio source for the new V.90 PCI modems. Before buying one, I'd like to know the status on the STABLE branch, and/or stability of code in the CURRENT- branch for its support. TIA, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 17:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18477 for freebsd-stable-outgoing; Mon, 27 Jul 1998 17:18:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18331 for ; Mon, 27 Jul 1998 17:17:35 -0700 (PDT) (envelope-from scott@iprg.nokia.com) Received: from melkor.iprg.nokia.com (melkor.iprg.nokia.com [205.226.1.82]) by mailhost.iprg.nokia.com (8.8.8/8.6.10) with SMTP id RAA13260; Mon, 27 Jul 1998 17:16:31 -0700 (PDT) Message-ID: <35BD185E.4487EB71@iprg.nokia.com> Date: Mon, 27 Jul 1998 17:16:30 -0700 From: Scott Sewall Organization: Nokia Communications X-Mailer: Mozilla 3.04Gold (X11; U; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: FDDI NIC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see that FreeBSD supports the DEC FDDI cards. Does anyone have any experience in using these cards? How good/stable is the support? -- Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 18:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05125 for freebsd-stable-outgoing; Mon, 27 Jul 1998 18:38:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05108; Mon, 27 Jul 1998 18:38:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA02623; Mon, 27 Jul 1998 18:36:30 -0700 (PDT) Message-Id: <199807280136.SAA02623@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jeff Kletsky cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Mon, 27 Jul 1998 16:11:23 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 18:36:30 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have not been able to find evidence in the FAQs or sio source for the new > V.90 PCI modems. Before buying one, I'd like to know the status on the > STABLE branch, and/or stability of code in the CURRENT- branch for its > support. There is no explicit support for these. If they look like a standard UART, you can tweak an sio to match the parameters the BIOS assigns to them. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Jul 27 20:15:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20301 for freebsd-stable-outgoing; Mon, 27 Jul 1998 20:15:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hackerz.org (randy@hackerz.org [209.31.146.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20292; Mon, 27 Jul 1998 20:15:19 -0700 (PDT) (envelope-from randy@hackerz.org) Received: (from randy@localhost) by hackerz.org (8.9.0/8.9.0) id XAA27299; Mon, 27 Jul 1998 23:16:06 -0400 (EDT) Message-ID: <19980727231605.64387@hackerz.org> Date: Mon, 27 Jul 1998 23:16:05 -0400 From: Charles Quarri To: freebsd-stable@FreeBSD.ORG, frebsd-mobile@FreeBSD.ORG Subject: ThinkPad 600 Memory Problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed a 64Meg Sim in my ThinkPad 600 and rebooted the machine, and the box hung right after hard drive was detected with a series of rapid beeps. I took out the SIMM and the machine worked normally. I tried recompiling the kernel with MAXMEM=98304 and trying it again, but to no avail. The ThinkPad 600 uses SDRAM. Thanks in advance for your help. ---------- C. Quarri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 20:31:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22016 for freebsd-stable-outgoing; Mon, 27 Jul 1998 20:31:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jamesn.locker13.com (root@here.what.net [207.136.36.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22010 for ; Mon, 27 Jul 1998 20:31:30 -0700 (PDT) (envelope-from jamesn@here.what.net) Received: from localhost (741 bytes) by jamesn.locker13.com via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Mon, 27 Jul 1998 22:31:00 -0500 (CDT) (Smail-3.2.0.98 1997-Oct-16 #3 built 1997-Oct-30) Message-Id: Date: Mon, 27 Jul 1998 22:31:00 -0500 (CDT) From: James Nuckolls To: scott@iprg.nokia.com, freebsd-stable@FreeBSD.ORG Subject: Re: FDDI NIC In-Reply-To: <35BD185E.4487EB71@iprg.nokia.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In mailinglist.freebsd.stable, you wrote: >I see that FreeBSD supports the DEC FDDI cards. Does anyone >have any experience in using these cards? How good/stable >is the support? It's stable. That's all I can really say about it, because I never seem to have any problems. Other than the usual lEnti PCI bandwidth problems, they are quite speedy. I do, however, like the fact that they actually compain about ring wraps, where as my OSF boxes just don't care (until they run out of bufcache due to ring isolation..). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 27 23:54:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16117 for freebsd-stable-outgoing; Mon, 27 Jul 1998 23:54:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from inet.chipweb.ml.org (qmailr@c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA16104 for ; Mon, 27 Jul 1998 23:54:44 -0700 (PDT) (envelope-from ludwigp@bigfoot.com) Message-Id: <199807280654.XAA16104@hub.freebsd.org> Received: (qmail 18596 invoked from network); 28 Jul 1998 06:53:41 -0000 Received: from speedy.chipweb.ml.org (172.16.1.1) by inet.chipweb.ml.org with SMTP; 28 Jul 1998 06:53:41 -0000 X-Sender: ludwigp2@mail-r X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 27 Jul 1998 23:53:34 -0700 To: Mike Smith , Jeff Kletsky From: Ludwig Pummer Subject: Re: Support for V.90 PCI modems? Cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG In-Reply-To: <199807280136.SAA02623@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:36 PM 7/27/98 -0700, Mike Smith wrote: >> I have not been able to find evidence in the FAQs or sio source for the new >> V.90 PCI modems. Before buying one, I'd like to know the status on the >> STABLE branch, and/or stability of code in the CURRENT- branch for its >> support. > >There is no explicit support for these. If they look like a standard >UART, you can tweak an sio to match the parameters the BIOS assigns to >them. > I don't think they look like a standard UART. They get an auto-assigned IRQ and a memory range. They only work in Win95 AFAIK (no NT support). Under Win95, they load a special driver to emulate a normal COM port (taking up the IO address for that COM port and usually another IRQ). --Ludwig Pummer ludwigp@bigfoot.com ludwigp@chipweb.ml.org ICQ UIN: 692441 http://chipweb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 01:34:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00336 for freebsd-stable-outgoing; Tue, 28 Jul 1998 01:34:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00324 for ; Tue, 28 Jul 1998 01:34:31 -0700 (PDT) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.7.1/8.7.1) id KAA01986; Tue, 28 Jul 1998 10:33:36 +0200 (MESZ) Date: Tue, 28 Jul 1998 10:33:36 +0200 (MESZ) Message-Id: <199807280833.KAA01986@king.ki.informatik.uni-frankfurt.de> From: Marko Schuetz MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@FreeBSD.ORG Subject: Global register variables and stdio.h?!? X-Mailer: VM 6.34 under Emacs 20.2.1 Reply-To: marko@cs.uni-frankfurt.de Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to compile mercury on FreeBSD-stable (before 2.2.6-RELEASE) using gcc 2.7.2.1. Mercury tries to use global register variables, but I get the error: [...] gmake[1]: Entering directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' MERCURY_C_INCL_DIR=. ../scripts/mgnuc --grade asm_fast.gc --no-ansi -I../runtime -I../boehm_gc -g -c label.c -o label.o In file included from regs.h:67, from imp.h:36, from label.c:19: machdeps/i386_regs.h:61: global register variable follows a function definition machdeps/i386_regs.h:62: global register variable follows a function definition machdeps/i386_regs.h:67: global register variable follows a function definition gmake[1]: *** [label.o] Error 1 gmake[1]: Leaving directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' gmake: *** [runtime] Error 2 I checked the preprocessor output and found that there is only one function definition which is included from stdio.h: static __inline int __sputc(int _c, FILE *_p) { if (--_p->_w >= 0 || (_p->_w >= _p->_lbfsize && (char)_c != '\n')) return (*_p->_p++ = _c); else return (__swbuf(_c, _p)); } I know I can disable use of global register veriables, but that only seems to be a quick fix and not the correct solution. What is the correct solution: is a newer version of gcc available that perhaps allows function definitions preceding global register variable declarations or is this not a function definition in more recent FreeBSD versions? What other alternatives are there better than disabling global register variables? Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 05:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29789 for freebsd-stable-outgoing; Tue, 28 Jul 1998 05:15:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29779 for ; Tue, 28 Jul 1998 05:15:10 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA08702 for ; Tue, 28 Jul 1998 05:13:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Date: Tue, 28 Jul 1998 05:13:15 -0700 Message-ID: <8694.901627995.1@time.cdrom.com> From: "Jordan K. Hubbard" Subject: Advance announcement for 2.2.8 and some changes. MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: current@freebsd.org Subject: Advance announcement for 2.2.8 and some changes. Date: Tue, 28 Jul 1998 05:13:15 -0700 Message-ID: <8694.901627995@time.cdrom.com> From: "Jordan K. Hubbard" Just so nobody can claim that I'm going to sneak another -stable release out the door, let me just announce it NOW with plenty of advance notice! :-) The official release date for FreeBSD 2.2.8 is November 15th, 1998. This will be the LAST release along the 2.2 branch, at which point it will be well and truly dead except for a very small amount of security and other types of similar "nasty bug" fixing for the benefit of those who continue to sync themselves to the 2.2-stable branch. Since 3.0 is scheduled for release on October 15th, I figure that by the time people are looking to upgrade again sometime in Q1 of 1999, we'll have enough of the rough edges filed off for people to make a full and reasonable committment to 3.0.x. Again, November 15th is the date and I'm not going to change it, so just mark it now on your calendars and don't claim that I didn't warn you when the time comes around - I expect everyone to remember this date and, if they don't, it's their own darn fault. I may or may not make another announcement closer to that date, so simply take it as read that November 15th is the date in question and if you forget and start gritching come November, I'm merely going to forward this message to you again and say "I scheduled this almost 4 months ago and announced it widely, so it's not *my* fault if you have Alzheimers!" :-) Now that we've got that out of the way, I'd also like to make some changes to the way 2.2.x has been maintained. Rather than do a merge from hell right before the 2.2.8 release, like I did for 2.2.6 and 2.2.7, I'm just going to expect the committers to back-port any work they do in -current which fits the classic definition of something which should go into -stable (obvious bug fix, low impact, no significant new functionality unless it fixes something which is seriously broken [like MSDOSfs], etc.). If you don't take care to merge it, don't be surprised if it doesn't make it into 2.2.8 since I refuse to take that all on my own shoulders again. The quality of this last release of 2.2 will rest squarely with the committers and the various users who can help by spotting things in 3.0 which really should be back-ported and reporting that to committers@freebsd.org. Once more, 2.2.8 is going to be the VERY LAST release on the 2.2-stable branch and if you want to make it a worthy cap for what has been a highly successful line, there's no time like the present for thinking about what you need to merge. The sooner you do the work, the more time the CVSup/CTMers of 2.2-stable will also have for testing it and seeing if there are any unforseen side-effects. I propose to freeze the branch on November 7th, so please don't leave it to the last minute like everyone always does - once this release is out the door, there won't be a second chance for the 2.2 branch! This has been a public service announcement. :) Thanks! - Jordan ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 07:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14719 for freebsd-stable-outgoing; Tue, 28 Jul 1998 07:07:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14700 for ; Tue, 28 Jul 1998 07:07:24 -0700 (PDT) (envelope-from tfuruya@dilemma.tf.or.jp@ppp142007.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142007.asahi-net.or.jp [202.213.142.7]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id XAA16836; Tue, 28 Jul 1998 23:12:29 +0900 Received: from dilemma.tf.or.jp (dilemma.tf.or.jp [192.168.1.3]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id XAA22149; Tue, 28 Jul 1998 23:06:44 +0900 (JST) Received: from dilemma.tf.or.jp (localhost [127.0.0.1]) by dilemma.tf.or.jp (8.8.8/3.6W-CF3.6W-dilemma-tf.or.jp-9807) with ESMTP id XAA03014; Tue, 28 Jul 1998 23:10:37 +0900 (JST) Message-Id: <199807281410.XAA03014@dilemma.tf.or.jp> To: smarzloff@carif-idf.org Cc: freebsd-stable@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Disk problem. From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Mon, 27 Jul 1998 09:54:56 +0200" References: <19980727095456.A26476@rafiki.intranet.carif.asso.fr> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Date: Tue, 28 Jul 1998 23:10:34 +0900 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA14708 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, you have returned. In Message-ID: <19980727095456.A26476@rafiki.intranet.carif.asso.fr> Stephane Marzloff wrote: > Dans un message du 09 Jul à 06:49, Tetsuro FURUYA écrivait : > > > > > > Your ide disk sector is broken. > > Try > > bad144 -s -v /dev/wd0 > > or > > badsect & fsck (This is rather difficult. So, please read man). > > Hello.. > I'm back. > > So I launch the 'bad144 -s -v wd0, it run about 48H for a 4,8Go. We have to pay attention to drive assignment, or we will destroy disk. Block device name is required. We have to read man bad144(8) carefully. So it took 48 Hours, but finally bad144 finished. It seems too long. Something may be abnormal except disk sectors. > > This is the report : > > [18:22] root@rafiki:~ # bad144 -s -v wd0 > cyl: 621, tracks: 255, secs: 63, sec/cyl: 16065, start: 0, end: 9992178 > 9976365 of 9992178 blocks ( 99%) > bad block information at sector 9992304 in /dev/rwd0c: > cartridge serial number: -1108550333(10) > bt_flag=a70a(16)? > bad144: /dev/rwd0c: bad flag in bad-sector table > bad144: /dev/rwd0c: bad magic number ??? > bad144: cyl/trk/sect out of range in existing entry: sn=656226137, cn=40848, tn=44, sn=245 This seems to be a gabage data on the bad sector information which is located in the first 5 even numbered sectors of the last track of the disk pack. If there exists bad sectors, they are processed before these data. > bad144: cyl/trk/sect out of range in existing entry: sn=429083853, cn=26709, tn=58, sn=114 ............ > bad144: cyl/trk/sect out of range in existing entry: sn=577960943, cn=35976, tn=102, sn=77 > Exit 1 If there are bad sectors, bad144 displays those blocks when executing access to those blocks, such as, Block: 1308727 will be marked BAD. Did you have messages like this ? Unfortunately, bad144 leaves no data of bad blocks on /var/log/messages. So, I get this data doing, ============================ #/usr/local/bin/bash (or /bin/sh) #bad144 -s -v 2>1& | tee bad144.log #echo "#include ">cr.cc;echo "using namespace std;\ main(){char cc;while(cin.get(cc)){if(cc==0x0d)cc=0x0a;cout << cc;}}" >>cr.cc; #g++ cr.cc;./a.out < bad144.log | egrep -i BAD ======================================================= And, it says "/dev/rwd0c: bad flag in bad-sector table". It is difficult to know the meaning of this statement. Does "bad flag" mean that bad-sector table is broken ? Or, is "bad sector" registered as a flag in bad-sector table ? If there are bad sectors and the case is the latter, you can know these are fixed or not by achieving some simple tests. For example, ===================================== /usr/local/bin/bash (or /bin/sh) su root sync cat /dev/zero >/usr/ttt 2> catzero1.log sync cat /usr/ttt > /dev/null 2> catzero2.log rm /usr/ttt sync find /usr -name "peanuts" > /dev/null 2> find.log sync egrep -R "peanuts" /usr > /dev/null 2> egrep.log less /var/log/messages ================================================== And if wd driver has hung up, bad144 could not end and display these gabage data. So, there seems to be no need for a patch to wd.c. In this case, fdisk do not show whether there is bad sectors or not, because, there are bad sectors in my disk, but my fdsik shows the same list. > > # fdisk > ******* Working on device /dev/rwd0 ******* > parameters extracted from in-core disklabel are: > cylinders=622 heads=255 sectors/track=63 (16065 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=622 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 9992367 (4879 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 1; > end: cyl 621/ sector 63/ head 254 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > -- > Stéphane Marzloff -> smarzloff@carif-idf.org > (setq viper-mode t) > If you cannot find bad sectors, and the defects continues, that was not for bad sectors. Tetsuro Furuya These are my logs. ===================================== #bad144 -s -v wd0 2>1& | tee bad144.log #/usr/local/bin/bash (or /bin/sh) #bad144 -s -v 2>1& | tee bad144.log #echo "#include ">cr.cc;echo "using namespace std;\ main(){char cc;while(cin.get(cc)){if(cc==0x0d)cc=0x0a;cout << cc;}}" >>cr.cc; #g++ cr.cc;./a.out < bad144.log cyl: 657, tracks: 64, secs: 63, sec/cyl: 4032, start: 0, end: 2652804 0 of 2652804 blocks ( 0%) 4032 of 2652804 blocks ( 0%) 8064 of 2652804 blocks ( 0%) ...... 1278144 of 2652804 blocks ( 48%) Block: 1278972 will be marked BAD. Block: 1279172 will be marked BAD. Block: 1279173 will be marked BAD. ...... Block: 1310765 will be marked BAD. Too many bad sectors, can only handle 126 per slice. #egrep -R "peanuts" /usr/ports > /dev/null 2> egrep.log #cat egrep.log egrep: /usr/ports/archivers/gshar+gunshar/patches/patch-aa: Input/output error egrep: /usr/ports/comms/mgetty+sendfax/work/mgetty-1.0.0/tools/g3.o: Input/output error egrep: /usr/ports/japanese/mew/work/mew-1.54/mew-header.el: Input/output error egrep: /usr/ports/japanese/mew/work/mew-1.54/Makefile.orig: Input/output error ...... #tail -5 /var/log/messages Jul 28 22:45:01 dilemma /kernel: wd0s1f: hard error reading fsbn 1215944 of 1215944-1215951 (wd0s1 bn 1342920; cn 333 tn 4 sn 12)wd0: status 59 error 10 Jul 28 22:45:20 dilemma /kernel: wd0: interrupt timeout: Jul 28 22:45:21 dilemma /kernel: wd0: status 58 error 10 Jul 28 22:47:35 dilemma /kernel: wd0s1f: hard error reading fsbn 1215936 of 1215936-1215939 (wd0s1 bn 1342912; cn 333 tn 4 sn 4)wd0: status 59 error 10 Jul 28 22:48:17 dilemma /kernel: wd0s1f: hard error reading fsbn 1215940 of 1215940-1215943 (wd0s1 bn 1342916; cn 333 tn 4 sn 8)wd0: status 59 error 40 Tetsuro Furuya ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 || E-Mail: 8==------ ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp * || pgp-fingerprint: \|/ pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 08:39:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02184 for freebsd-stable-outgoing; Tue, 28 Jul 1998 08:39:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles227.castles.com [208.214.165.227]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02167; Tue, 28 Jul 1998 08:39:13 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03327; Tue, 28 Jul 1998 08:37:55 -0700 (PDT) Message-Id: <199807281537.IAA03327@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ludwig Pummer cc: Mike Smith , Jeff Kletsky , freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Mon, 27 Jul 1998 23:53:34 PDT." <199807280654.QAA02235@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 08:37:54 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 06:36 PM 7/27/98 -0700, Mike Smith wrote: > >> I have not been able to find evidence in the FAQs or sio source for the new > >> V.90 PCI modems. Before buying one, I'd like to know the status on the > >> STABLE branch, and/or stability of code in the CURRENT- branch for its > >> support. > > > >There is no explicit support for these. If they look like a standard > >UART, you can tweak an sio to match the parameters the BIOS assigns to > >them. > > > I don't think they look like a standard UART. They get an auto-assigned IRQ > and a memory range. They only work in Win95 AFAIK (no NT support). Under > Win95, they load a special driver to emulate a normal COM port (taking up > the IO address for that COM port and usually another IRQ). Yecch. This sounds more and more like a "Winmodem" all the time. Does anyone have any documentation on how they're supposed to work? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Jul 28 08:52:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04979 for freebsd-stable-outgoing; Tue, 28 Jul 1998 08:52:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pandora.lovett.com (root@pandora.lovett.com [38.155.241.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04900; Tue, 28 Jul 1998 08:52:14 -0700 (PDT) (envelope-from ade@lovett.com) Received: from pandora.lovett.com ([38.155.241.3] ident=ade) by pandora.lovett.com with esmtp (Exim 2.01 #1) id 0z1C1V-0003Ad-00; Tue, 28 Jul 1998 10:50:45 -0500 To: Mike Smith cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? Reply-To: ade@lovett.com In-reply-to: Your message of "Tue, 28 Jul 1998 08:37:54 PDT." <199807281537.IAA03327@antipodes.cdrom.com> Date: Tue, 28 Jul 1998 10:50:45 -0500 From: Ade Lovett Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > >> I don't think they look like a standard UART. They get an auto-assigned IRQ >> and a memory range. They only work in Win95 AFAIK (no NT support). Under >> Win95, they load a special driver to emulate a normal COM port (taking up >> the IO address for that COM port and usually another IRQ). > >Yecch. This sounds more and more like a "Winmodem" all the time. > >Does anyone have any documentation on how they're supposed to work? Sounds exactly like the DSVD PCI modem inside the Fujitsu Lifebook -- sadly Fujitsu have not exactly been forthcoming on information about how their Windows drivers work (though in this case there's support for both Win95/98 and NT). Under Windows, it appears as a pseudo-com port (it identifies itself as being on COM3, but probing around in the equivalent IO address reveals nothing obvious) -aDe -- Ade Lovett, Austin, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 11:00:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04512 for freebsd-stable-outgoing; Tue, 28 Jul 1998 11:00:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from caffeine.internal.enteract.com (qmailr@caffeine.internal.enteract.com [207.229.129.24]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA04434 for ; Tue, 28 Jul 1998 11:00:31 -0700 (PDT) (envelope-from kdulzo@caffeine.internal.enteract.com) Received: (qmail 25108 invoked by uid 100); 28 Jul 1998 17:59:57 -0000 Message-ID: <19980728125957.A24837@caffeine.internal.enteract.com> Date: Tue, 28 Jul 1998 12:59:57 -0500 From: "Kevin M. Dulzo" To: freebsd-stable@FreeBSD.ORG Subject: Optimizing breaks /bin/sh in 2.2.7-RELEASE Reply-To: kdulzo@enteract.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA04444 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When compiling (buildworld, or by hand) /bin/sh with -O2 or -O3 it causes some bizarre error when running makedev (the ^E appears as a clover) MAKEDEV: arith: syntax error: "" The /bin/sh from 2.2.6 appears to work fine in this circumstance. The only change I note between them is the following: 36c36 < * $Id: eval.c,v 1.7.2.3 1997/08/25 09:09:42 jkh Exp $ --- > * $Id: eval.c,v 1.7.2.4 1998/05/04 07:25:58 cracauer Exp $ 767c767,770 < evaltree(cmdentry.u.func, 0); --- > if (flags & EV_TESTED) > evaltree(cmdentry.u.func, EV_TESTED); > else > evaltree(cmdentry.u.func, 0); It works properly when compiled -O. Any ideas? Also is it safe to use optimization on the buildworld level. I did have no problems with -O2 on 2.2.6... Thanks, -Kevin -- .-._.-. To see a thing uncolored by one's own personal preferences and desires is to see it in its own pristine simplicity. ._.-._. +==-- | Kevin M. Dulzo Check us out! | | Network Operations http://www.enteract.com | | Enteract, L.L.C. mailto: info@enteract.com| | kdulzo@enteract.com (773)248-8511 | --==+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 11:30:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10350 for freebsd-stable-outgoing; Tue, 28 Jul 1998 11:30:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from socko.cdnow.com (socko.cdnow.com [209.83.166.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10190; Tue, 28 Jul 1998 11:29:58 -0700 (PDT) (envelope-from heller@daria.cdnow.com) Received: from daria.cdnow.com (daria.cdnow.com [209.83.166.60]) by socko.cdnow.com (8.9.0/8.9.0) with ESMTP id OAA02701; Tue, 28 Jul 1998 14:28:26 -0400 (EDT) Received: (from heller@localhost) by daria.cdnow.com (8.8.8/8.8.8) id OAA16891; Tue, 28 Jul 1998 14:25:37 -0400 (EDT) From: "A. Karl Heller" Message-Id: <199807281825.OAA16891@daria.cdnow.com> Subject: Re: Support for V.90 PCI modems? To: ade@lovett.com Date: Tue, 28 Jul 1998 14:25:37 -0400 (EDT) Cc: mike@smith.net.au, freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Reply-To: heller@cdnow.com In-Reply-To: from "Ade Lovett" at Jul 28, 98 10:50:45 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do I dare ask how external V.90 modems work then? > Mike Smith writes: > > > >> I don't think they look like a standard UART. They get an auto-assigned IRQ > >> and a memory range. They only work in Win95 AFAIK (no NT support). Under > >> Win95, they load a special driver to emulate a normal COM port (taking up > >> the IO address for that COM port and usually another IRQ). > > > >Yecch. This sounds more and more like a "Winmodem" all the time. > > > >Does anyone have any documentation on how they're supposed to work? > Sounds exactly like the DSVD PCI modem inside the Fujitsu Lifebook -- > sadly Fujitsu have not exactly been forthcoming on information about > how their Windows drivers work (though in this case there's support > for both Win95/98 and NT). > Under Windows, it appears as a pseudo-com port (it identifies itself > as being on COM3, but probing around in the equivalent IO address > reveals nothing obvious) > -aDe > -- > Ade Lovett, Austin, TX. > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- A. Karl Heller - Senior Systems Engineer - heller@cdnow.com ----------------------------------------------------------------------------- An unbreakable toy is useful for breaking other toys. Do something unusual today. Accomplish work on the computer. >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 12:53:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28937 for freebsd-stable-outgoing; Tue, 28 Jul 1998 12:53:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28797 for ; Tue, 28 Jul 1998 12:52:56 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id VAA23519; Tue, 28 Jul 1998 21:50:55 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA03410; Tue, 28 Jul 1998 21:49:57 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807281949.VAA03410@semyam.dinoco.de> To: heller@cdnow.com cc: freebsd-stable@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Tue, 28 Jul 1998 14:25:37 EDT." <199807281825.OAA16891@daria.cdnow.com> Date: Tue, 28 Jul 1998 21:49:57 +0200 From: Stefan Eggers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do I dare ask how external V.90 modems work then? They are just normal modems. I know as I have one. ;-) Gives me about 2/3 of the German ISDN speed of 64000 bps - it reaches 44000 bps - which makes the WWW real fun and CVSUp more enjoyable and cheaper. The one in question is a PCI card from what I read and for such cards one can make the hardware cheaper by putting part of the processing into a special driver which makes it appear like a normal COM port modem to the system and is just noticeable by reducing the available main CPU power a bit when in use. W/o such a driver (under FreeBSD for example) one can't use it then. As far as I understand the problem with this is that one can't write a driver w/o documentation (I guess no one will doubt this :->) and it seems for such devices the only documentation for the hardware is the binary version of the Windows driver. One would first have to reverse engineer the Windows driver. :-( Of course one might envision a hybrid version where one does this trick over a serial port but I hope no manufac- turer makes such an insane device as then the serial port has to be faster I think and then it might fail with not so good cabling which just works with normal modems for example but can't stand higher speed. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 13:04:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01874 for freebsd-stable-outgoing; Tue, 28 Jul 1998 13:04:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01584; Tue, 28 Jul 1998 13:03:46 -0700 (PDT) (envelope-from dave@mmrd.com) Received: by persprog.com (8.7.5/4.10) id OAA06837; Tue, 28 Jul 1998 14:55:16 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma006833; Tue Jul 28 15:54:50 1998 Message-ID: <35BE2C75.4440B92A@mmrd.com> Date: Tue, 28 Jul 1998 15:54:29 -0400 From: "David W. Alderman" X-Mailer: Mozilla 4.04 [en] (WinNT; U) MIME-Version: 1.0 To: heller@cdnow.com CC: ade@lovett.com, mike@smith.net.au, freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? References: <199807281825.OAA16891@daria.cdnow.com> X-Corel-MessageType: EMail Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A. Karl Heller wrote: > Do I dare ask how external V.90 modems work then? > Like any other standard modem. There are three basic types of internal modem: 1-Modems that take the full AT command set through a serial chip (or hardware simulacrum thereof). 2-Modems that use the CPU to interpret the AT commands but all codec and compression functions are performed in hardware. 3-Modems that use the CPU to interpret AT commands and some of the codec and compression functions. I believe the original RPI modems were of class 3 above and therefore sucked. Most V.90 Winmodems are actually of class 2 and do not suck as badly as the RPI's. Many internal V.90 modems are class1 and therefore FreeBSD friendly. Most are PnP, though. WARNING: I am not a modem expert. The classes above are strictly my own and made up 3 minutes ago based on my observations of the current consumer modem "scene". YMMV. I do have an external V.90 modem that does not require special software drivers to work. Give it the appropriate AT string and it goes! -- Dave Alderman dave@persprog.com is changing to dave@mmrd.com dwa@atlantic.net -or- dwald@earthlink.net -or- dalderman@compuserve.com -or- dwa@hal.cen.ufl.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 15:13:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00322 for freebsd-stable-outgoing; Tue, 28 Jul 1998 15:13:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00188 for ; Tue, 28 Jul 1998 15:12:17 -0700 (PDT) (envelope-from tfuruya@ppp142115.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142115.asahi-net.or.jp [202.213.142.115]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id HAA49504; Wed, 29 Jul 1998 07:17:10 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id HAA25371; Wed, 29 Jul 1998 07:11:23 +0900 (JST) Message-Id: <199807282211.HAA25371@galois.tf.or.jp> To: smarzloff@carif-idf.org Cc: freebsd-stable@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Disk problem. From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Mon, 27 Jul 1998 09:54:56 +0200" References: <19980727095456.A26476@rafiki.intranet.carif.asso.fr> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Date: Wed, 29 Jul 1998 07:11:22 +0900 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA00207 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, because of too long mail header, quoted-printable might not be decoded. So, resend this mail. Oh, you have returned. In Message-ID: <19980727095456.A26476@rafiki.intranet.carif.asso.fr> Stephane Marzloff wrote: > Dans un message du 09 Jul à 06:49, Tetsuro FURUYA écrivait : > > > > > > Your ide disk sector is broken. > > Try > > bad144 -s -v /dev/wd0 > > or > > badsect & fsck (This is rather difficult. So, please read man). > > Hello.. > I'm back. > > So I launch the 'bad144 -s -v wd0, it run about 48H for a 4,8Go. We have to pay attention to drive assignment, or we will destroy disk. Block device name is required. We have to read man bad144(8) carefully. So it took 48 Hours, but finally bad144 finished. It seems too long. Something may be abnormal except disk sectors. > > This is the report : > > [18:22] root@rafiki:~ # bad144 -s -v wd0 > cyl: 621, tracks: 255, secs: 63, sec/cyl: 16065, start: 0, end: 9992178 > 9976365 of 9992178 blocks ( 99%) > bad block information at sector 9992304 in /dev/rwd0c: > cartridge serial number: -1108550333(10) > bt_flag=a70a(16)? > bad144: /dev/rwd0c: bad flag in bad-sector table > bad144: /dev/rwd0c: bad magic number ??? > bad144: cyl/trk/sect out of range in existing entry: sn=656226137, cn=40848, tn=44, sn=245 This seems to be a gabage data on the bad sector information which is located in the first 5 even numbered sectors of the last track of the disk pack. If there exists bad sectors, they are processed before these data. > bad144: cyl/trk/sect out of range in existing entry: sn=429083853, cn=26709, tn=58, sn=114 ............ > bad144: cyl/trk/sect out of range in existing entry: sn=577960943, cn=35976, tn=102, sn=77 > Exit 1 If there are bad sectors, bad144 displays those blocks when executing access to those blocks, such as, Block: 1308727 will be marked BAD. Did you have messages like this ? Unfortunately, bad144 leaves no data of bad blocks on /var/log/messages. So, I get this data doing, ============================ #/usr/local/bin/bash (or /bin/sh) #bad144 -s -v 2>1& | tee bad144.log #echo "#include ">cr.cc;echo "using namespace std;\ main(){char cc;while(cin.get(cc)){if(cc==0x0d)cc=0x0a;cout << cc;}}" >>cr.cc; #g++ cr.cc;./a.out < bad144.log | egrep -i BAD ======================================================= And, it says "/dev/rwd0c: bad flag in bad-sector table". It is difficult to know the meaning of this statement. Does "bad flag" mean that bad-sector table is broken ? Or, is "bad sector" registered as a flag in bad-sector table ? If there are bad sectors and the case is the latter, you can know these are fixed or not by achieving some simple tests. For example, ===================================== /usr/local/bin/bash (or /bin/sh) su root sync cat /dev/zero >/usr/ttt 2> catzero1.log sync cat /usr/ttt > /dev/null 2> catzero2.log rm /usr/ttt sync find /usr -name "peanuts" > /dev/null 2> find.log sync egrep -R "peanuts" /usr > /dev/null 2> egrep.log less /var/log/messages ================================================== And if wd driver has hung up, bad144 could not end and display these gabage data. So, there seems to be no need for a patch to wd.c. In this case, fdisk do not show whether there is bad sectors or not, because, there are bad sectors in my disk, but my fdsik shows the same list. > > # fdisk > ******* Working on device /dev/rwd0 ******* > parameters extracted from in-core disklabel are: > cylinders=622 heads=255 sectors/track=63 (16065 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=622 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 9992367 (4879 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 1; > end: cyl 621/ sector 63/ head 254 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > -- > Stéphane Marzloff -> smarzloff@carif-idf.org > (setq viper-mode t) > If you cannot find bad sectors, and the defects continues, that was not for bad sectors. Tetsuro Furuya These are my logs. ===================================== #bad144 -s -v wd0 2>1& | tee bad144.log #/usr/local/bin/bash (or /bin/sh) #bad144 -s -v 2>1& | tee bad144.log #echo "#include ">cr.cc;echo "using namespace std;\ main(){char cc;while(cin.get(cc)){if(cc==0x0d)cc=0x0a;cout << cc;}}" >>cr.cc; #g++ cr.cc;./a.out < bad144.log cyl: 657, tracks: 64, secs: 63, sec/cyl: 4032, start: 0, end: 2652804 0 of 2652804 blocks ( 0%) 4032 of 2652804 blocks ( 0%) 8064 of 2652804 blocks ( 0%) ...... 1278144 of 2652804 blocks ( 48%) Block: 1278972 will be marked BAD. Block: 1279172 will be marked BAD. Block: 1279173 will be marked BAD. ...... Block: 1310765 will be marked BAD. Too many bad sectors, can only handle 126 per slice. #egrep -R "peanuts" /usr/ports > /dev/null 2> egrep.log #cat egrep.log egrep: /usr/ports/archivers/gshar+gunshar/patches/patch-aa: Input/output error egrep: /usr/ports/comms/mgetty+sendfax/work/mgetty-1.0.0/tools/g3.o: Input/output error egrep: /usr/ports/japanese/mew/work/mew-1.54/mew-header.el: Input/output error egrep: /usr/ports/japanese/mew/work/mew-1.54/Makefile.orig: Input/output error ...... #tail -5 /var/log/messages Jul 28 22:45:01 dilemma /kernel: wd0s1f: hard error reading fsbn 1215944 of 1215944-1215951 (wd0s1 bn 1342920; cn 333 tn 4 sn 12)wd0: status 59 error 10 Jul 28 22:45:20 dilemma /kernel: wd0: interrupt timeout: Jul 28 22:45:21 dilemma /kernel: wd0: status 58 error 10 Jul 28 22:47:35 dilemma /kernel: wd0s1f: hard error reading fsbn 1215936 of 1215936-1215939 (wd0s1 bn 1342912; cn 333 tn 4 sn 4)wd0: status 59 error 10 Jul 28 22:48:17 dilemma /kernel: wd0s1f: hard error reading fsbn 1215940 of 1215940-1215943 (wd0s1 bn 1342916; cn 333 tn 4 sn 8)wd0: status 59 error 40 Tetsuro Furuya ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 || E-Mail: 8==------ ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp * || pgp-fingerprint: \|/ pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 20:05:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21712 for freebsd-stable-outgoing; Tue, 28 Jul 1998 20:05:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from werple.mira.net (werple.mira.net [203.9.190.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA21670 for ; Tue, 28 Jul 1998 20:05:35 -0700 (PDT) (envelope-from gfm@mira.net) Received: (qmail 7324 invoked from network); 29 Jul 1998 03:04:58 -0000 Received: from dp-m-r034.werple.net.au (203.17.46.34) by mira.net with SMTP; 29 Jul 1998 03:04:58 -0000 From: gfm@mira.net (Graham Menhennitt) To: freebsd-stable@FreeBSD.ORG Subject: Re: Optimizing breaks /bin/sh in 2.2.7-RELEASE Date: Wed, 29 Jul 1998 03:06:46 GMT Message-ID: <35be65fe.66621767@mira.net> References: <19980728125957.A24837@caffeine.internal.enteract.com> In-Reply-To: <19980728125957.A24837@caffeine.internal.enteract.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA21701 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998 12:59:57 -0500, "Kevin M. Dulzo" wrote: > if (flags & EV_TESTED) > evaltree(cmdentry.u.func, EV_TESTED); > else > evaltree(cmdentry.u.func, 0); I know that this is not the slightlest bit relevant to you question but this chunk of code is equivalent to the much simpler: evaltree(cmdentry.u.func, flags & EV_TESTED); Graham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 22:33:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13400 for freebsd-stable-outgoing; Tue, 28 Jul 1998 22:33:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13383; Tue, 28 Jul 1998 22:33:26 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA15381; Tue, 28 Jul 1998 23:32:52 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <35BEB404.125BAAA7@softweyr.com> Date: Tue, 28 Jul 1998 23:32:52 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Jeff Kletsky CC: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeff Kletsky wrote: > > I have not been able to find evidence in the FAQs or sio source for the new > V.90 PCI modems. Before buying one, I'd like to know the status on the > STABLE branch, and/or stability of code in the CURRENT- branch for its > support. I happened to have one of these lying around, a Diamond V.90 PCI internal. I stuck it in this machine and rebooted, running pretty much vanilla 2.2.6-RELEASE, and this is what dmesg tells me: pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 [no driver assigned] Somebody mentioned a couple of weeks ago how to modify one of the system sources to wire this up to the sio driver. Can anyone throw some quick instructions at me? I'll give this a try in the morning, I'm off to bed. If I can't get this working fairly easily in the FreeBSD machine, it'll get banished to the void of the wife's Win95 machine, so it's not a total loss. For $40, it's pretty hard to lose much anyhow. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 23:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17929 for freebsd-stable-outgoing; Tue, 28 Jul 1998 23:06:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (root@wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17924 for ; Tue, 28 Jul 1998 23:06:09 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id XAA05724 for ; Tue, 28 Jul 1998 23:04:41 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: In-Reply-To: <35BEB404.125BAAA7@softweyr.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 28 Jul 1998 22:59:32 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: Re: Support for V.90 PCI modems? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I happened to have one of these lying around, a Diamond V.90 PCI internal. >I stuck it in this machine and rebooted, running pretty much vanilla >2.2.6-RELEASE, and this is what dmesg tells me: > >pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > [no driver assigned] With Microsoft/Intel's PC99 http://www.microsoft.com/hwdev/pc99.htm http://developer.intel.com/design/desguide/ calling for the elimination of ISA slots and suggesting only USB/PC Card (*not* serial port) "external" modems within the next year, I don't think we'll be seeing any new ISA modems from the major manufacturers. Perhaps PCI modem drivers could be incorporated into the upcoming 3.0 transition? Thanks! Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 28 23:50:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26351 for freebsd-stable-outgoing; Tue, 28 Jul 1998 23:50:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26254; Tue, 28 Jul 1998 23:50:11 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00819; Tue, 28 Jul 1998 23:47:40 -0700 (PDT) Message-Id: <199807290647.XAA00819@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Wes Peters cc: Jeff Kletsky , freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Tue, 28 Jul 1998 23:32:52 MDT." <35BEB404.125BAAA7@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 23:47:39 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jeff Kletsky wrote: > > > > I have not been able to find evidence in the FAQs or sio source for the new > > V.90 PCI modems. Before buying one, I'd like to know the status on the > > STABLE branch, and/or stability of code in the CURRENT- branch for its > > support. > > I happened to have one of these lying around, a Diamond V.90 PCI internal. > I stuck it in this machine and rebooted, running pretty much vanilla > 2.2.6-RELEASE, and this is what dmesg tells me: > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > [no driver assigned] > > Somebody mentioned a couple of weeks ago how to modify one of the system > sources to wire this up to the sio driver. Can anyone throw some quick > instructions at me? Have a look at the way that if_ed_p.c does it. First, boot with -v and confirm that all it's asking for is an 8-byte I/O mapping; if it has anything else, then it's not going to be a UART clone. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Jul 29 05:27:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13176 for freebsd-stable-outgoing; Wed, 29 Jul 1998 05:27:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA13150; Wed, 29 Jul 1998 05:27:33 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id IAA22687; Wed, 29 Jul 1998 08:26:14 -0400 Date: Wed, 29 Jul 1998 08:26:14 -0400 (EDT) From: Jamie Bowden To: "A. Karl Heller" cc: ade@lovett.com, mike@smith.net.au, freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-Reply-To: <199807281825.OAA16891@daria.cdnow.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 Sure, they plug into a serial port. On Tue, 28 Jul 1998, A. Karl Heller wrote: > > > Do I dare ask how external V.90 modems work then? > > > Mike Smith writes: > > > > > >> I don't think they look like a standard UART. They get an auto-assigned IRQ > > >> and a memory range. They only work in Win95 AFAIK (no NT support). Under > > >> Win95, they load a special driver to emulate a normal COM port (taking up > > >> the IO address for that COM port and usually another IRQ). > > > > > >Yecch. This sounds more and more like a "Winmodem" all the time. > > > > > >Does anyone have any documentation on how they're supposed to work? > > > Sounds exactly like the DSVD PCI modem inside the Fujitsu Lifebook -- > > sadly Fujitsu have not exactly been forthcoming on information about > > how their Windows drivers work (though in this case there's support > > for both Win95/98 and NT). > > > Under Windows, it appears as a pseudo-com port (it identifies itself > > as being on COM3, but probing around in the equivalent IO address > > reveals nothing obvious) > > > -aDe > > > -- > > Ade Lovett, Austin, TX. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > A. Karl Heller - Senior Systems Engineer - heller@cdnow.com > ----------------------------------------------------------------------------- > An unbreakable toy is useful for breaking other toys. > Do something unusual today. Accomplish work on the computer. > >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 07:42:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07279 for freebsd-stable-outgoing; Wed, 29 Jul 1998 07:42:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07263 for ; Wed, 29 Jul 1998 07:42:07 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA11444; Wed, 29 Jul 1998 16:41:02 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Wed, 29 Jul 1998 16:41:01 +0200 (MET DST) Mime-Version: 1.0 To: kdulzo@enteract.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Optimizing breaks /bin/sh in 2.2.7-RELEASE References: <19980728125957.A24837@caffeine.internal.enteract.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 29 Jul 1998 16:41:01 +0200 In-Reply-To: "Kevin M. Dulzo"'s message of "Tue, 28 Jul 1998 12:59:57 -0500" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA07273 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kevin M. Dulzo" writes: > It works properly when compiled -O. Any ideas? Also is it > safe to use optimization on the buildworld level. I did have no > problems with -O2 on 2.2.6... Yes, it's safe. Isn't -O2 the default? But it doesn't really give you much better performance than -O, and it's noticeably slower. I recommend setting CFLAGS to "-O -pipe". DES -- Dag-Erling Smørgrav - dag-erli@ifi.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 Jul 29 08:59:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20092 for freebsd-stable-outgoing; Wed, 29 Jul 1998 08:59:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20070 for ; Wed, 29 Jul 1998 08:59:43 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id LAA08949 for ; Wed, 29 Jul 1998 11:59:11 -0400 (EDT) Date: Wed, 29 Jul 1998 11:59:11 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: stable@FreeBSD.ORG Subject: make buildworld/installworld 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 Could someone confirm whether this is pilot error or not? These sources are from July 26. I was short on space, so I skipped over some things by giving a bunch of flags such as -DNOINFO -DNOSHARE -DNOPROFILE, etc... The build went fine, but install is complaining about: -------------------------------------------------------------- Rebuilding man page indexes -------------------------------------------------------------- cd /usr/src/share/man && /usr/obj/usr/src/tmp/usr/bin/make makedb cd: can't cd to /usr/src/share/man *** Error code 2 Stop. *** Error code 1 Stop. Now I didn't want to install anything from /usr/src/share, so it doesn't exist. Is it absolutely necessary? In this case I'm only upgrading from a snapshot of about 3 weeks ago... And I am calling installworld with the exact same flags. Even tried adding -DNOMAN with the same results. Do I absolutely need /usr/src/share? Thanks, Charles Charles Sprickman spork@super-g.com ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 12:41:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12351 for freebsd-stable-outgoing; Wed, 29 Jul 1998 12:41:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.ukconnect.net (mail.ukconnect.net [195.219.13.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA12345 for ; Wed, 29 Jul 1998 12:41:05 -0700 (PDT) (envelope-from phil@virtek.com) Received: from gsi.ukconnect.net (gsi.ukconnect.net [195.219.13.179]) by mail.virtek.com (NTMail 3.03.0017/1.aa3h) with ESMTP id sa011406 for ; Wed, 29 Jul 1998 19:38:51 +0100 Message-Id: <3.0.3.32.19980729203940.00d39f10@mail.virtek.com> X-Sender: phil@mail.virtek.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 29 Jul 1998 20:39:40 +0100 To: freebsd-stable@FreeBSD.ORG From: Phil Allsopp Subject: twin network cards in one PC Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I put two network cards in one Pc and both cards are on the same subnet ie. 194.159.112.3 and 194.159.112.4 I can not ping one of the cards wheras if I have one of the cards set to 192.168.1.1 I can ping them both. Why is this ? Phil. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 13:20:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18842 for freebsd-stable-outgoing; Wed, 29 Jul 1998 13:20:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from galois.tf.or.jp (ppp142044.asahi-net.or.jp [202.213.142.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18821 for ; Wed, 29 Jul 1998 13:20:35 -0700 (PDT) (envelope-from tfuruya@dilemma.tf.or.jp@ppp142044.asahi-net.or.jp) Received: from dilemma.tf.or.jp (dilemma.tf.or.jp [192.168.1.3]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98073004) with ESMTP id FAA07646; Thu, 30 Jul 1998 05:19:40 +0900 (JST) Received: from dilemma.tf.or.jp (localhost [127.0.0.1]) by dilemma.tf.or.jp (8.8.8/3.6W-CF3.6W-dilemma-tf.or.jp-9807) with ESMTP id FAA04739; Thu, 30 Jul 1998 05:24:16 +0900 (JST) Message-Id: <199807292024.FAA04739@dilemma.tf.or.jp> To: smarzloff@carif-idf.org Cc: freebsd-stable@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Disk problem. From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Mon, 27 Jul 1998 09:54:56 +0200" References: <19980727095456.A26476@rafiki.intranet.carif.asso.fr> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 30 Jul 1998 05:24:10 +0900 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA18827 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Mr. Marzloff. >From your result, In Message-ID: <19980727095456.A26476@rafiki.intranet.carif.asso.fr> Stephane Marzloff wrote: > So I launch the 'bad144 -s -v wd0, it run about 48H for a 4,8Go. > > This is the report : > > [18:22] root@rafiki:~ # bad144 -s -v wd0 > cyl: 621, tracks: 255, secs: 63, sec/cyl: 16065, start: 0, end: 9992178 > 9976365 of 9992178 blocks ( 99%) > bad block information at sector 9992304 in /dev/rwd0c: > cartridge serial number: -1108550333(10) > bt_flag=a70a(16)? > bad144: /dev/rwd0c: bad flag in bad-sector table > bad144: /dev/rwd0c: bad magic number > bad144: cyl/trk/sect out of range in existing entry: sn=656226137, cn=40848, tn=44, sn=245 I would like to think this last part in detail. So, would you mind sending me the source code of bad144 you are using ? If you send the source codes, of course they are in /usr/src/usr.sbin/bad144/, and will you please compress them by gzip or compress, and encode them by uuencode or base64. Tetsuro, Furuya. ht5t-fry@asahi-net.or.jp ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 || E-Mail: 8==------ ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp * || pgp-fingerprint: \|/ pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 15:57:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21424 for freebsd-stable-outgoing; Wed, 29 Jul 1998 15:57:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (root@wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21307 for ; Wed, 29 Jul 1998 15:57:18 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id PAA07287; Wed, 29 Jul 1998 15:56:24 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: In-Reply-To: <3.0.3.32.19980729203940.00d39f10@mail.virtek.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 29 Jul 1998 15:53:56 -0700 To: Phil Allsopp From: Jeff Kletsky Subject: Re: twin network cards in one PC Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >When I put two network cards in one Pc and both cards are on the same >subnet ie. 194.159.112.3 and >194.159.112.4 > >I can not ping one of the cards wheras if I have one of the cards set to >192.168.1.1 > >I can ping them both. > >Why is this ? Try looking at your firewall configuration (pointed to in /etc/rc.conf) to make sure that the addresses both permit the proper flow of packets. Stock FreeBSD configurations only expect one IP address. If that doesn't help, you might look at the package 'icmpinfo' which will let you "see" the ping packets as they come and go. You can also set logging with 'ipfw' -- lines like ipfw add 1 count log any from any to any via (your interface device #1) ipfw add 1 count log any from any to any via (your interface device #2) should provide lots of debugging help. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 17:39:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14698 for freebsd-stable-outgoing; Wed, 29 Jul 1998 17:39:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA14683 for ; Wed, 29 Jul 1998 17:38:54 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z1gjS-0002nm-00; Wed, 29 Jul 1998 17:38:10 -0700 Date: Wed, 29 Jul 1998 17:38:07 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Jeff Kletsky cc: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: twin network cards in one PC 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 > >When I put two network cards in one Pc and both cards are on the same > >subnet ie. 194.159.112.3 and > >194.159.112.4 > > > >I can not ping one of the cards wheras if I have one of the cards set to > >192.168.1.1 > > > >I can ping them both. > > > >Why is this ? > > Try looking at your firewall configuration (pointed to in /etc/rc.conf) to > make sure that the addresses both permit the proper flow of packets. Stock > FreeBSD configurations only expect one IP address. No, it much simpler. You can't have two interfaces within the same network. Why? Think about routing. If you have 10.0.0.1/24 on one interface, and 10.0.0.2/24 on another interface, to which interface does traffic destined for 10.0.0.0/10 go out from? Once you configure the first interface, you will get an implied route for network 10.0.0.0/0 out via the first interface. When configuring the second interface, the implied route is either overwritten or ignored (I don't remember, which but I think it is ignored with an error). Basically, the route table can only have one route for a particular network. Someone is working on load balancing code. This code will allow multiple routes to a particular network, and will balance traffic among them. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 18:40:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14698 for freebsd-stable-outgoing; Wed, 29 Jul 1998 17:39:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA14683 for ; Wed, 29 Jul 1998 17:38:54 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z1gjS-0002nm-00; Wed, 29 Jul 1998 17:38:10 -0700 Date: Wed, 29 Jul 1998 17:38:07 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Jeff Kletsky cc: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: twin network cards in one PC 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 > >When I put two network cards in one Pc and both cards are on the same > >subnet ie. 194.159.112.3 and > >194.159.112.4 > > > >I can not ping one of the cards wheras if I have one of the cards set to > >192.168.1.1 > > > >I can ping them both. > > > >Why is this ? > > Try looking at your firewall configuration (pointed to in /etc/rc.conf) to > make sure that the addresses both permit the proper flow of packets. Stock > FreeBSD configurations only expect one IP address. No, it much simpler. You can't have two interfaces within the same network. Why? Think about routing. If you have 10.0.0.1/24 on one interface, and 10.0.0.2/24 on another interface, to which interface does traffic destined for 10.0.0.0/10 go out from? Once you configure the first interface, you will get an implied route for network 10.0.0.0/0 out via the first interface. When configuring the second interface, the implied route is either overwritten or ignored (I don't remember, which but I think it is ignored with an error). Basically, the route table can only have one route for a particular network. Someone is working on load balancing code. This code will allow multiple routes to a particular network, and will balance traffic among them. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 18:50:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06070 for freebsd-stable-outgoing; Wed, 29 Jul 1998 18:50:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeker.itsolutions.com.au ([203.39.0.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06027 for ; Wed, 29 Jul 1998 18:50:29 -0700 (PDT) (envelope-from ahodges@itsolutions.com.au) Received: from scooter (scooter.itsolutions.com.au [192.168.1.25]) by gatekeeker.itsolutions.com.au (8.8.8/8.8.8) with SMTP id LAA25154 for ; Thu, 30 Jul 1998 11:15:32 +0930 (CST) (envelope-from ahodges@itsolutions.com.au) Message-ID: <001e01bdbb5c$1fc484c0$1901a8c0@scooter.itsolutions.com.au> From: "Andrew Hodges" To: Subject: Fw: twin network cards in one PC Date: Thu, 30 Jul 1998 11:18:16 +0930 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had similar issues in the past with this and have no problems with two ethernet cards now and can route between interfaces etc. However, I have complicated the matter further by doing dialin using PPP. Therefore I have an additional network to consider. Currently I have a remote 10.0.0.0/24 LAN connected via PPP 192.168.1.100 --> 192.168.1.101. The machine that has 192.168.1.101 has two ethernets 192.168.1.1 and 203.x.x.x. The bit that puzzles me is that I have proxyarp on the PPP link. Does this mean that the PPP interface appears as though it is on the local LAN in the same subnet? If so then routing should all work, right?. Have I configured this correctly, or am I missing something? regards Andrew -----Original Message----- From: Tom To: Jeff Kletsky Cc: Phil Allsopp ; freebsd-stable@FreeBSD.ORG Date: Thursday, 30 July 1998 9:55 Subject: Re: twin network cards in one PC > >> >When I put two network cards in one Pc and both cards are on the same >> >subnet ie. 194.159.112.3 and >> >194.159.112.4 >> > >> >I can not ping one of the cards wheras if I have one of the cards set to >> >192.168.1.1 >> > >> >I can ping them both. >> > >> >Why is this ? >> >> Try looking at your firewall configuration (pointed to in /etc/rc.conf) to >> make sure that the addresses both permit the proper flow of packets. Stock >> FreeBSD configurations only expect one IP address. > > No, it much simpler. You can't have two interfaces within the same >network. Why? Think about routing. If you have 10.0.0.1/24 on one >interface, and 10.0.0.2/24 on another interface, to which interface does >traffic destined for 10.0.0.0/10 go out from? Once you configure the >first interface, you will get an implied route for network 10.0.0.0/0 out >via the first interface. When configuring the second interface, the >implied route is either overwritten or ignored (I don't remember, which >but I think it is ignored with an error). Basically, the route table can >only have one route for a particular network. > > Someone is working on load balancing code. This code will allow >multiple routes to a particular network, and will balance traffic among >them. > >Tom > > >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 Jul 29 21:50:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27904 for freebsd-stable-outgoing; Wed, 29 Jul 1998 21:50:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27870; Wed, 29 Jul 1998 21:50:25 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA17443; Wed, 29 Jul 1998 22:49:29 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <35BFFB59.5E63DC4A@softweyr.com> Date: Wed, 29 Jul 1998 22:49:29 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? References: <199807290647.XAA00819@antipodes.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: > > > I happened to have one of these lying around, a Diamond V.90 PCI internal. > > I stuck it in this machine and rebooted, running pretty much vanilla > > 2.2.6-RELEASE, and this is what dmesg tells me: > > > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > > [no driver assigned] > > > Have a look at the way that if_ed_p.c does it. First, boot with -v and > confirm that all it's asking for is an 8-byte I/O mapping; if it has > anything else, then it's not going to be a UART clone. It reported: pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 [no driver assigned] map(10): mem32(e4000000) I assume this means it wants 10 bytes of I/O, and may not be emulating a simple UART? I'll go plunge around the Diamond Multimedia pages and see if I can find any information. (Yeah, right). -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 29 23:15:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09494 for freebsd-stable-outgoing; Wed, 29 Jul 1998 23:15:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09439 for ; Wed, 29 Jul 1998 23:14:49 -0700 (PDT) (envelope-from mvergall@mail.double-barrel.be) Received: (from uucp@localhost) by mail.double-barrel.be (8.9.1/8.8.8) id IAA28334; Thu, 30 Jul 1998 08:12:47 +0200 (CEST) (envelope-from mvergall@mail.double-barrel.be) Received: from ns.double-barrel.be(194.7.102.18) via SMTP by mail.double-barrel.be, id smtpdW28332; Thu Jul 30 08:12:40 1998 Date: Thu, 30 Jul 1998 08:12:37 +0200 (CEST) From: "Michael C. Vergallen" X-Sender: mvergall@ns.double-barrel.be To: Phil Allsopp cc: freebsd-stable@FreeBSD.ORG Subject: Re: twin network cards in one PC In-Reply-To: <3.0.3.32.19980729203940.00d39f10@mail.virtek.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, what you seem to have done is difine a exteral segment and a fakenet segment this works because your machine acts as a gateway between two segments. when you define 2 cards as subsequent IP's on the same subnet you create a multipe IP route this becomes problematic. but it should work if you define the primary IP as the fakenet and then in rc.local add a ip alias for the fakenet ip to be the .4 real ip. Michael. --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Wed, 29 Jul 1998, Phil Allsopp wrote: > When I put two network cards in one Pc and both cards are on the same > subnet ie. 194.159.112.3 and > 194.159.112.4 > > I can not ping one of the cards wheras if I have one of the cards set to > 192.168.1.1 > > I can ping them both. > > Why is this ? > > Phil. > > 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 Jul 29 23:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10955 for freebsd-stable-outgoing; Wed, 29 Jul 1998 23:22:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10937; Wed, 29 Jul 1998 23:22:25 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00420; Wed, 29 Jul 1998 23:21:30 -0700 (PDT) Message-Id: <199807300621.XAA00420@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Wes Peters cc: Mike Smith , freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Wed, 29 Jul 1998 22:49:29 MDT." <35BFFB59.5E63DC4A@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 23:21:29 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > > I happened to have one of these lying around, a Diamond V.90 PCI internal. > > > I stuck it in this machine and rebooted, running pretty much vanilla > > > 2.2.6-RELEASE, and this is what dmesg tells me: > > > > > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > > > [no driver assigned] > > > > > Have a look at the way that if_ed_p.c does it. First, boot with -v and > > confirm that all it's asking for is an 8-byte I/O mapping; if it has > > anything else, then it's not going to be a UART clone. > > It reported: > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > [no driver assigned] > map(10): mem32(e4000000) > > I assume this means it wants 10 bytes of I/O, and may not be emulating a > simple UART? 10 is the configuration register address. It's asking for a 32-bit accessible memory region - I'd have to go look up the encoding of the field to tell you how big it is. It also wants an interrupt. It's certainly not emulating a UART. > I'll go plunge around the Diamond Multimedia pages and see if I can find > any information. (Yeah, right). More useful than that would be to tell us what the part(s) on the card are. Diamond just use off-the-shelf parts in most of their designs; they're too small to do anything really custom. Then go hunting for the datasheets for the parts in question; that's where you'll find what you're after. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Jul 30 01:50:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03197 for freebsd-stable-outgoing; Thu, 30 Jul 1998 01:50:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03190 for ; Thu, 30 Jul 1998 01:50:28 -0700 (PDT) (envelope-from henry@visint.co.uk) Received: from dopey.visint.co.uk (dopey.visint.co.uk [194.207.134.243]) by mail.visint.co.uk (8.8.8/8.8.5) with SMTP id JAA04338; Thu, 30 Jul 1998 09:50:22 +0100 (BST) Date: Thu, 30 Jul 1998 09:50:22 +0100 (BST) From: Henry Whincup To: Phil Allsopp cc: freebsd-stable@FreeBSD.ORG Subject: Re: twin network cards in one PC In-Reply-To: <3.0.3.32.19980729203940.00d39f10@mail.virtek.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 If you put the second interface up with a netmask of 0xffffffff (all ones) you will be able to use it fine assumming that both cards go onto the same physical and logical network... then again if this is the case why not just use an alias on one card? Henry On Wed, 29 Jul 1998, Phil Allsopp wrote: > When I put two network cards in one Pc and both cards are on the same > subnet ie. 194.159.112.3 and > 194.159.112.4 > > I can not ping one of the cards wheras if I have one of the cards set to > 192.168.1.1 > > I can ping them both. > > Why is this ? > > Phil. > > 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 Jul 30 03:36:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15681 for freebsd-stable-outgoing; Thu, 30 Jul 1998 03:36:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from internationalschool.co.uk (intschool.easynet.co.uk [194.72.37.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15670 for ; Thu, 30 Jul 1998 03:36:41 -0700 (PDT) (envelope-from stuart@internationalschool.co.uk) Received: from internationalschool.co.uk (bamboo.tis [10.0.0.70]) by internationalschool.co.uk (8.8.8/8.8.8) with ESMTP id LAA02990; Thu, 30 Jul 1998 11:32:56 +0100 (BST) Message-ID: <35C04C10.194139F2@internationalschool.co.uk> Date: Thu, 30 Jul 1998 11:33:52 +0100 From: Stuart Henderson Organization: The International School X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Tom CC: Jeff Kletsky , Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: twin network cards in one PC References: Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > > Someone is working on load balancing code. This code will allow > multiple routes to a particular network, and will balance traffic among > them. announced in comp.unix.bsd.freebsd.announce a month or two ago, try a dejanews search there (probably posted by Chrisy Luke). the traceroute output with it in place looks extremely cool :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 30 06:05:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03415 for freebsd-stable-outgoing; Thu, 30 Jul 1998 06:05:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03410 for ; Thu, 30 Jul 1998 06:05:48 -0700 (PDT) (envelope-from benst@nemesis.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9293-17135>; Thu, 30 Jul 1998 15:03:17 +0200 Received: from nemesis.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.8.8/8.8.8) with UUCP id OAA17692 for stable@freebsd.org; Thu, 30 Jul 1998 14:59:13 +0200 (MET DST) (envelope-from benst@nemesis.stuyts.nl) Received: from giskard.stuyts.nl (giskard.stuyts.nl [193.78.231.1]) by nemesis.stuyts.nl (8.8.8/8.8.8) with ESMTP id OAA20069 for ; Thu, 30 Jul 1998 14:56:18 +0200 (MET DST) (envelope-from benst) Received: (from benst@localhost) by giskard.stuyts.nl (8.8.5/8.8.5) id OAA06297 for stable@freebsd.org; Thu, 30 Jul 1998 14:56:17 +0200 (MET DST) Message-Id: <199807301256.OAA06297@giskard.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Thu, 30 Jul 98 14:56:16 +0200 To: stable@FreeBSD.ORG Subject: Again: tar to remote tape drive stopped working Reply-To: ben@stuyts.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, A couple of days ago I posted the below message, but I haven't had any response to it. I would really appreciate some advice. Thanks, Ben Begin forwarded message: From: Ben Stuyts Date: Mon, 27 Jul 98 16:26:04 +0200 To: stable@freebsd.org Subject: tar to remote tape drive stopped working Hi, I cvsupped/rebuilt -stable on the 23rd of july, and since then I've been having a problem using tar on a remote tape drive. I think a kernel built on the 17th of July still worked. I can reproduce it on the local machine like this. As root, using no host name in the tape file name. everything works fine: # tar tfv /dev/rst0 V--------- 0/0 0 Jul 27 05:20 1998 level 1 backup of / on nemesis at Mon Jul 27 05:20:05 MET DST 1998 Volume 1--Volume Header-- drwxr-xr-x root/wheel 250 Jul 24 11:58 1998 ./ drwxr-xr-x bin/bin 179 Jul 24 11:20 1998 ./bin/ ...etc And now using the local host's name in the tape file name: # tar tfv nemesis:/dev/rst0 tar: can't open nemesis:/dev/rst0 : Input/output error Permissions (.rhosts, etc) seem to be ok. Any idea what could be causing this? Thanks, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 30 07:01:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06443 for freebsd-stable-outgoing; Thu, 30 Jul 1998 07:01:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06437 for ; Thu, 30 Jul 1998 07:01:49 -0700 (PDT) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.7.1/8.7.1) id QAA05194 for freebsd-stable@freebsd.org; Thu, 30 Jul 1998 16:01:39 +0200 (MESZ) Message-Id: <199807280833.KAA01986@king.ki.informatik.uni-frankfurt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: VM 6.34 under Emacs 20.2.1 Reply-To: marko@cs.uni-frankfurt.de From: Marko Schuetz To: freebsd-stable@FreeBSD.ORG Subject: Global register variables and stdio.h?!? Date: Tue, 28 Jul 1998 10:33:36 +0200 (MESZ) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I am resending this: it seems not to have made it to the list.] I am trying to compile mercury on FreeBSD-stable (before 2.2.6-RELEASE) using gcc 2.7.2.1. Mercury tries to use global register variables, but I get the error: [...] gmake[1]: Entering directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' MERCURY_C_INCL_DIR=. ../scripts/mgnuc --grade asm_fast.gc --no-ansi -I../runtime -I../boehm_gc -g -c label.c -o label.o In file included from regs.h:67, from imp.h:36, from label.c:19: machdeps/i386_regs.h:61: global register variable follows a function definition machdeps/i386_regs.h:62: global register variable follows a function definition machdeps/i386_regs.h:67: global register variable follows a function definition gmake[1]: *** [label.o] Error 1 gmake[1]: Leaving directory `/usr/home/marko/src/mercury-0.7.3.orig/runtime' gmake: *** [runtime] Error 2 I checked the preprocessor output and found that there is only one function definition which is included from stdio.h: static __inline int __sputc(int _c, FILE *_p) { if (--_p->_w >= 0 || (_p->_w >= _p->_lbfsize && (char)_c != '\n')) return (*_p->_p++ = _c); else return (__swbuf(_c, _p)); } I know I can disable use of global register veriables, but that only seems to be a quick fix and not the correct solution. What is the correct solution: is a newer version of gcc available that perhaps allows function definitions preceding global register variable declarations or is this not a function definition in more recent FreeBSD versions? What other alternatives are there better than disabling global register variables? Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 30 10:03:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21877 for freebsd-stable-outgoing; Thu, 30 Jul 1998 10:03:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.missouri.edu (mail.missouri.edu [128.206.2.169]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21868 for ; Thu, 30 Jul 1998 10:03:44 -0700 (PDT) (envelope-from rich@chumbly.math.missouri.edu) Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12]) by mail.missouri.edu (8.9.0/8.9.0) with SMTP id LAA94418 for <@mail.missouri.edu:freebsd-stable@freebsd.org>; Thu, 30 Jul 1998 11:15:21 -0500 Received: by chumbly.math.missouri.edu (950413.SGI.8.6.12/940406.SGI.AUTO) for freebsd-stable@FreeBSD.ORG id LAA13148; Thu, 30 Jul 1998 11:15:20 -0500 From: rich@chumbly.math.missouri.edu (Rich Winkel) Message-Id: <199807301615.LAA13148@chumbly.math.missouri.edu> Subject: 486 keeps crashing during install To: freebsd-stable@FreeBSD.ORG Date: Thu, 30 Jul 1998 11:15:20 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] 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 Trying to install 2.2.6-release from cd to a 66mhz 486 with ide drives. The only message I've managed to catch on the screen is "double panic". Usually it just reboots and any messages are lost. It runs windows 95 with no problem. Do I have a hardware problem? Are there any good diagnostic programs on the net? Thanks for any help!! Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 30 12:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01337 for freebsd-stable-outgoing; Thu, 30 Jul 1998 12:23:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from helios.whro.org (helios.whro.org [198.78.178.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01291 for ; Thu, 30 Jul 1998 12:23:32 -0700 (PDT) (envelope-from bboone@whro.org) Received: from wizard.whro.org (stargate.whro.net [198.78.178.11]) by helios.whro.org (8.8.5/8.8.5) with SMTP id PAA01177 for ; Thu, 30 Jul 1998 15:16:30 -0400 (EDT) Message-ID: <002e01bdbbf0$8e63eb20$ef63a8c0@wizard.whro.org> From: "Bob Boone" To: Subject: Security Issue -- Date: Thu, 30 Jul 1998 15:30:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if this is the "right" place for this, but this is the list I'm on. . . . I'm a marginal Unix-person, who used FreeBSD because Apache ran on it, and it has been dependable for nearly 2-years. . . So dependable that I have not had to get deep into Unix to keep it crusin' . . . . . now I've got trouble. . . . . Running a webserver on 2.2.5 / Apache, loaded update 10/21/97, running continuously since that date. Security file this morning noted: checking setuid files and devices: www setuid diffs: 2d1 < -r-xr-sr-x 1 bin kmem 167936 Oct 21 10:15:06 1997 /bin/ps 48d46 < -r-xr-sr-x 2 bin kmem 16384 Oct 21 10:19:37 1997 /usr/bin/uptime 54d51 < -r-xr-sr-x 2 bin kmem 16384 Oct 21 10:19:37 1997 /usr/bin/w checking for uids of 0: root 0 toor 0 The "uids" have never been anything but "0" . . . . but the other lines seemed to indicate a HACK. A quick directory check showed a number of files changed between 3-6 am, some with "kmem" some with other owners. and a specific file in /bin: "libtcl76.a" -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 hostname -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 kill -rw-r--r-- 1 root bin 308582 Jul 30 05:41 libtcl76.a -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 ln -r-xr-xr-x 1 bin bin 155648 Oct 21 1997 ls -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 mkdir All password files had been updated during this time, and a user account was changed. Before I could get downstairs to the server, the "libtcl76.a" file dissappeared. My "messages" log was deleted, and there were no httpd-access or -error entries for that period of time . . . Like an "alien" abduction, all overt evidence was erased, but I expect this is a more common "earthly" problem than that. . . . There was one last entry on the terminal screen, that a mail error had occurred from "noc.ipspeed.net" -- they show up in internic as a new ISP in california (I'm on the east coast), so they should not have been the last bounce for mail to me, and I'm not sure what connection, if any, they are to my other problem . . . QUESTIONS: (1) Is this a known hack ??? (2) What else should I assume is corrupt, beyond password and user files. And how do I "delete" a user . . . sysinstall lets me ADD, but not DELETE, and when it adds it puts stuff in several different files, so I assume I'll need to go to each of these areas to delete the specific user-info . . . . ?? (3) What do I do to keep it from happening again ??? ============================================================ Bob Boone Chief Engineer,TV & Radio (Studios) WHRO-TV/FM Norfolk, Va. bboone@whro.org PH: 757.889.9466 FX: 757.489.4444 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 30 12:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07241 for freebsd-stable-outgoing; Thu, 30 Jul 1998 12:43:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07234 for ; Thu, 30 Jul 1998 12:43:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00458; Thu, 30 Jul 1998 12:42:42 -0700 (PDT) Message-Id: <199807301942.MAA00458@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bob Boone" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Security Issue -- In-reply-to: Your message of "Thu, 30 Jul 1998 15:30:42 EDT." <002e01bdbbf0$8e63eb20$ef63a8c0@wizard.whro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Jul 1998 12:42:42 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not sure if this is the "right" place for this, but this is the list I'm on. > .. . . I'm a marginal Unix-person, who used FreeBSD because Apache ran on > it, and it has been dependable for nearly 2-years. . . So dependable that I > have not had to get deep into Unix to keep it crusin' . . . . . now I've got > trouble. . . . . > > Running a webserver on 2.2.5 / Apache, loaded update 10/21/97, running > continuously since that date. > > Security file this morning noted: > > checking setuid files and devices: > www setuid diffs: > 2d1 > < -r-xr-sr-x 1 bin kmem 167936 Oct 21 10:15:06 1997 /bin/ps > 48d46 > < -r-xr-sr-x 2 bin kmem 16384 Oct 21 10:19:37 1997 /usr/bin/uptime > 54d51 > < -r-xr-sr-x 2 bin kmem 16384 Oct 21 10:19:37 1997 /usr/bin/w > checking for uids of 0: > root 0 > toor 0 > > The "uids" have never been anything but "0" . . . . but the other lines > seemed to indicate a HACK. A quick directory check showed a number of files > changed between 3-6 am, some with "kmem" some with other owners. and a > specific file in /bin: "libtcl76.a" > > -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 hostname > -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 kill > -rw-r--r-- 1 root bin 308582 Jul 30 05:41 libtcl76.a > -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 ln > -r-xr-xr-x 1 bin bin 155648 Oct 21 1997 ls > -r-xr-xr-x 1 bin bin 40960 Oct 21 1997 mkdir > > All password files had been updated during this time, and a user account was > changed. > > Before I could get downstairs to the server, the "libtcl76.a" file > dissappeared. My "messages" log was deleted, and there were no httpd-access > or -error entries for that period of time . . . Like an "alien" abduction, > all overt evidence was erased, but I expect this is a more common "earthly" > problem than that. . . . There was one last entry on the terminal screen, > that a mail error had occurred from "noc.ipspeed.net" -- they show up in > internic as a new ISP in california (I'm on the east coast), so they should > not have been the last bounce for mail to me, and I'm not sure what > connection, if any, they are to my other problem . . . > > QUESTIONS: (1) Is this a known hack ??? It's not a "known hack", but you certainly had intruder activity. > (2) What else should I assume is corrupt, beyond > password and user files. Everything. Extract your *data* only to a backup device, reinstall and reconfigure from scratch. You should be performing regular data backups, so this should be pretty straightforward. > And how do I "delete" a user . . . sysinstall > lets me ADD, but not DELETE, and when it adds it puts stuff in several > different files, so I assume I'll need to go to each of these areas to > delete the specific user-info . . . . ?? 'pw userdel -r' is pretty effective. > (3) What do I do to keep it from happening again ??? If you're running the Qualcomm pop server 'popper' you should upgrade it as there are known exploits. In general, you should ensure that you subscribe to the freebsd-security list, and check out the security advisories on a regular basis. When you reinstall, I would suggest moving to 2.2.7 and correspondingly upgrading apache and any CGI utilities that you're using. Be aware that while your system is in its compromised state (ie. now) it is quite likely being used to attack other systems. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Jul 30 13:23:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15112 for freebsd-stable-outgoing; Thu, 30 Jul 1998 13:23:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rachel.glenatl.glenayre.com (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA15088 for ; Thu, 30 Jul 1998 13:23:31 -0700 (PDT) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by rachel.glenatl.glenayre.com (SMI-8.6/SMI-SVR4) id QAA28034; Thu, 30 Jul 1998 16:16:45 -0400 Received: from jhicks.glenatl.glenayre.com (localhost.glenatl.glenayre.com [127.0.0.1]) by jhicks.glenatl.glenayre.com (8.8.8/8.8.5) with ESMTP id QAA22137; Thu, 30 Jul 1998 16:16:43 -0400 (EDT) Message-Id: <199807302016.QAA22137@jhicks.glenatl.glenayre.com> To: "Bob Boone" cc: freebsd-stable@FreeBSD.ORG, jhicks@jhicks.glenatl.glenayre.com Subject: Re: Security Issue -- In-reply-to: Your message of "Thu, 30 Jul 1998 15:30:42 EDT." <002e01bdbbf0$8e63eb20$ef63a8c0@wizard.whro.org> Date: Thu, 30 Jul 1998 16:16:43 -0400 From: Jerry Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bob, Sorry to hear about your trouble. I would take it as a break-in. Could be a local user though. I would probably reload the system using a new disk, keeping the old one in its current state. Later, after you have a running system, you can probably retrieve most of your web content from the previous disk. It'll be some work; Be most careful about not bringing over any binary programs and make *sure* to check your cgi-bin files for any tampering. I would probably change most user names and passwords too. (But then I'm paranoid :-) - This list concerns matters important to those who track FreeBSD's -STABLE branch. >From your message you don't seem to be doing that. Sadly, this probably would have helped prevent you from experiencing what might have been a known exploit for 2.2.5. Better Luck, Jerry Hicks jhicks@glenatl.glenayre.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 02:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01247 for freebsd-stable-outgoing; Fri, 31 Jul 1998 02:52:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from internationalschool.co.uk ([194.72.37.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01236 for ; Fri, 31 Jul 1998 02:52:07 -0700 (PDT) (envelope-from stuart@internationalschool.co.uk) Received: from internationalschool.co.uk (bamboo.tis [10.0.0.70]) by internationalschool.co.uk (8.8.8/8.8.8) with ESMTP id KAA08074; Fri, 31 Jul 1998 10:40:03 +0100 (BST) Message-ID: <35C19133.5145D67F@internationalschool.co.uk> Date: Fri, 31 Jul 1998 10:41:07 +0100 From: Stuart Henderson Organization: The International School X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: Bob Boone , freebsd-stable@FreeBSD.ORG Subject: Re: Security Issue -- References: <199807301942.MAA00458@dingo.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: > 'pw userdel -r' is pretty effective. rmuser(8) http://www.cert.org/ has a lot of advice about recovering from root compromise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 08:07:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06818 for freebsd-stable-outgoing; Fri, 31 Jul 1998 08:07:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ccsales.com (ccsales.ccsales.com [207.137.172.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06812 for ; Fri, 31 Jul 1998 08:07:14 -0700 (PDT) (envelope-from randyk@ccsales.com) Received: from ntrkcasa (b217.ecom.net [207.13.225.217]) by ccsales.com (8.9.0/8.9.0) with SMTP id IAA27750 for ; Fri, 31 Jul 1998 08:07:02 -0700 (PDT) Message-Id: <3.0.5.32.19980731080248.034bcbc0@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 31 Jul 1998 08:02:48 -0700 To: freebsd-stable@FreeBSD.ORG From: "Randy A. Katz" Subject: Larger then 8.5GB IDE Support - 2.2 stable In-Reply-To: <35C19133.5145D67F@internationalschool.co.uk> References: <199807301942.MAA00458@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Is support for the larger IDE drives still in 2.2 stable? I loaded it up on a 4.5GB primary drive and tried to add a 11.5GB secondary and it showed the partition as 8.xGB...any ideas??? Thank you, Randy Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 09:39:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16701 for freebsd-stable-outgoing; Fri, 31 Jul 1998 09:39:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ccsales.com (ccsales.ccsales.com [207.137.172.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16685 for ; Fri, 31 Jul 1998 09:39:29 -0700 (PDT) (envelope-from randyk@ccsales.com) Received: (from randyk@localhost) by ccsales.com (8.9.0/8.9.0) id JAA29055; Fri, 31 Jul 1998 09:39:27 -0700 (PDT) Message-ID: <19980731093927.14206@com> Date: Fri, 31 Jul 1998 09:39:27 -0700 From: randyk To: freebsd-stable@FreeBSD.ORG Subject: Larger then 8.5GB IDE Support - 2.2 stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Is support for the larger IDE drives still in 2.2 stable? I loaded it up on a 4.5GB primary drive and tried to add a 11.5GB secondary and it showed the partition as 8.xGB...any ideas??? Thank you, Randy Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 09:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17304 for freebsd-stable-outgoing; Fri, 31 Jul 1998 09:42:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ccsales.com (ccsales.ccsales.com [207.137.172.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17222 for ; Fri, 31 Jul 1998 09:42:12 -0700 (PDT) (envelope-from randyk@ccsales.com) Received: (from randyk@localhost) by ccsales.com (8.9.0/8.9.0) id JAA29122; Fri, 31 Jul 1998 09:42:05 -0700 (PDT) Message-ID: <19980731094205.02097@com> Date: Fri, 31 Jul 1998 09:42:05 -0700 From: randyk To: freebsd-stable@FreeBSD.ORG Subject: Larger then 8.5GB IDE Support - 2.2 stable Reply-To: randyk@ccsales.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Is support for the larger IDE drives still in 2.2 stable? I loaded it up on a 4.5GB primary drive and tried to add a 11.5GB secondary and it showed the partition as 8.xGB...any ideas??? Thank you, Randy Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 09:57:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19082 for freebsd-stable-outgoing; Fri, 31 Jul 1998 09:57:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19075 for ; Fri, 31 Jul 1998 09:57:51 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with SMTP id JAA29519; Fri, 31 Jul 1998 09:57:43 -0700 (PDT) Date: Fri, 31 Jul 1998 09:57:43 -0700 (PDT) From: Brooks Davis Reply-To: brooks@one-eyed-alien.net To: "Randy A. Katz" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Larger then 8.5GB IDE Support - 2.2 stable In-Reply-To: <3.0.5.32.19980731080248.034bcbc0@ccsales.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 Fri, 31 Jul 1998, Randy A. Katz wrote: > Is support for the larger IDE drives still in 2.2 stable? I loaded it up on > a 4.5GB primary drive and tried to add a 11.5GB secondary and it showed the > partition as 8.xGB...any ideas??? It's probably a BIOS problem. See the following white paper at IBM: http://www.storage.ibm.com/hardsoft/diskdrdl/library/8.4gb.htm -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 10:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23747 for freebsd-stable-outgoing; Fri, 31 Jul 1998 10:27:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netmug.org (netmug.org [207.88.43.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23738 for ; Fri, 31 Jul 1998 10:27:15 -0700 (PDT) (envelope-from perl@netmug.org) Received: from localhost (perl@localhost) by netmug.org (8.8.8/NetMUG_1.0.0) with SMTP id KAA13624; Fri, 31 Jul 1998 10:22:13 -0700 (PDT) Date: Fri, 31 Jul 1998 10:22:13 -0700 (PDT) From: perl To: Brooks Davis cc: "Randy A. Katz" , freebsd-stable@FreeBSD.ORG Subject: Re: Larger then 8.5GB IDE Support - 2.2 stable 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 I've got the same problem, but my bios shows the actual size of the drive. Michael On Fri, 31 Jul 1998, Brooks Davis wrote: > On Fri, 31 Jul 1998, Randy A. Katz wrote: > > > Is support for the larger IDE drives still in 2.2 stable? I loaded it up on > > a 4.5GB primary drive and tried to add a 11.5GB secondary and it showed the > > partition as 8.xGB...any ideas??? > > It's probably a BIOS problem. See the following white paper at IBM: > > http://www.storage.ibm.com/hardsoft/diskdrdl/library/8.4gb.htm > > -- Brooks > > > 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 Jul 31 10:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26493 for freebsd-stable-outgoing; Fri, 31 Jul 1998 10:47:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26488 for ; Fri, 31 Jul 1998 10:46:59 -0700 (PDT) (envelope-from igor@alecto.physics.uiuc.edu) Received: (from igor@localhost) by alecto.physics.uiuc.edu (8.9.0/8.9.0) id MAA03242 for stable@freebsd.org; Fri, 31 Jul 1998 12:46:55 -0500 (CDT) From: Igor Roshchin Message-Id: <199807311746.MAA03242@alecto.physics.uiuc.edu> Subject: T440BX and Symbios Logic* 53C875JBE To: stable@FreeBSD.ORG Date: Fri, 31 Jul 1998 12:46:55 -0500 (CDT) 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 Hello, sorry if this should've gone to a different list. I wonder if the the Intel T440BX motherboard is currently supported ? Besides overall support by FreeBSD, my two main concerns are: 1. Conflict between integrated PCI Cirrus Logic* GD 5480 graphics controller and AGP graphics controller plugged into the AGP slot. 2. SCSI controller: Symbios Logic* 53C875JBE Ultra I didn't find any reference to it in the Handbook/FAQ However it seems to be somewhat relevant to NCR 53C875 mentioned as being supported. Thanks, IgoR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 10:49:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26782 for freebsd-stable-outgoing; Fri, 31 Jul 1998 10:49:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ccsales.com (ccsales.ccsales.com [207.137.172.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26750 for ; Fri, 31 Jul 1998 10:48:58 -0700 (PDT) (envelope-from randyk@ccsales.com) Received: (from randyk@localhost) by ccsales.com (8.9.0/8.9.0) id KAA00163; Fri, 31 Jul 1998 10:48:47 -0700 (PDT) Message-ID: <19980731104847.17879@com> Date: Fri, 31 Jul 1998 10:48:47 -0700 From: randyk To: perl Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Larger then 8.5GB IDE Support - 2.2 stable Reply-To: randyk@ccsales.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from perl on Fri, Jul 31, 1998 at 10:22:13AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's not a BIOS problem. I am loading 3.0 SNAP now which sees it fine...someone took it out of 2.2 stable (could you please put it back or are there problems???). Thank you, Randy Katz On Fri, Jul 31, 1998 at 10:22:13AM -0700, perl wrote: > I've got the same problem, but my bios shows the actual size of the drive. > > Michael > > On Fri, 31 Jul 1998, Brooks Davis wrote: > > > On Fri, 31 Jul 1998, Randy A. Katz wrote: > > > > > Is support for the larger IDE drives still in 2.2 stable? I loaded it up on > > > a 4.5GB primary drive and tried to add a 11.5GB secondary and it showed the > > > partition as 8.xGB...any ideas??? > > > > It's probably a BIOS problem. See the following white paper at IBM: > > > > http://www.storage.ibm.com/hardsoft/diskdrdl/library/8.4gb.htm > > > > -- Brooks > > > > > > 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 Jul 31 10:51:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27228 for freebsd-stable-outgoing; Fri, 31 Jul 1998 10:51:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ccsales.com (ccsales.ccsales.com [207.137.172.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27221 for ; Fri, 31 Jul 1998 10:51:41 -0700 (PDT) (envelope-from randyk@ccsales.com) Received: (from randyk@localhost) by ccsales.com (8.9.0/8.9.0) id KAA00217; Fri, 31 Jul 1998 10:51:33 -0700 (PDT) Message-ID: <19980731105133.11999@com> Date: Fri, 31 Jul 1998 10:51:33 -0700 From: randyk To: freebsd-stable@FreeBSD.ORG Subject: Love Reply-To: randyk@ccsales.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I love this FreeBSD stuff. I'm loading the 3.0 SNAP on the same box that I am sending this email off from on the maintenance console (F4) .. try that on any Win (yo mama) *.* box!!! Take care... Randy Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 11:08:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29357 for freebsd-stable-outgoing; Fri, 31 Jul 1998 11:08:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ian.axess.net (ian.axess.net [205.247.138.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29350 for ; Fri, 31 Jul 1998 11:08:48 -0700 (PDT) (envelope-from dfe@ian.axess.net) Received: from localhost (dfe@localhost) by ian.axess.net (8.8.7/8.8.7) with SMTP id OAA02857 for ; Fri, 31 Jul 1998 14:06:05 -0400 Date: Fri, 31 Jul 1998 14:06:05 -0400 (EDT) From: Doug Elznic To: freebsd-stable@FreeBSD.ORG Subject: Making a Free BSD CDROM 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, I am interested in making a FreeBSD cdrom. What directories do I need to get? Is thier a gzip of everything or better yet is there an iso image? Are there any cdrom vendors on this list that have an ISO image available? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 12:40:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11656 for freebsd-stable-outgoing; Fri, 31 Jul 1998 12:40:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11651 for ; Fri, 31 Jul 1998 12:40:43 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id MAA24929; Fri, 31 Jul 1998 12:38:58 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: randyk@ccsales.com cc: perl , freebsd-stable@FreeBSD.ORG Subject: Re: Larger then 8.5GB IDE Support - 2.2 stable In-reply-to: Your message of "Fri, 31 Jul 1998 10:48:47 PDT." <19980731104847.17879@com> Date: Fri, 31 Jul 1998 12:38:58 -0700 Message-ID: <24925.901913938@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's not a BIOS problem. I am loading 3.0 SNAP now which sees it > fine...someone took it out of 2.2 stable (could you please put it > back or are there problems???). It was never _in_ 2.2-stable. This is purely a 3.0 feature. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 13:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16674 for freebsd-stable-outgoing; Fri, 31 Jul 1998 13:13:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16660 for ; Fri, 31 Jul 1998 13:13:38 -0700 (PDT) (envelope-from manar@ivision.co.uk) Received: from pretender.ivision.co.uk [195.50.91.43] by stingray.ivision.co.uk with smtp (Exim 1.62 #2) id 0z2LYS-0005I7-00; Fri, 31 Jul 1998 21:13:32 +0100 Message-Id: <3.0.5.32.19980731211323.0094b520@stingray.ivision.co.uk> X-Sender: manarpop@stingray.ivision.co.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 31 Jul 1998 21:13:23 +0100 To: freebsd-stable@FreeBSD.ORG From: Manar Hussain Subject: Re: Larger then 8.5GB IDE Support - 2.2 stable Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> It's not a BIOS problem. I am loading 3.0 SNAP now which sees it >> fine...someone took it out of 2.2 stable (could you please put it >> back or are there problems???). > >It was never _in_ 2.2-stable. This is purely a 3.0 feature. Indeed - I trust we're not too likely to have much the same flamelet thread we @ivision caused with our last query on this. Very brief summary: there is a patch that works under 2.2 but it has a problem under certain conditions (can't remeber what they were) - hence it was not considered appropriate for -stable. I can't dig the thread out from the archives but I'm sure somene else here has a reference. It's not in 2.2.7, by the time 2.2.8 is out we'll be pretty much into 3.0+ so let's not have a huge thread on why it's not in 2.2* as it's too late to be much more than a slanging match. The key I think is to have the details on the patch to the wd driver appropriately available (i.e. *please* put it in the FAQ as it's going to be a common request) - along with appropriate warnings about any gotchas. Manar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 31 13:55:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24568 for freebsd-stable-outgoing; Fri, 31 Jul 1998 13:55:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24561 for ; Fri, 31 Jul 1998 13:55:37 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA02835; Fri, 31 Jul 1998 08:40:39 -0700 (PDT) Message-Id: <199807311540.IAA02835@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Randy A. Katz" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Larger then 8.5GB IDE Support - 2.2 stable In-reply-to: Your message of "Fri, 31 Jul 1998 08:02:48 PDT." <3.0.5.32.19980731080248.034bcbc0@ccsales.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 08:40:35 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello All, > > Is support for the larger IDE drives still in 2.2 stable? I loaded it up on > a 4.5GB primary drive and tried to add a 11.5GB secondary and it showed the > partition as 8.xGB...any ideas??? You need to enable LBA mode for the 'wd' driver; see the wd(4) manpage. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Fri Jul 31 19:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17849 for freebsd-stable-outgoing; Fri, 31 Jul 1998 19:47:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pobox.ids.net (pobox.ids.net [155.212.1.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17842 for ; Fri, 31 Jul 1998 19:47:18 -0700 (PDT) (envelope-from bobfe@ids.net) Received: from brussel (brussel.ids.nettv.net [155.212.5.2]) by pobox.ids.net (8.9.0/8.9.0) with SMTP id WAA05287 for ; Fri, 31 Jul 1998 22:47:05 -0400 (EDT) Message-Id: <199808010247.WAA05287@pobox.ids.net> X-Sender: bobfe@mb.home.ids.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 31 Jul 1998 22:46:55 -0400 To: freebsd-stable@FreeBSD.ORG From: Bob Fayne Subject: Re: Larger then 8.5GB IDE Support - 2.2 stable In-Reply-To: <199807311940.MAA11663@hub.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 At 12:40 PM 7/31/98, you wrote: >> It's not a BIOS problem. I am loading 3.0 SNAP now which sees it >> fine...someone took it out of 2.2 stable (could you please put it >> back or are there problems???). > >It was never _in_ 2.2-stable. This is purely a 3.0 feature. Ok, what did do wrong..or right? The BIOS showed this as an 8.5gig drive. FreeBSD 2.2.2-RELEASE wdc0: unit 0 (wd0): wd0: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S Filesystem 1K-blocks /dev/wd0s1c 9799976 --- Bob Fayne bobfe@ids.net Systems Administrator (401) 885-4243 x 228 http://www.ids.net/bobfe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 00:58:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15907 for freebsd-stable-outgoing; Sat, 1 Aug 1998 00:58:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from billy.queens.unimelb.edu.au ([203.28.244.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15887 for ; Sat, 1 Aug 1998 00:58:28 -0700 (PDT) (envelope-from bromage@billy.queens.unimelb.edu.au) Received: (from bromage@localhost) by billy.queens.unimelb.edu.au (8.8.8/8.8.8) id SAA21790; Sat, 1 Aug 1998 18:04:02 +1000 (EST) (envelope-from bromage) Message-ID: <19980801180401.24027@queens.unimelb.edu.au> Date: Sat, 1 Aug 1998 18:04:01 +1000 From: Andrew Bromage To: freebsd-stable@FreeBSD.ORG Subject: CD writers as a backup medium References: <199807311940.MAA11663@hub.freebsd.org> <199808010247.WAA05287@pobox.ids.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199808010247.WAA05287@pobox.ids.net>; from Bob Fayne on Fri, Jul 31, 1998 at 10:46:55PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day all. Just wondered if anyone had thoughts on using a CD writer with FreeBSD-stable as a backup medium. Does the lack of hard real-timeness matter? Like, if some other process starts thrashing, will my CD be ruined? Is the support for some writers better than others? Should I just stick with tape? Sharing of experiences would be greatly appreciated. Cheers, Andrew Bromage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 03:35:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29117 for freebsd-stable-outgoing; Sat, 1 Aug 1998 03:35:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tweetie.online.barbour-index.co.uk (tweetie-pipex.online.barbour-index.co.uk [194.129.192.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29099 for ; Sat, 1 Aug 1998 03:35:42 -0700 (PDT) (envelope-from scot@planet-three.com) Received: from localhost (scot@localhost) by tweetie.online.barbour-index.co.uk (8.8.8/8.8.8) with SMTP id LAA06431; Sat, 1 Aug 1998 11:34:50 +0100 (BST) (envelope-from scot@planet-three.com) X-Authentication-Warning: tweetie.online.barbour-index.co.uk: scot owned process doing -bs Date: Sat, 1 Aug 1998 11:34:50 +0100 (BST) From: Scot Elliott X-Sender: scot@tweetie.online.barbour-index.co.uk To: Andrew Bromage cc: freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium In-Reply-To: <19980801180401.24027@queens.unimelb.edu.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 Hi. I use a Plasmon CDR-480 (which is just a Panasonic CW-7502. It's supported by the cdrecord port. cdrecord automatically sets its priotity quite high, but I personally run it and the mkisofs process with real time priority (see rtprio). I believe this is what /usr/share/examples/worm/... use with the worm devices. My machine isn't overloaded, so I can't say what happens during high usage, but I've never had an overrun yet - and I always do mkisofs-cdrecord piping rather than creating an ISO image first. If you want any more help let me know. Scot. On Sat, 1 Aug 1998, Andrew Bromage wrote: > G'day all. > > Just wondered if anyone had thoughts on using a CD writer with > FreeBSD-stable as a backup medium. Does the lack of hard real-timeness > matter? Like, if some other process starts thrashing, will my CD be > ruined? Is the support for some writers better than others? Should I > just stick with tape? > > Sharing of experiences would be greatly appreciated. > > Cheers, > Andrew Bromage > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org, scot@cx) | Work: +44 (0)171 7046777 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 07:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15463 for freebsd-stable-outgoing; Sat, 1 Aug 1998 07:19:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15458 for ; Sat, 1 Aug 1998 07:18:58 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id QAA13084 for ; Sat, 1 Aug 1998 16:18:41 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id QAA04923 for ; Sat, 1 Aug 1998 16:18:43 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id QAA07060 for ; Sat, 1 Aug 1998 16:18:44 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808011418.QAA20459@internal> Subject: Re: CD writers as a backup medium In-Reply-To: from Scot Elliott at "Aug 1, 98 11:34:50 am" To: scot@planet-three.com (Scot Elliott) Date: Sat, 1 Aug 1998 16:18:35 +0200 (CEST) Cc: bromage@queens.unimelb.edu.au, freebsd-stable@FreeBSD.ORG 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 > Hi. > > I use a Plasmon CDR-480 (which is just a Panasonic CW-7502. It's > supported by the cdrecord port. I am using the old CDR100 from Yamaha with cdrecord (no CAM). > > cdrecord automatically sets its priotity quite high, but I personally run > it and the mkisofs process with real time priority (see rtprio). I That's what I do as well (rtprio 5, yes, the number doesn't matter as long as it's the only rtprio process). > believe this is what /usr/share/examples/worm/... use with the worm > devices. My machine isn't overloaded, so I can't say what happens during > high usage, but I've never had an overrun yet - and I always do Think you mean an underrun here :-) > mkisofs-cdrecord piping rather than creating an ISO image first. I create the iso image first but while running cdrecord with rtprio, I make a buildworld, use netscape, run rc5,... all at the same time and never got an underrun. I am writing my CDs at 4x speed :-) The write buffer never goes below 97% and the CDR100 only has 256k buffer. > > If you want any more help let me know. > > Scot. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 07:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17469 for freebsd-stable-outgoing; Sat, 1 Aug 1998 07:50:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.fcc.net (shell.fcc.net [207.198.253.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17452 for ; Sat, 1 Aug 1998 07:50:25 -0700 (PDT) (envelope-from nathan@shell.fcc.net) Received: (from nathan@localhost) by shell.fcc.net (8.8.8/8.8.8) id KAA12534; Sat, 1 Aug 1998 10:50:21 -0400 (EDT) (envelope-from nathan) Message-ID: <19980801105021.B12513@fcc.net> Date: Sat, 1 Aug 1998 10:50:21 -0400 From: Nathan Dorfman To: Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium References: <199807311940.MAA11663@hub.freebsd.org> <199808010247.WAA05287@pobox.ids.net> <19980801180401.24027@queens.unimelb.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980801180401.24027@queens.unimelb.edu.au>; from Andrew Bromage on Sat, Aug 01, 1998 at 06:04:01PM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 01, 1998 at 06:04:01PM +1000, Andrew Bromage wrote: > G'day all. > > Just wondered if anyone had thoughts on using a CD writer with > FreeBSD-stable as a backup medium. Does the lack of hard real-timeness > matter? Like, if some other process starts thrashing, will my CD be > ruined? Is the support for some writers better than others? Should I > just stick with tape? Yes, the lack of hard real-timeness matters. CD writers ideally want a constant stream of data. Depending on the size of the buffer in your drive, you can interrupt the stream for as much as a second or two. However, if some other process starts thrashing and the CDR drive's buffer *is* exhausted, there is nothing more to write and you're SOL, as that CD is now a coaster. This is why people make filesystems on their hard disk and then burn it to CD. However, if the system is mostly idle, and you have a fast disk, you shouldn't have too many problems backing up to CD. You may want to consider sticking to tape though. Tapes hold what, 4 gigs? CD-ROMS hold 650MB. > Cheers, > Andrew Bromage -- Nathan Dorfman | E-mail: nathan@fcc.net Frontline Communications | Front desk: 914-623-8553: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 10:11:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28270 for freebsd-stable-outgoing; Sat, 1 Aug 1998 10:11:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28263 for ; Sat, 1 Aug 1998 10:11:36 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id KAA09722; Sat, 1 Aug 1998 10:10:29 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Sat, 1 Aug 1998 10:10:29 -0700 (PDT) From: Scott To: Nathan Dorfman cc: Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium In-Reply-To: <19980801105021.B12513@fcc.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 On Sat, 1 Aug 1998, Nathan Dorfman wrote: > On Sat, Aug 01, 1998 at 06:04:01PM +1000, Andrew Bromage wrote: > > G'day all. > > > > Just wondered if anyone had thoughts on using a CD writer with > > FreeBSD-stable as a backup medium. Does the lack of hard real-timeness > > matter? Like, if some other process starts thrashing, will my CD be > > ruined? Is the support for some writers better than others? Should I > > just stick with tape? > > Yes, the lack of hard real-timeness matters. CD writers ideally > want a constant stream of data. Depending on the size of the buffer > in your drive, you can interrupt the stream for as much as a second > or two. However, if some other process starts thrashing and the CDR > drive's buffer *is* exhausted, there is nothing more to write and > you're SOL, as that CD is now a coaster. > > This is why people make filesystems on their hard disk and then burn > it to CD. However, if the system is mostly idle, and you have a fast > disk, you shouldn't have too many problems backing up to CD. You may > want to consider sticking to tape though. Tapes hold what, 4 gigs? > CD-ROMS hold 650MB. tapes may be 4GB, but most of them are extremely slow compared to a CD-R. Even some of the fastest tape drives aren't as fast as a 4x CD-R (last time i checked). Tape drives are also a lot more expensive and the tapes are EXTREMELY expensive. CD-R disk can be found for $1 or less if you have a rebate. Tapes for my TR1 drive (old; never in use anymore) are $30 each...and i have 5 tapes for them. So it really comes down to how much money you have. > > Cheers, > > Andrew Bromage > > -- > Nathan Dorfman | E-mail: nathan@fcc.net > Frontline Communications | Front desk: 914-623-8553: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 11:44:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07717 for freebsd-stable-outgoing; Sat, 1 Aug 1998 11:44:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.fcc.net (shell.fcc.net [207.198.253.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07711 for ; Sat, 1 Aug 1998 11:44:52 -0700 (PDT) (envelope-from nathan@shell.fcc.net) Received: (from nathan@localhost) by shell.fcc.net (8.8.8/8.8.8) id OAA12737; Sat, 1 Aug 1998 14:43:34 -0400 (EDT) (envelope-from nathan) Message-ID: <19980801144333.A12731@fcc.net> Date: Sat, 1 Aug 1998 14:43:33 -0400 From: Nathan Dorfman To: Scott Cc: Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium References: <19980801105021.B12513@fcc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Scott on Sat, Aug 01, 1998 at 10:10:29AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 01, 1998 at 10:10:29AM -0700, Scott wrote: > > > On Sat, 1 Aug 1998, Nathan Dorfman wrote: > > > On Sat, Aug 01, 1998 at 06:04:01PM +1000, Andrew Bromage wrote: > > > G'day all. > > > > > > Just wondered if anyone had thoughts on using a CD writer with > > > FreeBSD-stable as a backup medium. Does the lack of hard real-timeness > > > matter? Like, if some other process starts thrashing, will my CD be > > > ruined? Is the support for some writers better than others? Should I > > > just stick with tape? > > > > Yes, the lack of hard real-timeness matters. CD writers ideally > > want a constant stream of data. Depending on the size of the buffer > > in your drive, you can interrupt the stream for as much as a second > > or two. However, if some other process starts thrashing and the CDR > > drive's buffer *is* exhausted, there is nothing more to write and > > you're SOL, as that CD is now a coaster. > > > > This is why people make filesystems on their hard disk and then burn > > it to CD. However, if the system is mostly idle, and you have a fast > > disk, you shouldn't have too many problems backing up to CD. You may > > want to consider sticking to tape though. Tapes hold what, 4 gigs? > > CD-ROMS hold 650MB. > > tapes may be 4GB, but most of them are extremely slow compared to a CD-R. > Even some of the fastest tape drives aren't as fast as a 4x CD-R (last > time i checked). Tape drives are also a lot more expensive and the tapes > are EXTREMELY expensive. CD-R disk can be found for $1 or less if you have > a rebate. Tapes for my TR1 drive (old; never in use anymore) are $30 > each...and i have 5 tapes for them. So it really comes down to how much > money you have. A 90 meter DAT tape can hold up to 4 gigs per tape. You can get them for about $9 a piece, according to people who buy them. You'll need 6 CDs to back up 4 gigs on CD, that's $6-9. Use the DAT tape twice and you've already gotten your money's worth. A good CD-R drive is $400 (SCSI). How much is a SCSI DAT drive, anyone? Plus, I'm not even mentioning that you can buy 120m tapes for only a few dollars more. > > -- > > Nathan Dorfman | E-mail: nathan@fcc.net > > Frontline Communications | Front desk: 914-623-8553: > > -scott -- Nathan Dorfman | E-mail: nathan@fcc.net Frontline Communications | Front desk: 914-623-8553: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 12:10:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10668 for freebsd-stable-outgoing; Sat, 1 Aug 1998 12:10:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from neale.econ.vt.edu (neale.econ.vt.edu [128.173.173.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10662 for ; Sat, 1 Aug 1998 12:09:58 -0700 (PDT) (envelope-from rdmurphy@neale.econ.vt.edu) Received: (from rdmurphy@localhost) by neale.econ.vt.edu (8.8.8/8.8.8) id PAA13146; Sat, 1 Aug 1998 15:12:52 -0400 (EDT) (envelope-from rdmurphy) Date: Sat, 1 Aug 1998 15:12:52 -0400 (EDT) Message-Id: <199808011912.PAA13146@neale.econ.vt.edu> From: "Russell D. Murphy" To: stable@FreeBSD.ORG Subject: addgroup and rmgroup? Reply-to: rdmurphy@vt.edu Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG addgroup seems to have a typo on my machine: #!/usr/bin/tclsh # Copyright (c) 1996 Wolfram Schneider . Berlin. # All rights reserved. < ... > I also note that neither addgroup nor rmgroup seemed to have been updated after my most recent make world (or the earlier ones, either). Everything else seems fine. The system is running: neale [rdmurphy]% uname -a FreeBSD neale.econ.vt.edu 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Tue Jul 28 17:19:46 EDT 1998 root@neale.econ.vt.edu:/usr/src/sys/compile/NEALE i386 Have these utilities disappeared? Russ Murphy ----- 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 Sat Aug 1 12:29:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12677 for freebsd-stable-outgoing; Sat, 1 Aug 1998 12:29:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12662 for ; Sat, 1 Aug 1998 12:29:32 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id PAA12685; Sat, 1 Aug 1998 15:28:03 -0400 (EDT) Message-Id: <199808011928.PAA12685@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Scott cc: Nathan Dorfman , Andrew Bromage , freebsd-stable@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: CD writers as a backup medium References: In-reply-to: Your message of "Sat, 01 Aug 1998 10:10:29 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 15:28:02 -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > tapes may be 4GB, but most of them are extremely slow compared to a CD-R. > Even some of the fastest tape drives aren't as fast as a 4x CD-R (last > time i checked). Tape drives are also a lot more expensive and the tapes > are EXTREMELY expensive. CD-R disk can be found for $1 or less if you have > a rebate. Tapes for my TR1 drive (old; never in use anymore) are $30 > each...and i have 5 tapes for them. So it really comes down to how much > money you have. > Sounds like you should have bought a DAT tape then. A DDS-2 drive (without compression) has a 326 kByte/s transfer rate; this will be somewhat larger if you've got compression enabled in the drive. So you'll have 4 GB uncompressed on a 90 meter tape and perhaps twice that with compression enabled. If this is large enough to hold your dump, then in some sense you don't really care what the transfer rate is if you don't have to swap media. I bought a reconditioned DDS-2 changer (that holds 4 or 12 tapes depending on the magazine) for a bit less than $400. Media is about $7-$12 depending on what you find. DDS-3 increases the capacity (and thus transfer rate) again. I think the media cost might be a wash between CD and DAT for bulk storage. The CD media is less clostly, but has a factor of about 3 or 4 less capacity. The DAT media is resuable - sure, you can get rewritable CD media, but now the cost is considerably higher. Clearly the Travan drives lose on a cost measure - the drives are cheap, but you go broke buying the media. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 12:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13466 for freebsd-stable-outgoing; Sat, 1 Aug 1998 12:36:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from icarus.eng.mindspring.net (icarus.eng.mindspring.net [207.69.192.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13444 for ; Sat, 1 Aug 1998 12:35:59 -0700 (PDT) (envelope-from dmayne@icarus.eng.mindspring.net) Received: (from dmayne@localhost) by icarus.eng.mindspring.net (8.8.7/8.8.7) id PAA10383 for freebsd-stable@FreeBSD.ORG; Sat, 1 Aug 1998 15:38:01 -0400 (EDT) From: David Mayne Message-Id: <199808011938.PAA10383@icarus.eng.mindspring.net> Subject: Re: CD writers as a backup medium In-Reply-To: <19980801144333.A12731@fcc.net> from Nathan Dorfman at "Aug 1, 98 02:43:33 pm" To: freebsd-stable@FreeBSD.ORG Date: Sat, 1 Aug 1998 15:38:01 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Sat, 1 Aug 1998, Nathan Dorfman wrote: > > A 90 meter DAT tape can hold up to 4 gigs per tape. You can get them > for about $9 a piece, according to people who buy them. You'll need > 6 CDs to back up 4 gigs on CD, that's $6-9. Use the DAT tape twice > and you've already gotten your money's worth. A good CD-R drive is > $400 (SCSI). How much is a SCSI DAT drive, anyone? Plus, I'm not > even mentioning that you can buy 120m tapes for only a few dollars > more. Unfortunately, DAT tapes are extremely fragile, can be used only a few times, and can be stored in the best conditions (cool, dust free) for only about a year without risking data loss. The pattern written to the tapes is so tight that you may have bleed over affect with the bits after that year is up. DLT's write a nice wider format, but are very expensive. QIC drives are available from tandenbergdata.com which offer the best long term storage capability, and you can get them up to 5GB, and the drives can be had for around $500 refurbished. Unfortunately, the media is about $35 a tape, but they can be written to many times, and will store for 5-10 years. If you have data that has to be backed up daily, and want the backup to last more than a year, I would suggest QIC. CD's could be useful if you only need to do backups periodically (such as once a month). DAT tapes - in my experience, don't use one more than 5 times, and prepare to have data loss after a year or so, so a once yearly CD burn may be in order. Regards, David dmayne@mindspring.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 12:44:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14328 for freebsd-stable-outgoing; Sat, 1 Aug 1998 12:44:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ainet.com (ainet.com [204.30.40.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14319 for ; Sat, 1 Aug 1998 12:44:02 -0700 (PDT) (envelope-from jmscott@ainet.com) Received: from perl.ainet.com (perl.ainet.com [204.30.40.14]) by ainet.com (8.9.1/8.9.1) with SMTP id MAA12672; Sat, 1 Aug 1998 12:43:44 -0700 (PDT) Message-Id: <3.0.5.32.19980801124448.0082a430@mail.ainet.com> X-Sender: jmscott@mail.ainet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 01 Aug 1998 12:44:48 -0700 To: Nathan Dorfman , Scott From: "Joseph M. Scott" Subject: Re: CD writers as a backup medium Cc: Andrew Bromage , freebsd-stable@FreeBSD.ORG In-Reply-To: <19980801144333.A12731@fcc.net> References: <19980801105021.B12513@fcc.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >A 90 meter DAT tape can hold up to 4 gigs per tape. You can get them >for about $9 a piece, according to people who buy them. You'll need >6 CDs to back up 4 gigs on CD, that's $6-9. Use the DAT tape twice >and you've already gotten your money's worth. A good CD-R drive is >$400 (SCSI). How much is a SCSI DAT drive, anyone? Plus, I'm not >even mentioning that you can buy 120m tapes for only a few dollars >more. > >> > -- >> > Nathan Dorfman | E-mail: nathan@fcc.net >> > Frontline Communications | Front desk: 914-623-8553: We recently sat down and talked about which tape drive to go with. The DAT if I recall are faster, the tapes are cheaper ( around $9 or $10 sounds right I thing, compared to $30 to $40 for most other types ) but the DAT drives usually run over $700 if I recall. For the machines that we were buying that added more cost than we could justify. This is all is US dollars. Joseph Scott jmscott@ainet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 13:00:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16582 for freebsd-stable-outgoing; Sat, 1 Aug 1998 13:00:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16576 for ; Sat, 1 Aug 1998 13:00:33 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id MAA00348; Sat, 1 Aug 1998 12:56:41 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Sat, 1 Aug 1998 12:56:41 -0700 (PDT) From: Scott To: Nathan Dorfman cc: Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium In-Reply-To: <19980801144333.A12731@fcc.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 On Sat, 1 Aug 1998, Nathan Dorfman wrote: > On Sat, Aug 01, 1998 at 10:10:29AM -0700, Scott wrote: > > > > > > On Sat, 1 Aug 1998, Nathan Dorfman wrote: > > > > > On Sat, Aug 01, 1998 at 06:04:01PM +1000, Andrew Bromage wrote: > > > > G'day all. > > > > > > > > Just wondered if anyone had thoughts on using a CD writer with > > > > FreeBSD-stable as a backup medium. Does the lack of hard real-timeness > > > > matter? Like, if some other process starts thrashing, will my CD be > > > > ruined? Is the support for some writers better than others? Should I > > > > just stick with tape? > > > > > > Yes, the lack of hard real-timeness matters. CD writers ideally > > > want a constant stream of data. Depending on the size of the buffer > > > in your drive, you can interrupt the stream for as much as a second > > > or two. However, if some other process starts thrashing and the CDR > > > drive's buffer *is* exhausted, there is nothing more to write and > > > you're SOL, as that CD is now a coaster. > > > > > > This is why people make filesystems on their hard disk and then burn > > > it to CD. However, if the system is mostly idle, and you have a fast > > > disk, you shouldn't have too many problems backing up to CD. You may > > > want to consider sticking to tape though. Tapes hold what, 4 gigs? > > > CD-ROMS hold 650MB. > > > > tapes may be 4GB, but most of them are extremely slow compared to a CD-R. > > Even some of the fastest tape drives aren't as fast as a 4x CD-R (last > > time i checked). Tape drives are also a lot more expensive and the tapes > > are EXTREMELY expensive. CD-R disk can be found for $1 or less if you have > > a rebate. Tapes for my TR1 drive (old; never in use anymore) are $30 > > each...and i have 5 tapes for them. So it really comes down to how much > > money you have. > > A 90 meter DAT tape can hold up to 4 gigs per tape. You can get them > for about $9 a piece, according to people who buy them. You'll need > 6 CDs to back up 4 gigs on CD, that's $6-9. Use the DAT tape twice > and you've already gotten your money's worth. A good CD-R drive is > $400 (SCSI). How much is a SCSI DAT drive, anyone? Plus, I'm not > even mentioning that you can buy 120m tapes for only a few dollars > more. The 7502 can be found for $269 or less for the bare drive. Its a 4x8 drive with 1MB or 2MB cache (can't remember). DAT drives are nice, but the drives are quite expensive. Plus, you can't beat the versatility of a CD-ROM. > > > -- > > > Nathan Dorfman | E-mail: nathan@fcc.net > > > Frontline Communications | Front desk: 914-623-8553: > > > > -scott > > -- > Nathan Dorfman | E-mail: nathan@fcc.net > Frontline Communications | Front desk: 914-623-8553: > > 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 Sat Aug 1 13:00:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16611 for freebsd-stable-outgoing; Sat, 1 Aug 1998 13:00:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16601 for ; Sat, 1 Aug 1998 13:00:47 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id MAA00337; Sat, 1 Aug 1998 12:53:57 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Sat, 1 Aug 1998 12:53:57 -0700 (PDT) From: Scott To: "Louis A. Mamakos" cc: Nathan Dorfman , Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium In-Reply-To: <199808011928.PAA12685@whizzo.transsys.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 Sat, 1 Aug 1998, Louis A. Mamakos wrote: > > > tapes may be 4GB, but most of them are extremely slow compared to a CD-R. > > Even some of the fastest tape drives aren't as fast as a 4x CD-R (last > > time i checked). Tape drives are also a lot more expensive and the tapes > > are EXTREMELY expensive. CD-R disk can be found for $1 or less if you have > > a rebate. Tapes for my TR1 drive (old; never in use anymore) are $30 > > each...and i have 5 tapes for them. So it really comes down to how much > > money you have. > > > > Sounds like you should have bought a DAT tape then. should have but at the times i had a budget of $200 > > A DDS-2 drive (without compression) has a 326 kByte/s transfer rate; this > will be somewhat larger if you've got compression enabled in the drive. So > you'll have 4 GB uncompressed on a 90 meter tape and perhaps twice that > with compression enabled. > > If this is large enough to hold your dump, then in some sense you don't > really care what the transfer rate is if you don't have to swap media. i was only using my backups to store junk i downloaded. (Back in my windows days) > > I bought a reconditioned DDS-2 changer (that holds 4 or 12 tapes depending > on the magazine) for a bit less than $400. Media is about $7-$12 depending > on what you find. Thats some serious data storage. Brand new that thing would be extremely expensive. > > DDS-3 increases the capacity (and thus transfer rate) again. I think the > media cost might be a wash between CD and DAT for bulk storage. The CD > media is less clostly, but has a factor of about 3 or 4 less capacity. The > DAT media is resuable - sure, you can get rewritable CD media, but now the > cost is considerably higher. CDs are so cheap nowdays that there is no sense for a rewritable when it would be just as quick/easy to rewrite the whole thing. > > Clearly the Travan drives lose on a cost measure - the drives are cheap, but > you go broke buying the media. you can say that again :) > > louie > -scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 15:05:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26173 for freebsd-stable-outgoing; Sat, 1 Aug 1998 15:05:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26160 for ; Sat, 1 Aug 1998 15:04:58 -0700 (PDT) (envelope-from bs@devnull.ruhr.de) Received: (from admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id XAA04655; Sat, 1 Aug 1998 23:36:44 +0200 (MET DST) Received: from [192.168.22.75] (helo=rm.devnull.ruhr.de) by devnull.ruhr.de with esmtp (Exim 1.92 #1) id 0z2ZI1-0002MS-00; Sat, 1 Aug 1998 12:53:29 +0200 Received: from bs by rm.devnull.ruhr.de with local (Exim 1.92 #1) id 0z2ZHr-0001pX-00; Sat, 1 Aug 1998 12:53:19 +0200 To: Andrew Bromage Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium References: <199807311940.MAA11663@hub.freebsd.org> <199808010247.WAA05287@pobox.ids.net> <19980801180401.24027@queens.unimelb.edu.au> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit From: Benedikt Stockebrand Date: 01 Aug 1998 12:53:18 +0200 In-Reply-To: Andrew Bromage's message of "Sat, 1 Aug 1998 18:04:01 +1000" Message-ID: <874svxm0rl.fsf@devnull.ruhr.de> Lines: 57 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Bromage writes: > Just wondered if anyone had thoughts on using a CD writer with > FreeBSD-stable as a backup medium. Writing a CD-ROM on a machine that is doing other things as well is bound to cause trouble. Your backups will be plain unreliable. > Does the lack of hard real-timeness matter? Not as long as the machine isn't too busy. Which you can't guarantee on an ordinary server. > Like, if some other process starts thrashing, will my CD be ruined? Exactly. But there are events short of actual thrashing that may ruin it already. Like a couple processes too many doing disk I/O, e.g. makewhatis or locate.updatedb. > Is the support for some writers better than others? The slower they are the better are your chances that things will work out in spite of other processes. Maybe the writers themselves differ in their cache size, too. > Should I just stick with tape? Yes, except maybe if you've got a dedicated "Toaster" machine and make sure it's only doing one thing at a time. Or shut down your server and do the writing in single user mode or something similar. Anyway, tapes are the better choice. > Sharing of experiences would be greatly appreciated. A DDS-2 streamer is about as expensive in hardware as a CD-Writer, cheaper in media (considering their capacity), faster, requiring less media changes and just more reliable. That is, unless you re-use the tapes too often. If you can afford to spend some money you may even consider a small DLT drive. A DLT 4000 is no more expensive than a dedicated "toaster" box. The media are expensive so you have to recycle them more often (but they'll last more cycles than a DDS tape). If you want to build up an archive of backups they're probably no choice, really. Otherwise go for it if possible. So long, Ben -- Ben(edikt)? Stockebrand Un*x SA My name and email address are not to be added to any list used for advertising purposes. Any sender of unsolicited advertisement e-mail to this address im- plicitly agrees to pay a DM 500 fee to the recipient for proofreading services. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 16:57:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05943 for freebsd-stable-outgoing; Sat, 1 Aug 1998 16:57:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05938 for ; Sat, 1 Aug 1998 16:57:45 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with SMTP id TAA13198; Sat, 1 Aug 1998 19:57:24 -0400 (EDT) Date: Sat, 1 Aug 1998 19:57:23 -0400 (EDT) From: jack To: Benedikt Stockebrand cc: Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium In-Reply-To: <874svxm0rl.fsf@devnull.ruhr.de> 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 1 Aug 1998, Benedikt Stockebrand wrote: > Andrew Bromage writes: > > > Just wondered if anyone had thoughts on using a CD writer with > > FreeBSD-stable as a backup medium. > > Writing a CD-ROM on a machine that is doing other things as well is > bound to cause trouble. Your backups will be plain unreliable. My experience indicates that your statements are wrong. I piped the output of mkisofs to cdrecord in one xterm while doing level 0 dumps of about 4 gigs of files in another. Halfway through burning the CD /etc/daily started and called /etc/security with its `find'. The CD that was produced has been used to install, or upgrade to, 2.2.7 on three different machines so far. I have two 4gig and a 1gig hard drive, the tape drive, the CD burner, and a CD reader on a single Adaptec 2940UW. YMMV. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 1 17:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09883 for freebsd-stable-outgoing; Sat, 1 Aug 1998 17:45:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09878 for ; Sat, 1 Aug 1998 17:45:38 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id TAA09250; Sat, 1 Aug 1998 19:45:13 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 1 Aug 1998 19:45:12 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: jack cc: Benedikt Stockebrand , Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium 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 Sat, 1 Aug 1998, jack wrote: > My experience indicates that your statements are wrong. I piped the > output of mkisofs to cdrecord in one xterm while doing level 0 dumps > of about 4 gigs of files in another. Halfway through burning the CD > /etc/daily started and called /etc/security with its `find'. The CD > that was produced has been used to install, or upgrade to, 2.2.7 on > three different machines so far. > > I have two 4gig and a 1gig hard drive, the tape drive, the CD > burner, and a CD reader on a single Adaptec 2940UW. I was also able to beat my filesystems to death while burning a CD at 2x on an HP 4020e. I have two 4.3GB drives on an NCR 53c875 controller, and the CD writer was on an old Adaotec 1522 (AIC6360, ISA, non-busmastering.. not the most ideal card for the job either). The ISO image was already created, however, not created on the fly. I love FreeBSD... You can't even breathe on the mouse while trying to burn a CD in Winblows without risking a failure. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://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 Sat Aug 1 18:33:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14186 for freebsd-stable-outgoing; Sat, 1 Aug 1998 18:33:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14179 for ; Sat, 1 Aug 1998 18:33:41 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id SAA00668; Sat, 1 Aug 1998 18:32:07 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Sat, 1 Aug 1998 18:32:07 -0700 (PDT) From: Scott To: Chris Dillon cc: jack , Benedikt Stockebrand , Andrew Bromage , freebsd-stable@FreeBSD.ORG Subject: Re: CD writers as a backup medium 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 Sat, 1 Aug 1998, Chris Dillon wrote: > On Sat, 1 Aug 1998, jack wrote: > > > My experience indicates that your statements are wrong. I piped the > > output of mkisofs to cdrecord in one xterm while doing level 0 dumps > > of about 4 gigs of files in another. Halfway through burning the CD > > /etc/daily started and called /etc/security with its `find'. The CD > > that was produced has been used to install, or upgrade to, 2.2.7 on > > three different machines so far. > > > > I have two 4gig and a 1gig hard drive, the tape drive, the CD > > burner, and a CD reader on a single Adaptec 2940UW. > > I was also able to beat my filesystems to death while burning a CD at > 2x on an HP 4020e. I have two 4.3GB drives on an NCR 53c875 > controller, and the CD writer was on an old Adaotec 1522 (AIC6360, > ISA, non-busmastering.. not the most ideal card for the job either). > The ISO image was already created, however, not created on the fly. > > I love FreeBSD... You can't even breathe on the mouse while trying to > burn a CD in Winblows without risking a failure. :-) not trying to sound like i like like windows, but i have used Office 97 apps while burning CDs and it works fine. Never tried under FreeBSD though. > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > /* FreeBSD: The fastest and most stable server OS on the planet. > For Intel x86 and compatibles (SPARC and Alpha under development) > (http://www.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 Sat Aug 1 21:29:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28991 for freebsd-stable-outgoing; Sat, 1 Aug 1998 21:29:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bamboo.verinet.com (bamboo.verinet.com [204.144.246.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28984 for ; Sat, 1 Aug 1998 21:28:59 -0700 (PDT) (envelope-from allenc@verinet.com) Received: from struct. (tulip30.verinet.com [199.45.181.222]) by bamboo.verinet.com (8.8.8/8.7.1) with ESMTP id WAA10032; Sat, 1 Aug 1998 22:28:50 -0600 Received: (from allenc@localhost) by struct. (8.8.8/8.8.8) id WAA04158; Sat, 1 Aug 1998 22:28:06 -0600 (MDT) (envelope-from allenc) Message-ID: <19980801222806.A3869@verinet.com> Date: Sat, 1 Aug 1998 22:28:06 -0600 From: allen campbell To: rdmurphy@vt.edu Cc: stable@FreeBSD.ORG Subject: Re: addgroup and rmgroup? References: <199808011912.PAA13146@neale.econ.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808011912.PAA13146@neale.econ.vt.edu>; from Russell D. Murphy on Sat, Aug 01, 1998 at 03:12:52PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I also note that neither addgroup nor rmgroup seemed to have > been updated after my most recent make world (or the earlier ones, > either). Everything else seems fine. The system is running: > > neale [rdmurphy]% uname -a > FreeBSD neale.econ.vt.edu 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: > Tue Jul 28 17:19:46 EDT 1998 > root@neale.econ.vt.edu:/usr/src/sys/compile/NEALE i386 > > Have these utilities disappeared? See pw(1). -- Allen Campbell allenc@verinet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message