From owner-freebsd-current Sun Aug 27 0:35:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id F3FB837B422; Sun, 27 Aug 2000 00:35:07 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13Swxw-000166-00; Sun, 27 Aug 2000 09:34:53 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e7R7ZXp28310; Sun, 27 Aug 2000 09:35:33 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200008270735.e7R7ZXp28310@grimreaper.grondar.za> To: Adam Back Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG, jeroen@vangelderen.org Subject: Re: yarrow & /dev/random References: <200008262349.SAA06044@cypherspace.org> In-Reply-To: <200008262349.SAA06044@cypherspace.org> ; from Adam Back "Sat, 26 Aug 2000 18:49:56 EST." Date: Sun, 27 Aug 2000 09:35:32 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mark writes: > > [...] > > FreeBSD is using an earlier version of T'so's code; I beiieve he > > improved it later, but it has no (or little) backtracking protection, > > and can be too easily attacked "from both sides". > > OK, I agree that that's an area where yarrow offers better protection. > But it's not like Ted's code is broken or anything. We would break > things using /dev/random by switching as is to yarrow, so this is why > I don't like it: we're trying to improve things (Yarrows protection > aginst the attacks you describe), but in order to do this we're doing > some other damage. We should at least do no damage: we're improving > one thing and breaking something else. Again, I'm not so sure; Yarrow goes to great trouble to protect its internal state; by blocking, I have this very nasty suspicion that this carefully guarded state is being disclosed. The moment you block, you are confiding in the fact that you have no updating entropy, and as a result /dev/urandom gan be attacked to get the internal state. > > > The solution as I see it is to modify yarrow to bypass the yarrow > > > output function and grab raw de-skewing function output for > > > /dev/random output. You'd also want to do what John Kelsey was > > > suggesting and XOR the bypassed de-skewing function output with > > > /dev/urandom output as an additional safety measure. > > > > I'll look that up; It sounds like quite a departure from yarrow to > > me though; that makes me nervous. > > Well you leave most of yarrow alone, you just add the ability to > reserve de-skewing function outputs for /dev/random. /dev/urandom > still goes through the normal yarrow output function. OK - reasonable. > > ...there may not be a suitable monkey at the keyboard. What about > > a server in an unattended colo? MHO - hardware RNG. > > Unattended servers are a problem alright. > > One thing you can do is if your server has any private keys -- and it > generally will have if it's doing crypto -- is mix the private key > into the random pool along with the curren time. As the attacker > doesn't know your private key (if he does it's game over anyway), you > get a /dev/urandom which is secure. That works with what I already have: cat $privatekey > /dev/random :-) > The other thing you can do is mix in encrypted IVs people connecting > to your server send you -- for example SSL, SSH, and PGP and so on > tend to do this. It can't hurt because you're only mixing, and you > can't destroy entropy with a good mixing function; and if you presume > the collection of people who connect to you aren't colluding it helps. > (If there is only one person communicating with you, it doesn't matter > anyway, because they have their own plaintext.) > > We should encourage people to do these two things. I agree. we also need a device driver for Intel's harware RNG. I have some example code. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 1:25: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.253]) by hub.freebsd.org (Postfix) with ESMTP id D357D37B422 for ; Sun, 27 Aug 2000 01:24:58 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7R8OtN01228; Sun, 27 Aug 2000 10:24:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Boris Popov Cc: current@freebsd.org Subject: Re: PATCH: devfs mkIII test & review please. In-Reply-To: Your message of "Sun, 27 Aug 2000 07:12:25 +0700." Date: Sun, 27 Aug 2000 10:24:54 +0200 Message-ID: <1226.967364694@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Boris Popov writes: >On Fri, 18 Aug 2000, Poul-Henning Kamp wrote: > >> Missing: >> Rename >> Subdirs. >> Close some race conditions using guaranteed atomic operations. >> Mountoption (ro ?) to prevent new devices from appearing in an instance. >> All uses of cdevsw_add() needs to be use devfs_clone() instead. > > How should 3rd party KLDs implement cloning function ? For now it >seems to be impossible to use a single binary for DEVFS and non-DEVFS >case. Once the code has been shaken out, the cloning stuff will be standard. Right now I prefer to keep as much as possible under #ifdef DEVFS. See kern/vfs_conf.c for another good reason (besides KLD) to make the cloning stuff standard. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 1:27: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.253]) by hub.freebsd.org (Postfix) with ESMTP id 4F41737B43F for ; Sun, 27 Aug 2000 01:27:00 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7R8QpN01331; Sun, 27 Aug 2000 10:26:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: chris@calldei.com Cc: Boris Popov , freebsd-current@FreeBSD.ORG Subject: Re: official devfs patch for review In-Reply-To: Your message of "Sat, 26 Aug 2000 20:08:44 CDT." <20000826200844.N60058@holly.calldei.com> Date: Sun, 27 Aug 2000 10:26:51 +0200 Message-ID: <1329.967364811@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000826200844.N60058@holly.calldei.com>, Chris Costello writes: >On Sunday, August 27, 2000, Boris Popov wrote: >> No, not all bits are incorporated. At least you've missed two >> important things. First: >> >> # cd /dev/fd >> # ls >> 0 1 2 >> # cd .. >> # ls >> 0 1 2 >> >> And second - directory names supplied by readdir() function >> contains junk characters at the end. > > I'm going to commit some fdescfs-related patches sometime soon >next week. If you're not using the fdescfs code already, I can >probably integrate my work into devfs, since that was the point >of my work on fdescfs. I'm not quite ready to embrace fdescfs yet, I want to get devfs fully debugged first. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 5: 3:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 4795837B422; Sun, 27 Aug 2000 05:03:27 -0700 (PDT) Received: from [10.0.1.3] (dialup180.brussels.skynet.be [195.238.19.180]) by morpheus.skynet.be (Postfix) with ESMTP id 22111DA84; Sun, 27 Aug 2000 14:03:18 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200008270607.XAA09023@mass.osd.bsdi.com> References: <200008270607.XAA09023@mass.osd.bsdi.com> Date: Sun, 27 Aug 2000 14:00:14 +0200 To: Mike Smith From: Brad Knowles Subject: Re: DPT revision....(broken drivers in -STABLE) Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:07 PM -0700 2000/8/26, Mike Smith wrote: > The Linux driver for the V and VI cards is (according to a reliable > source) pretty awful. I've had to keep making modifications to them to get them to compile with newer and newer versions of the kernel, and while I keep contributing those changes back, they never seem to see the light of day. ;-( > I have theoretically production-quality drivers from Adaptec which I will > be committing as soon as I have time to test them (a few days, I hope). Cool! I can't wait! Is there anything I can do to help? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 5:14:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 0DCE537B424 for ; Sun, 27 Aug 2000 05:14:46 -0700 (PDT) Received: from work.mzaki.nom (86.pool1.ipctokyo.att.ne.jp [165.76.245.86]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id VAA00485; Sun, 27 Aug 2000 21:14:35 +0900 (JST) Date: Sun, 27 Aug 2000 21:14:34 +0900 Message-ID: <868ztilx3p.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: current@FreeBSD.ORG Subject: config(8) weirdness X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Can anyone success compiling kernel with the following config? # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices In my box (freshly built today), this config doesn't make atapi-all.o, so that kernel linking get fails. To make kernel, I needed enable 'atapicd'. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 5:33:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 31D4537B422 for ; Sun, 27 Aug 2000 05:33:24 -0700 (PDT) Received: from work.mzaki.nom (86.pool1.ipctokyo.att.ne.jp [165.76.245.86]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id VAA02615; Sun, 27 Aug 2000 21:33:22 +0900 (JST) Date: Sun, 27 Aug 2000 21:33:21 +0900 Message-ID: <867l92lw8e.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: current@FreeBSD.ORG Subject: hints static wiring X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When kernel is built with static device wiring (i.e. 'hints' line is enabled in the config file), is /boot/device.hints required? Doing 'make install' without /boot/device.hints is failed, saying "You must set up a /boot/device.hints file first." Is this right? -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 6:18:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id E412037B42C for ; Sun, 27 Aug 2000 06:18:35 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13T2KX-0000Kw-00; Sun, 27 Aug 2000 15:18:33 +0200 Received: from a2cc4.pppool.de ([213.6.44.196] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #20) id 13T2KX-0008Dq-00; Sun, 27 Aug 2000 15:18:33 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e7RDG2i02168; Sun, 27 Aug 2000 15:16:03 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200008271316.e7RDG2i02168@Magelan.Leidinger.net> Date: Sun, 27 Aug 2000 15:16:01 +0200 (CEST) From: Alexander Leidinger Subject: Re: config(8) weirdness To: mzaki@e-mail.ne.jp Cc: current@FreeBSD.ORG In-Reply-To: <868ztilx3p.wl@tkc.att.ne.jp> MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-967382164=:1457" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-967382164=:1457 Content-Type: TEXT/plain; charset=us-ascii On 27 Aug, Motomichi Matsuzaki wrote: > Can anyone success compiling kernel with the following config? > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > #device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > #options ATA_STATIC_ID #Static device numbering > #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > > In my box (freshly built today), > this config doesn't make atapi-all.o, > so that kernel linking get fails. I've the same problem. At the moment I'm using the attahed patch to work around this problem every time I configure a new kernel (cd /sys/compile/; patch ; Sun, 27 Aug 2000 06:55:25 -0700 (PDT) Received: (from mpp@localhost) by mppsystems.com (8.9.3/8.9.3) id IAA01923 for freebsd-current@freebsd.org; Sun, 27 Aug 2000 08:55:24 -0500 (CDT) (envelope-from mpp) From: Mike Pritchard Message-Id: <200008271355.IAA01923@mppsystems.com> Subject: 5.0-current 20000826 snapshot problems To: freebsd-current@freebsd.org Date: Sun, 27 Aug 2000 08:55:24 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just had a problem trying to install the latest -current snapshot from the 8/26 snap. Background: Windows trashed my hard disk on one of my machines, so I had to do clean install. Since I run -current on that machine anyways, I decided to try the latest snapshot to restore it. Booting kern.flp (i386) gives me (pardon any typos, I'm looking at one screen and typing on the other): FreeBSD/i386 bootstrap loader, Revision 0.8 (root@usw2.freebsd.org, Sat Aug 26 11:14:35 GMT 2000) /kernel text=0x2432ca zf_read: fill error elf_loadexec: archsw.readin failed / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... /kernel text=0x2432ca zf_read: fill error elf_loadexec: archsw.readin failed can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands..... ok ls ----- [ the ls was typed by me ] ------ / d boot kernel.gz ok boot kernel.gz don't know how to load module '/kernel.gz' This isn't a show stopper for me, since I can restore the machine via other methods, but since I haven't done a clean FreeBSD install in a while, I thought I would try our latest & greatest to see how it worked. As you can see, it didn't go very well :-(. -Mike -- Mike Pritchard mpp@FreeBSD.org or mpp@mppsystems.com ----- End of forwarded message from Mike Pritchard ----- -- Mike Pritchard mpp@FreeBSD.org or mpp@mppsystems.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 8:10:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherspace.org (modemcable228.178-201-24.mtl.mc.videotron.net [24.201.178.228]) by hub.freebsd.org (Postfix) with ESMTP id 743FD37B424; Sun, 27 Aug 2000 08:10:23 -0700 (PDT) Received: (from adam@localhost) by cypherspace.org (8.8.3/8.6.12) id LAA07481; Sun, 27 Aug 2000 11:11:55 -0500 Date: Sun, 27 Aug 2000 11:11:55 -0500 Message-Id: <200008271611.LAA07481@cypherspace.org> From: Adam Back To: mark@grondar.za Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG, jeroen@vangelderen.org In-reply-to: <200008270735.e7R7ZXp28310@grimreaper.grondar.za> (message from Mark Murray on Sun, 27 Aug 2000 09:35:32 +0200) Subject: Re: yarrow & /dev/random Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark writes: > Adam writes: > > OK, I agree that that's an area where yarrow offers better protection. > > But it's not like Ted's code is broken or anything. We would break > > things using /dev/random by switching as is to yarrow, so this is why > > I don't like it: we're trying to improve things (Yarrows protection > > aginst the attacks you describe), but in order to do this we're doing > > some other damage. We should at least do no damage: we're improving > > one thing and breaking something else. > > Again, I'm not so sure; Yarrow goes to great trouble to protect its > internal state; by blocking, I have this very nasty suspicion that > this carefully guarded state is being disclosed. The moment you block, > you are confiding in the fact that you have no updating entropy, and > as a result /dev/urandom gan be attacked to get the internal state. Are we talking Yarrow or Ts'o's algorithm? If you have no entropy, both Yarrow and Ts'o algorithm for non-blocking IO aren't going to leak the state any time soon for computationally bounded attackers -- they only release output through one way functions (SHA1 in Ts'o and counter-mode 3DES in Yarrow-160). - Yarrow-160 has it's Gate operation to ensure you don't compromise too much old output if you obtain the pool state due to host compromise. - Ts'o's algorithm does something analogous with SHA1/MD5 (depending on which version you're using), by modifying the pool when you draw output. > > One thing you can do is if your server has any private keys -- and it > > generally will have if it's doing crypto -- is mix the private key > > into the random pool along with the curren time. As the attacker > > doesn't know your private key (if he does it's game over anyway), you > > get a /dev/urandom which is secure. > > That works with what I already have: cat $privatekey > /dev/random :-) Yes. But the /dev/random device is traditionally crw-r--r-- which means user processes can't write to it. So you'd have to be root to do that. What could be done for yarrow is to change the device permissions to crw-rw-rw- and mix into a shared user source and set k_of_n_thresh so that the user can only trigger fast reseeds, and consider slow reseed de-skewing function output for blocking /dev/random; or just add user input with an entropy estimate of 0 so they can't affect reseeding, and draw fast reseed de-skewing function output for block /dev/random (slow output may be too slow). Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 8:47:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 6CB5837B423 for ; Sun, 27 Aug 2000 08:47:15 -0700 (PDT) Received: from [192.168.32.33] (helo=mx1.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13T4eA-0002px-00; Sun, 27 Aug 2000 17:46:58 +0200 Received: from p3ee1c397.dip0.t-ipconnect.de ([62.225.195.151] helo=neutron.cichlids.com) by mx1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13T4e6-0008Vd-00; Sun, 27 Aug 2000 17:46:54 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 9FEEFAB91; Sun, 27 Aug 2000 17:48:25 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 707FA14A9B; Sun, 27 Aug 2000 17:46:47 +0200 (CEST) Date: Sun, 27 Aug 2000 17:46:47 +0200 To: Seigo Tanimura Cc: Peter Jeremy , freebsd-current@FreeBSD.ORG Subject: Re: Newbusifying ed broke it Message-ID: <20000827174647.A18239@cichlids.cichlids.com> Mail-Followup-To: Seigo Tanimura , Peter Jeremy , freebsd-current@FreeBSD.ORG References: <00Aug17.111332est.115207@border.alcanet.com.au> <86wvhga6sg.wl@bunko.carrots.uucp.r.dl.itc.u-tokyo.ac.jp.nkth.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <86wvhga6sg.wl@bunko.carrots.uucp.r.dl.itc.u-tokyo.ac.jp.nkth.carrots.uucp.r.dl.itc.u-tokyo.ac.jp>; from tanimura@r.dl.itc.u-tokyo.ac.jp on Thu, Aug 17, 2000 at 12:46:39PM +0900 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Seigo Tanimura (tanimura@r.dl.itc.u-tokyo.ac.jp): > - bus_space_write_1(sc->bst, sc->bsh, regno, data); > + bus_space_write_1(rman_get_bustag(sc->port_res), rman_get_bushandle(sc->port_res), regno, data); Hmm. I used sc->bst/h to save function calls to rman_get_bus*, as many drivers use it. But obvioiusly I forgot to assign the values. I REALLY wonder why it worked for me ... strange. Thanks for fixing that. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 9:31:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id CA1EA37B422 for ; Sun, 27 Aug 2000 09:31:55 -0700 (PDT) Received: (qmail 75071 invoked by uid 1001); 27 Aug 2000 16:31:52 +0000 (GMT) To: tstromberg@rtci.com Cc: freebsd-current@freebsd.org Subject: Re: IDE RAID (HPT-370/Abit KT7-RAID) install questions.. From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 26 Aug 2000 08:47:51 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 27 Aug 2000 18:31:52 +0200 Message-ID: <75069.967393912@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BTW, these IBM 75GXP drives off of the HPT-370 are amazingly fast for > IDE. From my own measurements I'd say these drives are amazingly fast, period. They compete rather well with SCSI drives. A big thanks to sos for the HPT-370/UDMA100 support! Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 9:57:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 16FD037B422; Sun, 27 Aug 2000 09:57:56 -0700 (PDT) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id CA8074D; Sun, 27 Aug 2000 12:57:54 -0400 (AST) Message-ID: <39A94892.EB61FC4A@vangelderen.org> Date: Sun, 27 Aug 2000 12:57:54 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: Adam Back , current@FreeBSD.ORG, kris@FreeBSD.ORG Subject: Re: yarrow & /dev/random References: <200008262349.SAA06044@cypherspace.org> <200008270735.e7R7ZXp28310@grimreaper.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: [...] > Again, I'm not so sure; Yarrow goes to great trouble to protect its > internal state; by blocking, I have this very nasty suspicion that > this carefully guarded state is being disclosed. The moment you block, > you are confiding in the fact that you have no updating entropy, and > as a result /dev/urandom gan be attacked to get the internal state. You would normally assume that an attacker knows when you are not adding in entropy. In Yarrow, the assumption is that the internal state is (sufficiently) protected by both a hash and the blockcipher so blocking will not affect Yarrow's security properties AFAICS. Yes, /dev/urandom can be attacked at the point of blocking but given robust primitives the complexity is still 2^(sizeof(hash)) which is exactly the complexity Yarrow claims to provide. This is completely independent of any knowledge of reseed timings (or lack thereof). Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 10:17:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id CC28637B423; Sun, 27 Aug 2000 10:17:49 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id 8C44720F01; Sun, 27 Aug 2000 12:20:42 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id 866441D101; Sun, 27 Aug 2000 12:20:42 -0500 (CDT) Date: Sun, 27 Aug 2000 12:20:37 -0500 (CDT) From: Visigoth To: Jonathan Chen Cc: current@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: DPT revision....(broken drivers in -STABLE) In-Reply-To: <20000826180321.A1703@spock.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wonderful! Thanks everybody for the help and such... I have confirmed that this fixes the issue I was having as well. I look forward to Mike's new drivers! Laterz Visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBOak/2TnmC/+RTnGeEQK2TgCg1GnJs9NTWY+l9bPNzCdqlhBnoPkAn389 GM218rD5h0x6ED8jva6fTacV =6+Jd -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 11:47:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 3A4CF37B43E; Sun, 27 Aug 2000 11:47:38 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13T7Zv-00007c-00; Sun, 27 Aug 2000 12:54:47 -0600 Message-ID: <39A963F7.8A38871A@softweyr.com> Date: Sun, 27 Aug 2000 12:54:47 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Thomas Stromberg , freebsd-current@freebsd.org Subject: Re: IDE RAID (HPT-370/Abit KT7-RAID) install questions.. References: <200008260724.AAA00625@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > (excuse complete ignorance as far as IDE RAID below) > > > > For the buildbox here, I decided to go ahead with Soren's ATA-100 RAID > > suggestion, and bought an Abit KT7-RAID motherboard, which has an onboard > > Highpoint HPT-370 ATA-100 RAID. I'm using two 15G IBM 75GX drives on it. > > > > [...] > > > > While "lsdev" from the boot floppy shows one drive, in FreeBSD & fdisk > > they show up as two 15G drives (ad4s1 & ad6s1) rather then a 30G > > concatanated one. > > This is not an "IDE RAID" controller. It's an IDE controller with some > lame "RAID" software in the BIOS. We don't support this. Consider using vinum as an alternative. It is supported. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 12:32:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by hub.freebsd.org (Postfix) with ESMTP id B10BB37B423; Sun, 27 Aug 2000 12:32:21 -0700 (PDT) Received: from [129.250.38.62] (helo=dfw-mmp2.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7) id 13T8AG-00000i-00; Sun, 27 Aug 2000 19:32:20 +0000 Received: from [204.1.90.43] (helo=gs.verio.net) by dfw-mmp2.email.verio.net with esmtp (Exim 3.15 #4) id 13T8AG-0005h6-00; Sun, 27 Aug 2000 19:32:20 +0000 Message-ID: <39A96CC3.F47414B4@gs.verio.net> Date: Sun, 27 Aug 2000 14:32:19 -0500 From: Tony Johnson Reply-To: gjohnson@gs.verio.net Organization: Expert Solutions, L.L.C X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org, questions@freebsd.org Subject: devfs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sure you know this already, but I just want to reiterate. I have done a make world on Fridays and Saturday's Freebsd 5.0-CURRENT. I did a cvsup in the "wee" hours in the morning. I then did make world in /usr/src to rebuild the system, rebuild kernel, and mergemaster -sv. The system should be clean. Correct me if I am wrong. If I put "option DEVFS" in my kernel , build/install that kernel, my computer will not bot up completely. I will have to enter single user with an errr message stating "/dev: no such file or directory" Mounting of fstab filesystems fails. press enter for /bin/sh My /dev directory exists. Once I rebuild the kernel with no DEVFS it all works, but I like devfs as it makes all the device files that i need for my sound card as an example. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 12:35:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 89F8C37B422; Sun, 27 Aug 2000 12:35:31 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7RJZQN02015; Sun, 27 Aug 2000 21:35:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: gjohnson@gs.verio.net Cc: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: devfs In-Reply-To: Your message of "Sun, 27 Aug 2000 14:32:19 CDT." <39A96CC3.F47414B4@gs.verio.net> Date: Sun, 27 Aug 2000 21:35:26 +0200 Message-ID: <2013.967404926@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A96CC3.F47414B4@gs.verio.net>, Tony Johnson writes: >I'm sure you know this already, but I just want to reiterate. I have >done a make world on Fridays and Saturday's Freebsd 5.0-CURRENT. I did >a cvsup in the "wee" hours in the morning. I then did make world in >/usr/src to rebuild the system, rebuild kernel, and mergemaster -sv. >The system should be clean. Correct me if I am wrong. If I put "option >DEVFS" in my kernel , build/install that kernel, my computer will not >bot up completely. I will have to enter single user with an errr >message stating "/dev: no such file or directory" Mounting of fstab >filesystems fails. press enter for /bin/sh > >My /dev directory exists. Once I rebuild the kernel with no DEVFS it >all works, but I like devfs as it makes all the device files that i need >for my sound card as an example. Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init will mount devfs on /dev automatically. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 12:40:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42]) by hub.freebsd.org (Postfix) with ESMTP id 5871B37B423; Sun, 27 Aug 2000 12:40:29 -0700 (PDT) Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net) by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7) id 13T8I8-0005yE-00; Sun, 27 Aug 2000 19:40:28 +0000 Received: from [204.1.90.43] (helo=gs.verio.net) by dfw-mmp3.email.verio.net with esmtp (Exim 3.15 #4) id 13T8I8-0002pb-00; Sun, 27 Aug 2000 19:40:28 +0000 Message-ID: <39A96EAA.6E7DCFB0@gs.verio.net> Date: Sun, 27 Aug 2000 14:40:26 -0500 From: Tony Johnson Reply-To: gjohnson@gs.verio.net Organization: Expert Solutions, L.L.C X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: devfs References: <2013.967404926@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the repeat. I was playing with the sendmail 8.11.0 you guys have provided... But anyway, if DEVFS is in my fstab or not it gets mounted under /dev , as you point out. I guess this is the problem because I have to remove "options DEVFS" from my kernel in single user for my system to boot. Poul-Henning Kamp wrote: > > In message <39A96CC3.F47414B4@gs.verio.net>, Tony Johnson writes: > >I'm sure you know this already, but I just want to reiterate. I have > >done a make world on Fridays and Saturday's Freebsd 5.0-CURRENT. I did > >a cvsup in the "wee" hours in the morning. I then did make world in > >/usr/src to rebuild the system, rebuild kernel, and mergemaster -sv. > >The system should be clean. Correct me if I am wrong. If I put "option > >DEVFS" in my kernel , build/install that kernel, my computer will not > >bot up completely. I will have to enter single user with an errr > >message stating "/dev: no such file or directory" Mounting of fstab > >filesystems fails. press enter for /bin/sh > > > >My /dev directory exists. Once I rebuild the kernel with no DEVFS it > >all works, but I like devfs as it makes all the device files that i need > >for my sound card as an example. > > Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init > will mount devfs on /dev automatically. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 13: 5:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by hub.freebsd.org (Postfix) with ESMTP id D1E0037B423; Sun, 27 Aug 2000 13:05:06 -0700 (PDT) Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7) id 13T8fy-0000pQ-00; Sun, 27 Aug 2000 20:05:06 +0000 Received: from [204.1.90.43] (helo=gs.verio.net) by dfw-mmp4.email.verio.net with esmtp (Exim 3.15 #4) id 13T8fx-0003Gt-00; Sun, 27 Aug 2000 20:05:06 +0000 Message-ID: <39A97470.CEFDB6B0@gs.verio.net> Date: Sun, 27 Aug 2000 15:05:04 -0500 From: Tony Johnson Reply-To: gjohnson@gs.verio.net Organization: Expert Solutions, L.L.C X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp , current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: devfs References: <2013.967404926@critter> <39A96EAA.6E7DCFB0@gs.verio.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One last note, if this is a case for a functional union fs. I'd like to see my mistyping and the system combine things into one device directory so this type of problem will not stop my system frm booting up completely... Tony Johnson wrote: > > Sorry for the repeat. I was playing with the sendmail 8.11.0 you guys > have provided... > > But anyway, if DEVFS is in my fstab or not it gets mounted under /dev , > as you point out. I guess this is the problem because I have to remove > "options DEVFS" from my kernel in single user for my system to boot. > > Poul-Henning Kamp wrote: > > > > In message <39A96CC3.F47414B4@gs.verio.net>, Tony Johnson writes: > > >I'm sure you know this already, but I just want to reiterate. I have > > >done a make world on Fridays and Saturday's Freebsd 5.0-CURRENT. I did > > >a cvsup in the "wee" hours in the morning. I then did make world in > > >/usr/src to rebuild the system, rebuild kernel, and mergemaster -sv. > > >The system should be clean. Correct me if I am wrong. If I put "option > > >DEVFS" in my kernel , build/install that kernel, my computer will not > > >bot up completely. I will have to enter single user with an errr > > >message stating "/dev: no such file or directory" Mounting of fstab > > >filesystems fails. press enter for /bin/sh > > > > > >My /dev directory exists. Once I rebuild the kernel with no DEVFS it > > >all works, but I like devfs as it makes all the device files that i need > > >for my sound card as an example. > > > > Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init > > will mount devfs on /dev automatically. > > > > -- > > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > phk@FreeBSD.ORG | TCP/IP since RFC 956 > > FreeBSD coreteam member | BSD since 4.3-tahoe > > Never attribute to malice what can adequately be explained by incompetence. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 13:36:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 8DDFD37B422; Sun, 27 Aug 2000 13:36:36 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13T9AH-0005v1-00; Sun, 27 Aug 2000 22:36:25 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e7RKb3p29908; Sun, 27 Aug 2000 22:37:03 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200008272037.e7RKb3p29908@grimreaper.grondar.za> To: Adam Back Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG, jeroen@vangelderen.org Subject: Re: yarrow & /dev/random References: <200008271611.LAA07481@cypherspace.org> In-Reply-To: <200008271611.LAA07481@cypherspace.org> ; from Adam Back "Sun, 27 Aug 2000 11:11:55 EST." Date: Sun, 27 Aug 2000 22:37:03 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That works with what I already have: cat $privatekey > /dev/random :-) > > Yes. But the /dev/random device is traditionally crw-r--r-- which > means user processes can't write to it. So you'd have to be root to > do that. I go one further; at close, I do an explicit reseed, and I make sure that it is root doing the writing. > What could be done for yarrow is to change the device permissions to > crw-rw-rw- and mix into a shared user source and set k_of_n_thresh so > that the user can only trigger fast reseeds, and consider slow reseed > de-skewing function output for blocking /dev/random; or just add user > input with an entropy estimate of 0 so they can't affect reseeding, > and draw fast reseed de-skewing function output for block /dev/random > (slow output may be too slow). The estimate for "user" (really root) input is currently 0, except that I tie it to explicit (fast) reseeds. It shouldn't be a problem to tie it to a trickle-feed, and allow that to do fast-only reseeds after considerable lengths of time. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 14: 0:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E6E3737B423 for ; Sun, 27 Aug 2000 14:00:19 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA42069; Sun, 27 Aug 2000 21:38:24 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008271938.VAA42069@freebsd.dk> Subject: Re: IDE RAID (HPT-370/Abit KT7-RAID) install questions.. In-Reply-To: <75069.967393912@verdi.nethelp.no> from "sthaug@nethelp.no" at "Aug 27, 2000 06:31:52 pm" To: sthaug@nethelp.no Date: Sun, 27 Aug 2000 21:38:24 +0200 (CEST) Cc: tstromberg@rtci.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems sthaug@nethelp.no wrote: > > BTW, these IBM 75GXP drives off of the HPT-370 are amazingly fast for > > IDE. > > >From my own measurements I'd say these drives are amazingly fast, period. > > They compete rather well with SCSI drives. > > A big thanks to sos for the HPT-370/UDMA100 support! Well, this wouldn't have happend without Jeroen (asmodai) having good contacts at HighPoint, so I thank him for making this possible. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 14:10:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.email.msn.com (cpimssmtpu08.email.msn.com [207.46.181.30]) by hub.freebsd.org (Postfix) with ESMTP id 7162A37B422 for ; Sun, 27 Aug 2000 14:10:44 -0700 (PDT) Received: from lando - 63.15.2.126 by email.msn.com with Microsoft SMTPSVC; Sun, 27 Aug 2000 14:10:04 -0700 From: "James Johnson" To: Subject: Installkernel Date: Sun, 27 Aug 2000 14:09:19 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a little usability observation(or I am too lazy to script_my_own_tools and want to whine!) The method of building and installing a kernel to me seems a bit off.. Both the buildworld and installworld targets default to GENERIC, yet GENERIC is a file checked into the -CURRENT CVS repository.. Any changes to this file will get blown away if whenever you update the sources unless you explicity exclude this file. No one I know runs BSD with a GENERIC kernel, they have specific requirements for the hardware in their machines. Having to specify which kernel to build with the KERNEL= parameter seems to indicate that people should be running GENERIC kernels all the time as it is the default. This just doesnt seem right. I know a script could easily be written to grab a filename out of something like /boot/loader.conf to get which kernel config file you want to use by default.. Are there any plans to change this or is this method final? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 14:38:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 3B54237B422; Sun, 27 Aug 2000 14:38:01 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7RLQ3T26925; Sun, 27 Aug 2000 14:26:03 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma026923; Sun, 27 Aug 2000 14:25:56 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA66159; Sun, 27 Aug 2000 14:25:55 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008272125.OAA66159@bubba.whistle.com> Subject: Proposal to clarify mbuf handling rules To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Date: Sun, 27 Aug 2000 14:25:55 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In looking at some of the problems relating to divert, bridging, etc., it's apparent that lots of code is breaking one of the rules for handling mbufs: that mbuf data can sometimes be read-only. Each mbuf may be either a normal mbuf or a cluster mbuf (if the mbuf flags contains M_EXT). Cluster mbufs point to an entire page of memory, and this page of memory may be shared by more than one cluster mbuf (see m_copypacket()). This effectively makes the mbuf data read-only, because a change to one mbuf affects all of the mbufs, not just the one you're working on. There have been (and still are) several FreeBSD bugs because of this subtlety. A test for an mbuf being "read-only" is: if ((m->m_flags & M_EXT) != 0 && MEXT_IS_REF(m)) ... So an implicit rule for handling mbufs is that they should be treated as read-only unless/until you either check that it's not, and/or pullup a new (non-cluster) mbuf that covers the data area that you're going to modify. However, many routines that take an mbuf parameter assume that the mbuf given to them is modifiable and proceed to write all over it. A few examples are: ip_input(), in_arpinput(), tcp_input(), divert_packt(), etc. In practice, this is often not a problem because the mbuf is actually modifiable (because there are no other references to it). But this is just because we've been lucky. When you throw things like bridging, dummynet, divert, and netgraph into the mix, not to mention other site-specific hacks, then these assumptions no longer hold. At the minimum these assumptions should be clearly commented, but that's not even the case right now. Routines that don't change any data, or that only do m_pullup(), M_PREPEND(), m_adj(), etc. don't have a problem. So I'd like to propose a mini-project to clarify and fix this problem. Here is the propsal: 1. All routines that take an mbuf as an argument must not assume that any mbuf in the chain is modifyable, unless expclicitly and clearly documented (in the comment at the top of the function) as doing so. 2. For routines that don't modify data, incorporate liberal use of the "const" keyword to make this clear. For example, change struct ip *ip; ip = mtod(m, struct ip *); to: const struct ip *ip; ip = mtod(m, const struct ip *); 3. For any routines that do need to modify mbuf data, but don't assume anything about the mbuf, alter those routines to do an m_pullup() when necessary to make the data are they are working on modifiable. For example: struct ip *ip; /* Pull up IP header */ if (m->m_len < sizeof(*ip) && !(m = m_pullup(m, sizeof(*ip)))) return; ip = mtod(m, struct ip *); #ifdef NEW_CODE_BEING_ADDED /* Make sure the IP header area is writable */ if ((m->m_flags & M_EXT) != 0 && MEXT_IS_REF(m)) { /* m_pullup() *always* prepends a fresh, non-cluster mbuf */ if ((m = m_pullup(m, sizeof(struct ip))) == 0) return; ip = mtod(m, struct ip *); } #endif /* Modify the header */ ip->ip_len = 123; ... The only negative is the addition of the NEW_CODE_BEING_ADDED code in the relevant places. In practice this test will usually fail, as most mbufs are modifiable, so there should be no noticable slowdown. However, robustness should improve, especially when bridging, diverting, etc. What do people think? If this is generally agreeable I'll try to work on putting together a patch set for review. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 14:50:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4BF1337B423; Sun, 27 Aug 2000 14:50:12 -0700 (PDT) Received: from lanczos.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Aug 2000 22:50:11 +0100 (BST) Date: Sun, 27 Aug 2000 22:50:11 +0100 From: David Malone To: Archie Cobbs Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: Proposal to clarify mbuf handling rules Message-ID: <20000827225011.A10714@lanczos.maths.tcd.ie> References: <200008272125.OAA66159@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008272125.OAA66159@bubba.whistle.com>; from archie@whistle.com on Sun, Aug 27, 2000 at 02:25:55PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 27, 2000 at 02:25:55PM -0700, Archie Cobbs wrote: > What do people think? If this is generally agreeable I'll try to > work on putting together a patch set for review. Myself and Ian Dowse have been talking about almost this issue recently in relation to sbcompress. At the moment sbcompress is too conservative about compressing mbuf chains, with the result that it is easily possible to run many machines out of mbuf clusters. (We've seen this problem with netscape and kioslave). At the moment sbcompress only compresses into mbufs, where it could also compress into clusters, providing they have a reference count of 1. However, this still means it can't compress into jumbo buffers associated with gigabit ethernet and the like. We were thinking it might be a good idea to have a flag associated with mbufs which means they are writable, providing the reference count is 1. Then we can provide a macro for checking writability. This flag could be set on jumbo ethernet buffers, but not sendfile buffers (for example). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 15:10:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 56BBF37B424; Sun, 27 Aug 2000 15:09:59 -0700 (PDT) Received: from lanczos.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Aug 2000 23:09:58 +0100 (BST) Date: Sun, 27 Aug 2000 23:09:58 +0100 From: David Malone To: Archie Cobbs Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: Proposal to clarify mbuf handling rules Message-ID: <20000827230958.B10714@lanczos.maths.tcd.ie> References: <200008272125.OAA66159@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008272125.OAA66159@bubba.whistle.com>; from archie@whistle.com on Sun, Aug 27, 2000 at 02:25:55PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 27, 2000 at 02:25:55PM -0700, Archie Cobbs wrote: > Each mbuf may be either a normal mbuf or a cluster mbuf (if the > mbuf flags contains M_EXT). Cluster mbufs point to an entire page > of memory, and this page of memory may be shared by more than one > cluster mbuf (see m_copypacket()). Clusters are currently 2048 bytes in size - which I don't think it a page on the alpha or the i386. (Not that this is really important). > his effectively makes the mbuf > data read-only, because a change to one mbuf affects all of the > mbufs, not just the one you're working on. There have been (and > still are) several FreeBSD bugs because of this subtlety. > > A test for an mbuf being "read-only" is: > > if ((m->m_flags & M_EXT) != 0 && MEXT_IS_REF(m)) ... You should also check that it's really a cluster you're looking at: if ((m->m_flags & M_EXT) != 0 && (MEXT_IS_REF(m) || (m)->m_ext.ext_free != NULL)) { /* data is read only */ } (This is why the flag I was talking about in the other mail would be useful for spotting other cases where the storage may be writable, even if it's not a cluster). Cleaning up this sounds like a good plan. It would be worth getting Ian and Bosko involved if possible. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 15:59:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76]) by hub.freebsd.org (Postfix) with SMTP id 05F4237B423; Sun, 27 Aug 2000 15:59:33 -0700 (PDT) Received: by tsx-prime.MIT.EDU with sendmail-SMI-8.6/1.2, id SAA02131; Sun, 27 Aug 2000 18:59:20 -0400 Date: Sun, 27 Aug 2000 18:59:20 -0400 Message-Id: <200008272259.SAA02131@tsx-prime.MIT.EDU> From: "Theodore Y. Ts'o" To: Adam Back Cc: mark@grondar.za, current@FreeBSD.ORG, kris@FreeBSD.ORG, jeroen@vangelderen.org, yarrow@zeroknowledge.com Subject: Re: yarrow & /dev/random Phone: (781) 391-3464 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adam writes: >Yes. But the /dev/random device is traditionally crw-r--r-- which >means user processes can't write to it. So you'd have to be root to >do that. > >What could be done for yarrow is to change the device permissions to >crw-rw-rw- and mix into a shared user source and set k_of_n_thresh so >that the user can only trigger fast reseeds, and consider slow reseed >de-skewing function output for blocking /dev/random; or just add user >input with an entropy estimate of 0 so they can't affect reseeding, >and draw fast reseed de-skewing function output for block /dev/random >(slow output may be too slow). I'm not on the freebsd.org lists, so I've missed some of the discussion on this threads; I was pointed to the web archives by Adam. A couple of comments here. It was always the intention that /dev/random be 0666, and in my implementation, writing to /dev/random mixed the input into the entropy pool *without* changing the entropy estimate. The mixing algorithm was carefully chosen so that even if an attacker mixed all zero's, or some other carefully chosen input, he/she would gain no more information about the pool than he/she already had (which hopefully is non, of course. :-) I used an ioctl which atomically adds data into the entropy pool *and* updates the entropy count. I did this because (a) the (trusted, privileged) user-mode random collection daemon has the best idea of how much entropy the input data has, and (b) if someone is actively drawing on the entropy pool, you want to update the entropy count at exactly the same time as you add the entropy to the entropy pool. As far as yarrow versus the current design, I've certainly looked at yarrow, and I've certainly considered adding some of yarrow's design into my /dev/random implementation. Given that I strongly recommend that the 512 bytes of entropy be saved from /dev/random at shutdown time, and then written to /dev/random at startup time (without updating the entropy estimate), I question how realistic the attack scenario that Yarrow tries so hard to defend against. The other problem I have against the Yarrow design is that it depends on the strength of the crypto primitives a bit more than I feel comfortable doing. In my /dev/random design, which draws heavily from the philosophy of PGP's RNG, we use a crypto primitive for whitening, but as long as there is a sufficient amount of system entropy getting poured into the pool, the crypto primitive could be replaced with a CRC function (or even an additive checksum!) without really doing a lot of damage to system security. I also feel very strongly that something like 3DES/AES counter mode is something which a crypto application which needs a lot of session keys should be implemented in user-mode ---- in a library, probably. There's no real reason why that needs to be implemented in the kernel --- /dev/random needs to be there because it's doing all of the sampling of the system environment, and the entropy pool needs to be stored securely and easily updated by the entropy collection routines. So it may be that the best way to handle things is to implement the upper level of a yarrow-like design in a usermode library, and which does its "catastrophic reseeding" by reading from /dev/random as necessary. Certainly that is my bias at this point. - Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 16:18:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 8B94237B424 for ; Sun, 27 Aug 2000 16:18:10 -0700 (PDT) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id SAA10872; Sun, 27 Aug 2000 18:18:08 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <001c01c0107d$0fcca480$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "James Johnson" , References: Subject: Re: Installkernel Date: Sun, 27 Aug 2000 18:18:07 -0500 Organization: West Bend Internet X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "James Johnson" > The method of building and installing a kernel to me seems a bit off.. Both > the buildworld and installworld targets default to GENERIC, yet GENERIC is a > file checked into the -CURRENT CVS repository.. Any changes to this file > will get blown away if whenever you update the sources unless you explicity Your supposed to copy GENERIC to a new name, and then build your kernel with that file. You can change the default kernel to build by specifying: KERNEL= MY-KERNEL in the /etc/make.conf file. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 16:23:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8DB4F37B43E; Sun, 27 Aug 2000 16:23:38 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA22613; Sun, 27 Aug 2000 16:23:37 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA32732; Sun, 27 Aug 2000 16:23:37 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 27 Aug 2000 16:23:37 -0700 (PDT) Message-Id: <200008272323.QAA32732@vashon.polstra.com> To: current@FreeBSD.ORG Cc: green@FreeBSD.ORG Subject: Re: panic: reducing sbsize: lost count, uid = 1001 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian Fundakowski Feldman wrote: > If this is a problem with sbsize, this should take care of any possibility > ever of there being a problem... I tried your patch, but it panics reliably on start-up: Automatic boot in progress... /dev/da0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1a: clean, 335363 free (8667 frags, 40837 blocks, 1.1% fragmentation) /dev/da0s1e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1e: clean, 1966150 free (46222 frags, 239991 blocks, 1.0% fragmentation) Doing initial network setup: hostname. panic: reducing sbsize: lost count, uid = 0 Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.390 db> trace Debugger(c0280363) at Debugger+0x34 panic(c027fc80,0,2400,0,c7c20f74) at panic+0x70 chgsbsize(0,c7c20f78,2400,ffffffff,7fffffff) at chgsbsize+0x33 sbreserve(c7c20f74,2400,c7c20f00,c77ee440) at sbreserve+0x6a soreserve(c7c20f00,2400,a280,c7c20f00,c02bb368) at soreserve+0x1c udp_attach(c7c20f00,0,c77ee440,0,c86f6f80) at udp_attach+0x2a socreate(2,c86f6f20,2,0,c77ee440) at socreate+0xe8 socket(c77ee440,c86f6f80,8085098,bfbffda0,3) at socket+0x3e syscall2(2f,2f,2f,3,bfbffda0) at syscall2+0x1f1 Xint0x80_syscall() at Xint0x80_syscall+0x25 The value of *hiwat in chgsbsize() is 0: db> x/ul 0xc7c20f78 0xc7c20f78: 0 I can't get it to generate a core dump that it will recognize on reboot, and I'm not set up for remote gdb on this machine. But I can check anything you'd like with ddb. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 16:38: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 922EE37B43C; Sun, 27 Aug 2000 16:38:02 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA20412; Sun, 27 Aug 2000 16:38:02 -0700 Date: Sun, 27 Aug 2000 16:34:27 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: phk@freebsd.org Cc: current@freebsd.org Subject: alpha devfs feedback Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3 'da' disks that were found. The only real problem is that it won't see the partitions made for 'dangerously dedicated' 'da' disks. What's the plan for addressing this? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 17: 6:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 88F9637B424 for ; Sun, 27 Aug 2000 17:06:23 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13TBOv-000Puo-00; Sun, 27 Aug 2000 23:59:41 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id XAA12594; Sun, 27 Aug 2000 23:59:41 +0100 (BST) (envelope-from ben) Date: Sun, 27 Aug 2000 23:59:40 +0100 From: Ben Smithurst To: James Johnson Cc: freebsd-current@freebsd.org Subject: Re: Installkernel Message-ID: <20000827235940.N64260@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Johnson wrote: > Having to specify > which kernel to build with the KERNEL= parameter seems to indicate that > people should be running GENERIC kernels all the time as it is the default. No, it seems to indicate that you should specify KERNEL=YOURKERNEL in make.conf. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 17: 8:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 4FEC037B423 for ; Sun, 27 Aug 2000 17:08:30 -0700 (PDT) Received: from pacbell.net ([63.199.30.65]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FZZ009LN6Z5FA@mta6.snfc21.pbi.net> for current@freebsd.org; Sun, 27 Aug 2000 17:06:42 -0700 (PDT) Date: Sun, 27 Aug 2000 17:07:18 -0700 From: "George W. Dinolt" Subject: Linux ABI no longer supports staroffice To: Marcel Moolenaar Cc: current@freebsd.org Message-id: <39A9AD36.D3CAECDA@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel: Up until this weekend, I was able to use the staroffice52 port with little problem (I had installed it earlier without benefit of the port and it worked fine.) I did a 5.0-current kernel rebuild on Thursday with sources current on that day and things were fine. When I rebuilt my kernel yesterday afternoon with sources from Saturday morning, the port stopped working. I get the following error messages I18N: X Window System doesn't support locale "C" _X11TransSocketOpen: socket() failed for local _X11TransSocketOpenCOTSClient: Unable to open socket for local _X11TransOpen: transport open failed for local/dinolt1.bingdrive:0 setup.bin: cannot open display ":0.0" Please check your "DISPLAY" environment variable, as well as the permissions to access that display (See "man X" resp. "man xhost" for details) I am running the install as root. The Window Manager is up and running, other programs including linux-netscape have no trouble running in the same environment. This is not a clue for me, but it may mean something to others. (By the way, these errors did not appear prior to the changes.) I was wondering whether the setrlimit changes had something to do with this. This seems to be the major change to the linux code in the last few days. Apparently you were the one to make those changes, so I am writing to you (Marcel) Anyway, thought someone should know. George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 17:17:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3F23B37B424; Sun, 27 Aug 2000 17:17:50 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA21141; Sun, 27 Aug 2000 20:17:48 -0400 (EDT) (envelope-from wollman) Date: Sun, 27 Aug 2000 20:17:48 -0400 (EDT) From: Garrett Wollman Message-Id: <200008280017.UAA21141@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: freebsd-net@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Proposal to clarify mbuf handling rules In-Reply-To: <200008272125.OAA66159@bubba.whistle.com> References: <200008272125.OAA66159@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > However, many routines that take an mbuf parameter assume that the > mbuf given to them is modifiable and proceed to write all over it. s/assume/require as a necessary precondition/ It's not a coding error, it's part of the specification. No, it's not documented -- but it's pretty clear from the design of the original code. > 3. For any routines that do need to modify mbuf data, but don't > assume anything about the mbuf, alter those routines to do > an m_pullup() when necessary to make the data are they are > working on modifiable. m_pullup is evil. It would be better to fix the places (i.e., ip_input and ip_output) which make the modification necessary. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 17:24:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id C35C037B424 for ; Sun, 27 Aug 2000 17:24:09 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 0817C23D1; Sun, 27 Aug 2000 17:24:09 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id RAA26745; Sun, 27 Aug 2000 17:24:08 -0700 (PDT) Message-ID: <39A9B127.42C609B3@cup.hp.com> Date: Sun, 27 Aug 2000 17:24:07 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "George W. Dinolt" Cc: current@freebsd.org Subject: Re: Linux ABI no longer supports staroffice References: <39A9AD36.D3CAECDA@pacbell.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "George W. Dinolt" wrote: > > I was wondering whether the setrlimit changes had something to do with > this. This seems to be the major change to the linux code in the last > few days. Apparently you were the one to make those changes, so I am > writing to you (Marcel) Can you track down which change caused the failure. I haven't experienced any problems so far. I'll try running SO myself in the mean time. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 18:30:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id C625237B423 for ; Sun, 27 Aug 2000 18:30:31 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id SAA42115; Sun, 27 Aug 2000 18:29:39 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008280129.SAA42115@pike.osd.bsdi.com> Subject: Re: 5.0-current 20000826 snapshot problems In-Reply-To: <200008271355.IAA01923@mppsystems.com> from Mike Pritchard at "Aug 27, 2000 08:55:24 am" To: Mike Pritchard Date: Sun, 27 Aug 2000 18:29:39 -0700 (PDT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Pritchard wrote: > I just had a problem trying to install the latest -current > snapshot from the 8/26 snap. Background: > > Windows trashed my hard disk on one of my machines, so I had > to do clean install. Since I run -current on that machine > anyways, I decided to try the latest snapshot to restore it. > > Booting kern.flp (i386) gives me (pardon any typos, I'm looking at > one screen and typing on the other): > > FreeBSD/i386 bootstrap loader, Revision 0.8 > (root@usw2.freebsd.org, Sat Aug 26 11:14:35 GMT 2000) > /kernel text=0x2432ca zf_read: fill error > > elf_loadexec: archsw.readin failed Your floppy is bad. Try a different one. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 18:30:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherspace.org (modemcable228.178-201-24.mtl.mc.videotron.net [24.201.178.228]) by hub.freebsd.org (Postfix) with ESMTP id 8783737B43F; Sun, 27 Aug 2000 18:30:37 -0700 (PDT) Received: (from adam@localhost) by cypherspace.org (8.8.3/8.6.12) id VAA01008; Sun, 27 Aug 2000 21:32:38 -0500 Date: Sun, 27 Aug 2000 21:32:38 -0500 Message-Id: <200008280232.VAA01008@cypherspace.org> From: Adam Back To: tytso@MIT.EDU Cc: mark@grondar.za, current@FreeBSD.ORG, kris@FreeBSD.ORG, jeroen@vangelderen.org, yarrow@zeroknowledge.com In-reply-to: <200008272259.SAA02131@tsx-prime.MIT.EDU> (tytso@MIT.EDU) Subject: /dev/random device permissions (Re: yarrow & /dev/random) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted writes: > A couple of comments here. It was always the intention that > /dev/random be 0666, and in my implementation, writing to > /dev/random mixed the input into the entropy pool *without* changing > the entropy estimate. I see. This is not clear. We recently set it /dev/random to group writeable for a server application so we could write into /dev/random without being root. I'll change that to 0666. I think the confusion may come from a misunderstanding about the access control mechanism on the ioctls. (I tried 0666 just now and called the ioctl to zero the pool as a user and it denies access based on not being root -- so 0666 is in fact safe). Everyone seems to be setting it to 0644. Default linux Redhat, Slackware, freeBSD etc., etc is 0644. This is wrong, and as a result applications which really could benefit /dev/random by writing (private keys, encrypted IVs, user passwords, etc) aren't doing it. These tricks can really help mitigate lack of input device entropy in server environments. Given the importance of this, we ought to draw this to the attention of distribution maintainers and get it fixed. Bugtraq may be a good way to get the word out? The rest of Ted's comments about Yarrow and /dev/random design are interesting -- next mail. Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 18:40:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 3D3C637B423 for ; Sun, 27 Aug 2000 18:40:50 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e7S1ebY22983; Sun, 27 Aug 2000 18:40:37 -0700 Date: Sun, 27 Aug 2000 18:40:37 -0700 From: Brooks Davis To: Motomichi Matsuzaki Cc: current@FreeBSD.ORG Subject: Re: hints static wiring Message-ID: <20000827184037.A22500@Odin.AC.HMC.Edu> References: <867l92lw8e.wl@tkc.att.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <867l92lw8e.wl@tkc.att.ne.jp>; from mzaki@e-mail.ne.jp on Sun, Aug 27, 2000 at 09:33:21PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote: > > When kernel is built with static device wiring > (i.e. 'hints' line is enabled in the config file), > is /boot/device.hints required? > > Doing 'make install' without /boot/device.hints is failed, > saying "You must set up a /boot/device.hints file first." > Is this right? You should read cvs-all. There was a commit by Peter which forces you to install a /boot/device.hints file to install a kernel as an anti-foot shooting measure. An empty file (ie touch /boot/device.hints) is acceptable for those who don't want to use a hints file. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 19:21:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherspace.org (modemcable228.178-201-24.mtl.mc.videotron.net [24.201.178.228]) by hub.freebsd.org (Postfix) with ESMTP id 6622A37B43F; Sun, 27 Aug 2000 19:21:31 -0700 (PDT) Received: (from adam@localhost) by cypherspace.org (8.8.3/8.6.12) id WAA01579; Sun, 27 Aug 2000 22:23:33 -0500 Date: Sun, 27 Aug 2000 22:23:33 -0500 Message-Id: <200008280323.WAA01579@cypherspace.org> From: Adam Back To: tytso@MIT.EDU Cc: mark@grondar.za, current@FreeBSD.ORG, kris@FreeBSD.ORG, jeroen@vangelderen.org, yarrow@zeroknowledge.com In-reply-to: <200008272259.SAA02131@tsx-prime.MIT.EDU> (tytso@MIT.EDU) Subject: merits of the iterative guessing attack (Re: yarrow & /dev/random) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted writes: > [...] > > As far as yarrow versus the current design, I've certainly looked at > yarrow, and I've certainly considered adding some of yarrow's design > into my /dev/random implementation. Given that I strongly recommend > that the 512 bytes of entropy be saved from /dev/random at shutdown > time, and then written to /dev/random at startup time (without updating > the entropy estimate), I question how realistic the attack scenario that > Yarrow tries so hard to defend against. This would be the "iterative guessing attack" the yarrow authors design against to recover from state compromise. One argument against the realism of the iterative guessing attack might be you need root to obtain the state, and that if you have root you can easily change other things to maintain ability to predict crypto keys. Say like linking /dev/[u]random to /dev/zero, or something marginally more subtle, or modifying target binaries, or grabbing the target servers private key from /dev/keymem. However probably just grabbing the pool state with ioctl RNDGETPOOL and then getting out may be less likely to trigger alarms. Arguments in favor of the attempts to recover from state compromise: - The bootstrap problem -- where did /dev/random get it's start state from before there was a seed file to load; all the entropy samples went in small chunks, and if the machine was outputting randomness the whole time, the attacker may be able to maintain the "iterative guessing attack" right from install time. - Situations where the server has no writeable media to store it's /var/run/seed -- boot of CD or harddisk mounted read only plus /var mounting on a ram disk. In this scenario the attacker gets to mount - Distributions which don't include the shutdown and startup state save and restore. (I've got an old slackware installation at home with /dev/random, but no state saving and loading in /etc/rc.d/*). - Default wrong permissions on /dev/[u]random -- discards any user entropy (primarily an argument to persuade people to fix the permissions). If we buy these arguments, then Yarrow's conservative recovery strategies are a good idea. > I also feel very strongly that something like 3DES/AES counter mode is > something which a crypto application which needs a lot of session keys > should be implemented in user-mode ---- in a library, probably. There's > no real reason why that needs to be implemented in the kernel --- > /dev/random needs to be there because it's doing all of the sampling of > the system environment, and the entropy pool needs to be stored securely > and easily updated by the entropy collection routines. > > So it may be that the best way to handle things is to implement the > upper level of a yarrow-like design in a usermode library, and which > does its "catastrophic reseeding" by reading from /dev/random as > necessary. Certainly that is my bias at this point. It's certainly preferable to keep the line count in the kernel down. Yarrow is quite complex. However, unprivileged users can do DoS attacks against /dev/random -- cat /dev/random > /dev/null. This and the risk of server stall where there is no input device means many people avoid /dev/random for servers and use /dev/urandom. And use /dev/random just for long term private key generation. To use /dev/random as a source of state compromise recovery for a user land yarrow, you'd want a way to be able to use non-blocking IO to atomically read some chunk of bits (100 for fast and 160 for slow reseeds with Yarrow-160) from /dev/random otherwise you'd still be vulnerable to iterative guessing attacks based on other /dev/urandom processes outputs. Looking at the /dev/random code, I think you'll get a short read if not enough bits are available. A more integrated yarrow can avoid the risk of DoS attack preventing state compromise recovery by reserving some of the /dev/random output for state compromise recovery and leaving the rest for /dev/random users. Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 19:21:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 25BA837B43C for ; Sun, 27 Aug 2000 19:21:30 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 2A5091E48; Sun, 27 Aug 2000 19:21:26 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id TAA28440; Sun, 27 Aug 2000 19:21:22 -0700 (PDT) Message-ID: <39A9CC9F.5ED2A6E4@cup.hp.com> Date: Sun, 27 Aug 2000 19:21:19 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sean-Paul Rees Cc: current@FreeBSD.org, gdinolt@pacbell.net Subject: Broken definition for {g|s}etrlimit References: <39A9AD36.D3CAECDA@pacbell.net> <39A9B127.42C609B3@cup.hp.com> <20000827172728.A80939@seanrees.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean-Paul Rees wrote: > > On Sun, Aug 27, 2000 at 05:24:07PM -0700, Marcel Moolenaar wrote: > > "George W. Dinolt" wrote: > > > > > > I was wondering whether the setrlimit changes had something to do with > > > this. This seems to be the major change to the linux code in the last > > > few days. Apparently you were the one to make those changes, so I am > > > writing to you (Marcel) > > > > Can you track down which change caused the failure. I haven't > > experienced any problems so far. I'll try running SO myself in the mean > > time. > > I'm also running -current, however, StarOffice will barely even run! It seems > that all the Linux apps on -current run at about 1/10th their speed. It was > unbearable (and also unusable). > > This has been happening to me for the last few builds of -current. Maybe I'm > doing something wrong or need to reinstall something. Can you offer any > pointers? It seems that the recent change to {g|s}etrlimit hit upon a bug in the FreeBSD syscall definition. Can you tell me if the following patch solves the problem? (don't forget to run 'make sysent.c' in /sys/kern before running config) Index: syscalls.master =================================================================== RCS file: /home/ncvs/src/sys/kern/syscalls.master,v retrieving revision 1.81 diff -u -r1.81 syscalls.master --- syscalls.master 2000/07/29 10:05:23 1.81 +++ syscalls.master 2000/08/28 01:48:38 @@ -223,8 +223,8 @@ 141 COMPAT BSD { int getpeername(int fdes, caddr_t asa, int *alen); } 142 COMPAT BSD { long gethostid(void); } 143 COMPAT BSD { int sethostid(long hostid); } -144 COMPAT BSD { int getrlimit(u_int which, struct ogetrlimit *rlp); } -145 COMPAT BSD { int setrlimit(u_int which, struct ogetrlimit *rlp); } +144 COMPAT BSD { int getrlimit(u_int which, struct orlimit *rlp); } +145 COMPAT BSD { int setrlimit(u_int which, struct orlimit *rlp); } 146 COMPAT BSD { int killpg(int pgid, int signum); } 147 STD POSIX { int setsid(void); } 148 STD BSD { int quotactl(char *path, int cmd, int uid, \ @@ -294,10 +294,10 @@ 192 STD POSIX { int fpathconf(int fd, int name); } 193 UNIMPL NOHIDE nosys 194 STD BSD { int getrlimit(u_int which, \ - struct orlimit *rlp); } \ + struct rlimit *rlp); } \ getrlimit __getrlimit_args int 195 STD BSD { int setrlimit(u_int which, \ - struct orlimit *rlp); } \ + struct rlimit *rlp); } \ setrlimit __setrlimit_args int 196 STD BSD { int getdirentries(int fd, char *buf, u_int count, \ long *basep); } -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 19:28:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [64.50.162.3]) by hub.freebsd.org (Postfix) with SMTP id 0745437B43C for ; Sun, 27 Aug 2000 19:28:40 -0700 (PDT) Received: (qmail 33062 invoked by uid 1000); 28 Aug 2000 02:28:34 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Aug 2000 02:28:34 -0000 Date: Sun, 27 Aug 2000 22:28:34 -0400 (EDT) From: Systems Administrator To: questions@freebsd.org Cc: current@freebsd.org Subject: Monitor dies and doesn't come back. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having a strange problem recently after installing a new harddrive.. the harddrive works fine in other OS's, but in FreeBSD, (seemingly after the HD install), the Monitor (CTX VL19") goes into powersaving and you cant get it back without doing a cold reboot.. not even a warm reboot will work. I am not sure exactly what is happening here, perhaps something borked? I have a Western Digital Caviar 45GB drive running at UDMA33. dmesg output follows: FreeBSD 5.0-CURRENT #1: Sat Aug 26 00:24:22 MDT 2000 geniusj@phreebsd.org:/usr2/src/sys/compile/FREEBSD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 501138733 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 134217728 (131072K bytes) avail memory = 127107072 (124128K bytes) Preloaded elf kernel "kernel" at 0xc037e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc037e09c. Preloaded elf module "splash_bmp.ko" at 0xc037e0ec. Preloaded elf module "vesa.ko" at 0xc037e190. Preloaded splash_image_data "/boot/splash.bmp" at 0xc037e22c. Preloaded elf module "snd_emu10k1.ko" at 0xc037e27c. Preloaded elf module "snd_pcm.ko" at 0xc037e320. Pentium Pro MTRR support enabled VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc02f43b7 (1000117) VESA: 3dfx Interactive, Inc. npx0: on motherboard pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 5 pci0: at 7.3 pcm0: port 0xe400-0xe41f irq 10 at device 13.0 on pci0 pci0: <3Dfx Voodoo 3 graphics accelerator> at 15.0 irq 11 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ed0 at port 0x240-0x25f iomem 0xd8000-0xd9fff irq 3 on isa0 ed0: address 00:e0:29:16:cb:72, type SMC8416T (16 bit) sc1: on isa0 sc1: MDA <16 virtual consoles, flags=0x0> vga1: at port 0x3b0-0x3bb iomem 0xb0000-0xb7fff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 acd0: CD-RW at ata1-master using WDMA2 acd1: CDROM at ata1-slave using PIO3 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted Any help would be appreciated. Thanks! (Sorry, no panic, so that's all I could get) -JD- ---- Jason DiCioccio - IBM Global Services - djason@us.ibm.com - www.ibm.com Systems Admin - Open Domain Server - geniusj@ods.org - www.ods.org FreeBSD - The Power to Serve - - www.freebsd.org ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 19:37:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id B935637B422 for ; Sun, 27 Aug 2000 19:37:27 -0700 (PDT) Received: from zippy.pacbell.net ([207.214.149.131]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FZZ000WCDVDO2@mta5.snfc21.pbi.net> for current@freebsd.org; Sun, 27 Aug 2000 19:35:38 -0700 (PDT) Received: by zippy.pacbell.net (Postfix, from userid 1000) id 487E7179E; Mon, 28 Aug 2000 19:36:05 +0000 (GMT) Date: Mon, 28 Aug 2000 19:36:05 +0000 From: Alex Zepeda Subject: SMP and softupdates? To: current@freebsd.org Message-id: <20000828193605.A290@zippy> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In upgrading my system I've bought a shiny new SMP mobo to go with my new 30gb Deskstar... The nice thing about this new board is my HighPoint HPT366 based IDE controller works now (Buggy Phoenix BIOSes prevented it from working before). Perhaps in a rush to get started, I've compiled and been using a SMP kernel even before the second processor arrives. This has worked fine, however I've gotten some rather weird hangs and crashes resulting in a nice lost+found directory on the usr fs. In trying to track this down, I've tried a UP kernel which seems to not have crashed where the SMP one did before.. I'm sure it's not a cooling issue as the sole CPU is staying below 35C. However I'm curious: * Are there any known issues with SMP and softupdates as of late? * Is running one processor with an SMP kernel such a horrible idea (other than performance wise)? I'm glad I can run my harddrives (Caviar and Deskstar) at ATA66 speeds.. but having to tread lightly is sucking. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 19:41:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 0E6DC37B42C for ; Sun, 27 Aug 2000 19:41:45 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id MAA61574; Mon, 28 Aug 2000 12:11:31 +0930 (CST) (envelope-from grog) Date: Mon, 28 Aug 2000 12:11:30 +0930 From: Greg Lehey To: Systems Administrator Cc: current@FreeBSD.ORG Subject: Re: Monitor dies and doesn't come back. Message-ID: <20000828121130.J38394@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from geniusj@ods.org on Sun, Aug 27, 2000 at 10:28:34PM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [dropping -questions, this is a -CURRENT problem] On Sunday, 27 August 2000 at 22:28:34 -0400, Systems Administrator wrote: > I've been having a strange problem recently after installing a new > harddrive.. the harddrive works fine in other OS's, but in FreeBSD, > (seemingly after the HD install), the Monitor (CTX VL19") goes into > powersaving and you cant get it back without doing a cold reboot.. not > even a warm reboot will work. I am not sure exactly what is happening > here, perhaps something borked? I have a Western Digital Caviar 45GB drive > running at UDMA33. Well, this isn't the monitor, of course. Your system is probably dying a horrible death and not producing any video output. > ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > acd0: CD-RW at ata1-master using WDMA2 > acd1: CDROM at ata1-slave using PIO3 > Mounting root from ufs:/dev/ad0s1a > WARNING: / was not properly dismounted Well, it's not a good idea to put both disks on the same controller anyway. What happens if you put the disks on the primaries of each controller, and the CD-ROMS on the secondaries? If that doesn't help, does the system at least work without the 45 GB drive? Anyway, how far do you get in the book process? Can you get into single user mode the way you are now? Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 19:43:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 6A05C37B422; Sun, 27 Aug 2000 19:43:22 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7S2hC928224; Sun, 27 Aug 2000 19:43:12 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma028222; Sun, 27 Aug 2000 19:42:49 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id TAA66974; Sun, 27 Aug 2000 19:42:48 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008280242.TAA66974@bubba.whistle.com> Subject: Re: Proposal to clarify mbuf handling rules In-Reply-To: <20000827225011.A10714@lanczos.maths.tcd.ie> "from David Malone at Aug 27, 2000 10:50:11 pm" To: David Malone Date: Sun, 27 Aug 2000 19:42:48 -0700 (PDT) Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone writes: > We were thinking it might be a good idea to have a flag associated > with mbufs which means they are writable, providing the reference > count is 1. Then we can provide a macro for checking writability. > This flag could be set on jumbo ethernet buffers, but not sendfile > buffers (for example). That's a good idea.. I forgot about things like sendfile, where the mbuf is read-only due to other reasons. So we need some kind of flag it seems. That's good -- it makes it even more obvious. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 20:16:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f221.law4.hotmail.com [216.33.149.221]) by hub.freebsd.org (Postfix) with ESMTP id CFF2537B423 for ; Sun, 27 Aug 2000 20:16:17 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 27 Aug 2000 20:16:17 -0700 Received: from 24.131.146.82 by lw4fd.law4.hotmail.msn.com with HTTP; Mon, 28 Aug 2000 03:16:17 GMT X-Originating-IP: [24.131.146.82] From: "Michael Sabino" To: freebsd-current@freebsd.org Subject: subscribe Date: Mon, 28 Aug 2000 03:16:17 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 28 Aug 2000 03:16:17.0638 (UTC) FILETIME=[54963060:01C0109E] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 20:24:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CCAAF37B423; Sun, 27 Aug 2000 20:24:06 -0700 (PDT) Date: Sun, 27 Aug 2000 23:24:05 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: panic: reducing sbsize: lost count, uid = 1001 In-Reply-To: <200008272323.QAA32732@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Aug 2000, John Polstra wrote: > In article , > Brian Fundakowski Feldman wrote: > > If this is a problem with sbsize, this should take care of any possibility > > ever of there being a problem... > > I tried your patch, but it panics reliably on start-up: Woops, I have the KASSERT bungled up. Please change KASSERT(to < *hiwat && uip != NULL, to KASSERT(to >= *hiwat || uip != NULL, -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 21:40: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id 3EA6537B424 for ; Sun, 27 Aug 2000 21:40:01 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 27 Aug 2000 23:37:57 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e7S4Z9V35618 for ; Sun, 27 Aug 2000 23:35:13 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e7S4Z2V16515 for ; Sun, 27 Aug 2000 23:35:03 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200008280435.e7S4Z2V16515@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: hintmode not found. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Aug 2000 23:35:02 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone stashed a refewrence to an extern int hintmode in /sys/kern/subr_bus.c a couple of days ago - where's it actually defined? Mr Grep cant seem to find in /sys. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 27 22:33: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ego.mind.net (ego.mind.net [206.99.66.9]) by hub.freebsd.org (Postfix) with ESMTP id CB0E437B422 for ; Sun, 27 Aug 2000 22:33:00 -0700 (PDT) Received: from takhus-home.ashlandfn.org (AFN-Dynamic-22081.ashlandfiber.net [208.46.220.81] (may be forged)) by ego.mind.net (8.9.3/8.9.3) with ESMTP id WAA05576 for ; Sun, 27 Aug 2000 22:32:59 -0700 Received: from localhost (fleisher@localhost) by takhus-home.ashlandfn.org (8.11.0/8.11.0) with ESMTP id e7S5WwJ00746 for ; Sun, 27 Aug 2000 22:32:58 -0700 (PDT) (envelope-from takhus@takhus.mind.net) X-Authentication-Warning: takhus-home.ashlandfn.org: fleisher owned process doing -bs Date: Sun, 27 Aug 2000 22:32:58 -0700 (PDT) From: Tony Fleisher X-Sender: fleisher@takhus-home.ashlandfn.org To: current@FreeBSD.ORG Subject: Re: hints static wiring In-Reply-To: <20000827184037.A22500@Odin.AC.HMC.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a suggestion, but isn't this the type of thing that should be added to UPDATING? "This file contains a list, in reverse chronologocal order, of major breakages in tracking -current." TOny. On Sun, 27 Aug 2000, Brooks Davis wrote: > On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote: > > > > When kernel is built with static device wiring > > (i.e. 'hints' line is enabled in the config file), > > is /boot/device.hints required? > > > > Doing 'make install' without /boot/device.hints is failed, > > saying "You must set up a /boot/device.hints file first." > > Is this right? > > You should read cvs-all. There was a commit by Peter which forces you > to install a /boot/device.hints file to install a kernel as an anti-foot > shooting measure. An empty file (ie touch /boot/device.hints) is > acceptable for those who don't want to use a hints file. > > -- Brooks > > -- > Any statement of the form "X is the one, true Y" is FALSE. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 0:21:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id CFF5137B423 for ; Mon, 28 Aug 2000 00:21:09 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7S7L4N04131; Mon, 28 Aug 2000 09:21:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: Your message of "Sun, 27 Aug 2000 16:34:27 PDT." Date: Mon, 28 Aug 2000 09:21:04 +0200 Message-ID: <4129.967447264@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > >I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3 >'da' disks that were found. > >The only real problem is that it won't see the partitions made for >'dangerously dedicated' 'da' disks. What's the plan for addressing this? Hmm, which exact names are you missing ? Have you tried accessing them directly, for instance: ls -l /dev/da0s2e or whatever their names are ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 0:40:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EBEEE37B424 for ; Mon, 28 Aug 2000 00:40:19 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA21418; Mon, 28 Aug 2000 00:33:59 -0700 Date: Mon, 28 Aug 2000 00:33:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: <4129.967447264@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Aug 2000, Poul-Henning Kamp wrote: > In message , Matthew > Jacob writes: > > > >I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3 > >'da' disks that were found. > > > >The only real problem is that it won't see the partitions made for > >'dangerously dedicated' 'da' disks. What's the plan for addressing this? > > Hmm, which exact names are you missing ? > > Have you tried accessing them directly, for instance: > > ls -l /dev/da0s2e > > or whatever their names are ? Sure. They're not there. A reboot still just has da0[c], da1[c], and da2[c] show up. Remember that there's no such thing as slices in alpha. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 0:48:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 30D2037B43C for ; Mon, 28 Aug 2000 00:48:11 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7S7m8N04483; Mon, 28 Aug 2000 09:48:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: Your message of "Mon, 28 Aug 2000 00:33:56 PDT." Date: Mon, 28 Aug 2000 09:48:08 +0200 Message-ID: <4481.967448888@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > > >On Mon, 28 Aug 2000, Poul-Henning Kamp wrote: > >> In message , Matthew >> Jacob writes: >> > >> >I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3 >> >'da' disks that were found. >> > >> >The only real problem is that it won't see the partitions made for >> >'dangerously dedicated' 'da' disks. What's the plan for addressing this? >> >> Hmm, which exact names are you missing ? >> >> Have you tried accessing them directly, for instance: >> >> ls -l /dev/da0s2e >> >> or whatever their names are ? > >Sure. They're not there. A reboot still just has da0[c], da1[c], and >da2[c] show up. > >Remember that there's no such thing as slices in alpha. What names do you usually access your disks by ? Just da0a etc ? You should be able to find those as well with the clone stuff... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 0:56:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D34EE37B42C for ; Mon, 28 Aug 2000 00:56:10 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA21455; Mon, 28 Aug 2000 00:55:20 -0700 Date: Mon, 28 Aug 2000 00:55:18 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: <4481.967448888@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What names do you usually access your disks by ? Just da0a etc ? da0{a,b,c,d} and so on.. > > You should be able to find those as well with the clone stuff... Nope. Weren't there. I booted up once. I had 3 disks- none with a FreeBSD label. The contents of /dev for da disks was /dev/da{0,1,2}[c]. So, I did the '-Brw da0 auto' and disklabel -e trick to add a da0a to da0. disklabel happily saw da0a after this. Nothing in /dev. Okay- so this kind of rescan doesn't work yet. So, I reboot. The contents of dev still are /dev/da{0,1,2}[c]. I mostly was raising this to see if someone else has tried alpha in this regard. If not- I can help debug this and fix it, but next week. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 1:19:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-009.telepath.com [216.14.0.9]) by hub.freebsd.org (Postfix) with SMTP id C844337B422 for ; Mon, 28 Aug 2000 01:19:51 -0700 (PDT) Received: (qmail 77114 invoked by uid 100); 28 Aug 2000 08:19:15 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14762.8323.382969.782508@guru.mired.org> Date: Mon, 28 Aug 2000 03:19:15 -0500 (CDT) To: Brooks Davis Cc: current@FreeBSD.ORG Subject: Re: hints static wiring In-Reply-To: <20000827184037.A22500@Odin.AC.HMC.Edu> References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brooks Davis writes: > On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote: > > Doing 'make install' without /boot/device.hints is failed, > > saying "You must set up a /boot/device.hints file first." > > Is this right? > You should read cvs-all. There was a commit by Peter which forces you > to install a /boot/device.hints file to install a kernel as an anti-foot > shooting measure. An empty file (ie touch /boot/device.hints) is > acceptable for those who don't want to use a hints file. I do read cvs-all, and I missed it. Not did I find device.hints in the relevant Makefiles. Can you provide a pointer to details on how /boot/device.hints is used in the build process, or how having an empty one keeps you from shooting yourself in the foot? Thanx, ; Mon, 28 Aug 2000 01:22:35 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7S8MWN04757; Mon, 28 Aug 2000 10:22:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: Your message of "Mon, 28 Aug 2000 00:55:18 PDT." Date: Mon, 28 Aug 2000 10:22:32 +0200 Message-ID: <4755.967450952@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> >> What names do you usually access your disks by ? Just da0a etc ? > >da0{a,b,c,d} and so on.. >> >> You should be able to find those as well with the clone stuff... > >Nope. Weren't there. > >I booted up once. I had 3 disks- none with a FreeBSD label. The >contents of /dev for da disks was /dev/da{0,1,2}[c]. > >So, I did the '-Brw da0 auto' and disklabel -e trick to add >a da0a to da0. disklabel happily saw da0a after this. Nothing >in /dev. Okay- so this kind of rescan doesn't work yet. > >So, I reboot. The contents of dev still are /dev/da{0,1,2}[c]. I mostly >was raising this to see if someone else has tried alpha in this regard. >If not- I can help debug this and fix it, but next week. Hmm, can you send me a ls -l /dev from a !devfs alpha so I can see what it looks like ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 1:33:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BD45237B422 for ; Mon, 28 Aug 2000 01:33:23 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA21511; Mon, 28 Aug 2000 01:33:20 -0700 Date: Mon, 28 Aug 2000 01:33:18 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Meyer Cc: Brooks Davis , current@FreeBSD.ORG Subject: Re: hints static wiring In-Reply-To: <14762.8323.382969.782508@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I do read cvs-all, and I missed it. Not did I find device.hints in the > relevant Makefiles. Can you provide a pointer to details on how > /boot/device.hints is used in the build process, or how having an > empty one keeps you from shooting yourself in the foot? cvs-all is not appropriate. I am noticing a 3-7 day lag on UPDATING. Bad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 1:40:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-054.telepath.com [216.14.0.54]) by hub.freebsd.org (Postfix) with SMTP id 7B1C937B422 for ; Mon, 28 Aug 2000 01:40:39 -0700 (PDT) Received: (qmail 77598 invoked by uid 100); 28 Aug 2000 08:40:38 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14762.9605.935030.886966@guru.mired.org> Date: Mon, 28 Aug 2000 03:40:37 -0500 (CDT) To: "James Johnson" Cc: Subject: Installkernel In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Johnson writes: > The method of building and installing a kernel to me seems a bit off.. Both > the buildworld and installworld targets default to GENERIC, yet GENERIC is a > file checked into the -CURRENT CVS repository.. Any changes to this file > will get blown away if whenever you update the sources unless you explicity > exclude this file. No one I know runs BSD with a GENERIC kernel, they have > specific requirements for the hardware in their machines. Having to specify > which kernel to build with the KERNEL= parameter seems to indicate that > people should be running GENERIC kernels all the time as it is the default. > This just doesnt seem right. Now that it's all working properly, I like it. I build for multiple machines on one box, and then NFS-mount /usr/src & /usr/obj to do the installs. Being able to build all the kernels with one command, and use the same install commands on each box makes my life much simpler. As for GENERIC, it's what people run by default, and it can be used as is on much hardware. The documentation is a bit behind - the handbook should mention setting KERNEL in /etc/make.conf when it talks about buildkernel and installkernel. To: Poul-Henning Kamp Cc: gjohnson@gs.verio.net, current@freebsd.org, questions@freebsd.org Subject: Re: devfs In-reply-to: Your message of "Sun, 27 Aug 2000 21:35:26 +0200." <2013.967404926@critter> Date: Mon, 28 Aug 2000 11:06:44 +0200 Message-ID: <76354.967453604@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Aug 2000 21:35:26 +0200, Poul-Henning Kamp wrote: > Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init > will mount devfs on /dev automatically. Out of curiosity, what's the motivation behind this decision? Why don't you allow defvs to be mounted on an arbitrary mount point? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 2:15:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 761C037B43E; Mon, 28 Aug 2000 02:15:04 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7S9ErN05093; Mon, 28 Aug 2000 11:14:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: gjohnson@gs.verio.net, current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: devfs In-Reply-To: Your message of "Mon, 28 Aug 2000 11:06:44 +0200." <76354.967453604@axl.fw.uunet.co.za> Date: Mon, 28 Aug 2000 11:14:53 +0200 Message-ID: <5091.967454093@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <76354.967453604@axl.fw.uunet.co.za>, Sheldon Hearn writes: > > >On Sun, 27 Aug 2000 21:35:26 +0200, Poul-Henning Kamp wrote: > >> Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init >> will mount devfs on /dev automatically. > >Out of curiosity, what's the motivation behind this decision? Why don't >you allow defvs to be mounted on an arbitrary mount point? You can also mount it other places: mount -t devfs foo /usr/jail/jail1/dev (but the "no new devices" feature is not committed yet, I'm still working on it). The reason for mounting it in /sbin/init is historical and possibly wrong but it does have the benefit that it will DTRT for people. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 2:34:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id D0C3C37B423; Mon, 28 Aug 2000 02:34:23 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 869F928C43; Mon, 28 Aug 2000 16:34:16 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 7D4A928703; Mon, 28 Aug 2000 16:34:16 +0700 (ALMST) Date: Mon, 28 Aug 2000 16:34:16 +0700 (ALMST) From: Boris Popov To: Poul-Henning Kamp Cc: Sheldon Hearn , gjohnson@gs.verio.net, current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: devfs In-Reply-To: <5091.967454093@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Aug 2000, Poul-Henning Kamp wrote: > >> Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init > >> will mount devfs on /dev automatically. > > > >Out of curiosity, what's the motivation behind this decision? Why don't > >you allow defvs to be mounted on an arbitrary mount point? > > The reason for mounting it in /sbin/init is historical and possibly > wrong but it does have the benefit that it will DTRT for people. This is necessary for proper synching of the root filesystem. To achieve this effect devfs is mounted over readonly UFS, so when the root filesystem is updated to R/W state it pulls the proper device from devfs filesystem. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 2:59:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [64.50.162.3]) by hub.freebsd.org (Postfix) with SMTP id 0284637B42C for ; Mon, 28 Aug 2000 02:59:12 -0700 (PDT) Received: (qmail 42964 invoked by uid 1000); 28 Aug 2000 09:59:11 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Aug 2000 09:59:11 -0000 Date: Mon, 28 Aug 2000 05:59:11 -0400 (EDT) From: Systems Administrator To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: Monitor dies and doesn't come back. In-Reply-To: <20000828121130.J38394@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would the controller I have my drives on really cause that? Seems kind of strange :).. ---- Jason DiCioccio - IBM Global Services - djason@us.ibm.com - www.ibm.com Systems Admin - Open Domain Server - geniusj@ods.org - www.ods.org FreeBSD - The Power to Serve - - www.freebsd.org ---- On Mon, 28 Aug 2000, Greg Lehey wrote: > [dropping -questions, this is a -CURRENT problem] > > On Sunday, 27 August 2000 at 22:28:34 -0400, Systems Administrator wrote: > > I've been having a strange problem recently after installing a new > > harddrive.. the harddrive works fine in other OS's, but in FreeBSD, > > (seemingly after the HD install), the Monitor (CTX VL19") goes into > > powersaving and you cant get it back without doing a cold reboot.. not > > even a warm reboot will work. I am not sure exactly what is happening > > here, perhaps something borked? I have a Western Digital Caviar 45GB drive > > running at UDMA33. > > Well, this isn't the monitor, of course. Your system is probably > dying a horrible death and not producing any video output. > > > ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 > > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > > acd0: CD-RW at ata1-master using WDMA2 > > acd1: CDROM at ata1-slave using PIO3 > > Mounting root from ufs:/dev/ad0s1a > > WARNING: / was not properly dismounted > > Well, it's not a good idea to put both disks on the same controller > anyway. What happens if you put the disks on the primaries of each > controller, and the CD-ROMS on the secondaries? If that doesn't help, > does the system at least work without the 45 GB drive? Anyway, how > far do you get in the book process? Can you get into single user mode > the way you are now? > > Greg > -- > When replying to this message, please copy the original recipients. > For more information, see http://www.lemis.com/questions.html > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 3: 1:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id F225F37B423 for ; Mon, 28 Aug 2000 03:01:39 -0700 (PDT) Received: (qmail 9309 invoked from network); 28 Aug 2000 10:01:39 -0000 Received: from acs-24-154-11-41.zoominternet.net (HELO cvzoom.net) (24.154.11.41) by scully.zoominternet.net with SMTP; 28 Aug 2000 10:01:39 -0000 Message-ID: <39AA3882.914FC0A0@cvzoom.net> Date: Mon, 28 Aug 2000 06:01:38 -0400 From: Donn Miller X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: Brooks Davis , current@FreeBSD.ORG Subject: Re: hints static wiring References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > I do read cvs-all, and I missed it. Not did I find device.hints in the > relevant Makefiles. Can you provide a pointer to details on how > /boot/device.hints is used in the build process, or how having an > empty one keeps you from shooting yourself in the foot? Actually, device.hints isn't used in the build process. Your KERNEL.hints file is hard-coded into the kernel when your kernel is built (assuming you use one). /boot/device.hints is used to override the "hardcoded" values of hints, KERNEL.hints, at boot time. Sometimes, people can make a mistake in KERNEL.hints, and it's necessary to override those hints with /boot/device.hints. So, device.hints is created after-the-fact, and not part of the kernel build. Of course, if you don't have any hints to override, then just install an empty device.hints file. device.hints is there to save you from rebuilding your kernel every time you want to change a hint value. -Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 3: 4:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [64.50.162.3]) by hub.freebsd.org (Postfix) with SMTP id C87D337B422 for ; Mon, 28 Aug 2000 03:04:43 -0700 (PDT) Received: (qmail 43097 invoked by uid 1000); 28 Aug 2000 10:04:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Aug 2000 10:04:42 -0000 Date: Mon, 28 Aug 2000 06:04:42 -0400 (EDT) From: Systems Administrator To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: Monitor dies and doesn't come back. In-Reply-To: <20000828121130.J38394@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did just notice something.. why would I have sc0/sc1 and vga0/vga1? Or is that just because of the 'options SC_PIXEL_MODE' that I have? ---- Jason DiCioccio - IBM Global Services - djason@us.ibm.com - www.ibm.com Systems Admin - Open Domain Server - geniusj@ods.org - www.ods.org FreeBSD - The Power to Serve - - www.freebsd.org ---- On Mon, 28 Aug 2000, Greg Lehey wrote: > [dropping -questions, this is a -CURRENT problem] > > On Sunday, 27 August 2000 at 22:28:34 -0400, Systems Administrator wrote: > > I've been having a strange problem recently after installing a new > > harddrive.. the harddrive works fine in other OS's, but in FreeBSD, > > (seemingly after the HD install), the Monitor (CTX VL19") goes into > > powersaving and you cant get it back without doing a cold reboot.. not > > even a warm reboot will work. I am not sure exactly what is happening > > here, perhaps something borked? I have a Western Digital Caviar 45GB drive > > running at UDMA33. > > Well, this isn't the monitor, of course. Your system is probably > dying a horrible death and not producing any video output. > > > ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 > > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > > acd0: CD-RW at ata1-master using WDMA2 > > acd1: CDROM at ata1-slave using PIO3 > > Mounting root from ufs:/dev/ad0s1a > > WARNING: / was not properly dismounted > > Well, it's not a good idea to put both disks on the same controller > anyway. What happens if you put the disks on the primaries of each > controller, and the CD-ROMS on the secondaries? If that doesn't help, > does the system at least work without the 45 GB drive? Anyway, how > far do you get in the book process? Can you get into single user mode > the way you are now? > > Greg > -- > When replying to this message, please copy the original recipients. > For more information, see http://www.lemis.com/questions.html > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 3: 8:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-058.telepath.com [216.14.0.58]) by hub.freebsd.org (Postfix) with SMTP id 311D937B424 for ; Mon, 28 Aug 2000 03:08:44 -0700 (PDT) Received: (qmail 80118 invoked by uid 100); 28 Aug 2000 10:08:42 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14762.14890.276820.183791@guru.mired.org> Date: Mon, 28 Aug 2000 05:08:42 -0500 (CDT) To: Donn Miller Cc: Brooks Davis , current@FreeBSD.ORG Subject: Re: hints static wiring In-Reply-To: <39AA3882.914FC0A0@cvzoom.net> References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller writes: > Mike Meyer wrote: > > I do read cvs-all, and I missed it. Not did I find device.hints in the > > relevant Makefiles. Can you provide a pointer to details on how > > /boot/device.hints is used in the build process, or how having an > > empty one keeps you from shooting yourself in the foot? > Actually, device.hints isn't used in the build process. In that case, why does the kernel build process fail if it doesn't exist? > KERNEL.hints file is hard-coded into the kernel when your kernel is > built (assuming you use one). /boot/device.hints is used to override > the "hardcoded" values of hints, KERNEL.hints, at boot time. Sometimes, > people can make a mistake in KERNEL.hints, and it's necessary to > override those hints with /boot/device.hints. So, device.hints is > created after-the-fact, and not part of the kernel build. Of course, if > you don't have any hints to override, then just install an empty > device.hints file. Will the system fail to boot if there isn't an empty device.hints file? ; Mon, 28 Aug 2000 04:37:53 -0700 (PDT) Received: from localhost (gross@localhost) by sc-24-165-84-137.socal.rr.com (8.9.3/8.9.3) with ESMTP id EAA00415 for ; Mon, 28 Aug 2000 04:38:48 -0700 (PDT) (envelope-from gross@socal.rr.com) X-Authentication-Warning: sc-24-165-84-137.socal.rr.com: gross owned process doing -bs Date: Mon, 28 Aug 2000 04:38:48 -0700 (PDT) From: "Glendon M. Gross" To: current@freebsd.org Subject: Re: 3.4STABLE to 4.1STABLE can't make modules (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Although binary distribution would be easier, I suspect that many of us would prefer to build everything locally. That is one of the unique features of FreeBSD, even if it is time consuming. > > On Sat, Aug 27, 2000 , Gary Kline wrote: > > > > > > BTW, I have some ideas how this entire issue of updating one's > > FBSD system can be done lots easier: say, by doing essentially > > an ftp binary up-rev across major releases: 2 -> 3 or 3 -> 4. > > Then using a relatively simple build|install and mergemaster > > moving within released. > > > > Like everything else, it's a matter of time and prio.... > > > > gary > >-- > > Gary D. Kline kline@tao.thought.org Public service Unix > > > I vote for that! > Thanks. > Lazaro > > > > > > > > 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-current" in the body of the message From owner-freebsd-current Mon Aug 28 4:53:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id AE03737B43E for ; Mon, 28 Aug 2000 04:53:48 -0700 (PDT) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id NAA15311 for current@freebsd.org; Mon, 28 Aug 2000 13:53:47 +0200 (CEST) Date: Mon, 28 Aug 2000 13:53:46 +0200 From: Martin Cracauer To: current@freebsd.org Subject: vn broken? Message-ID: <20000828135346.A15059@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -current from Aug, 22, cd9660 image file mounted via vn reports this: Aug 28 13:45:51 counter /kernel: unexpected vn driver lock: 0xccf008c0: type VREG, usecount 2, writecount 1, refcount 452, flags (VOBJBUF) Aug 28 13:45:51 counter /kernel: tag VT_UFS, ino 357635, on dev #da/6 (13, 6) lock type inode: EXCL (count 1) by pid 5 This happens when multiple parallel things are done to the iso filesystem inside the vnode, i.e.: A single find /mnt -type f -exec cat {} \; | wc -c works without problems, two of them started with a delay cause these messages. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 5: 5:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id D705E37B423 for ; Mon, 28 Aug 2000 05:05:25 -0700 (PDT) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id OAA15476 for current@freebsd.org; Mon, 28 Aug 2000 14:05:23 +0200 (CEST) Date: Mon, 28 Aug 2000 14:05:23 +0200 From: Martin Cracauer To: current@freebsd.org Subject: Re: vn broken? Message-ID: <20000828140522.A15442@cons.org> References: <20000828135346.A15059@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000828135346.A15059@cons.org>; from cracauer@cons.org on Mon, Aug 28, 2000 at 01:53:46PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I should haven mentioned that this is a SMP machine (i440BX P-III 550 dual) and is running vmware. > -current from Aug, 22, cd9660 image file mounted via vn reports this: > > Aug 28 13:45:51 counter /kernel: unexpected vn driver lock: 0xccf008c0: type VREG, usecount 2, writecount 1, refcount 452, flags (VOBJBUF) > Aug 28 13:45:51 counter /kernel: tag VT_UFS, ino 357635, on dev #da/6 (13, 6) lock type inode: EXCL (count 1) by pid 5 > > This happens when multiple parallel things are done to the iso > filesystem inside the vnode, i.e.:[...] dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Aug 22 12:47:31 MEST 2000 cracauer@counter.bik-gmbh.de:/usr/src/sys/compile/COUNTER Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 268423168 (262132K bytes) avail memory = 257658880 (251620K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 11 IOAPIC #0 intpin 18 -> irq 10 IOAPIC #0 intpin 19 -> irq 12 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0396000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6974 (c0006974) VESA: Matrox Graphics Inc. md0: Malloc disk apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 pci0: at 4.1 pci0: at 4.2 irq 12 intpm0: port 0xe800-0xe80f irq 9 at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: port 0xd000-0xd0ff mem 0xe0000000-0xe0000fff irq 12 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs fxp0: port 0xb800-0xb83f mem 0xdf000000-0xdf0fffff,0xdf800000-0xdf800fff irq 12 at device 9.0 on pci0 fxp0: Ethernet address 00:d0:b7:92:4e:cc ahc1: port 0xb400-0xb4ff mem 0xde800000-0xde800fff irq 10 at device 10.0 on pci0 ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs isa0: too many memory ranges fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0a da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit) da0: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) WARNING: / was not properly dismounted cd0 at ahc1 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 5.000MB/s transfers (5.000MHz, offset 8) cd0: cd present [352862 x 2048 byte records] /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized (cd0:ahc1:0:4:0): PAUSE/RESUME. CDB: 4b 0 0 0 0 0 0 0 0 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:2c,0 (cd0:ahc1:0:4:0): Command sequence error /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 11716, unlocked dirty pages: 11665 [more cd error of the same kind deleted] (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 3517994, unlocked dirty pages: 1967598 (cd0:ahc1:0:4:0): PAUSE/RESUME. CDB: 4b 0 0 0 0 0 0 0 0 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:2c,0 (cd0:ahc1:0:4:0): Command sequence error (cd0:ahc1:0:4:0): PAUSE/RESUME. CDB: 4b 0 0 0 0 0 0 0 0 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:2c,0 (cd0:ahc1:0:4:0): Command sequence error sa0 at ahc1 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 8.064MB/s transfers (8.064MHz, offset 15) sa1 at ahc1 bus 0 target 3 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 8.064MB/s transfers (8.064MHz, offset 8) cd1 at ahc1 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: cd present [1 x 2048 byte records] cd9660: RockRidge Extension /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 1111976, unlocked dirty pages: 696805 (cd0:ahc1:0:4:0): PAUSE/RESUME. CDB: 4b 0 0 0 0 0 0 0 0 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:2c,0 (cd0:ahc1:0:4:0): Command sequence error /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 462622, unlocked dirty pages: 303701 (cd0:ahc1:0:4:0): PAUSE/RESUME. CDB: 4b 0 0 0 0 0 0 0 0 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:2c,0 (cd0:ahc1:0:4:0): Command sequence error /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 372415, unlocked dirty pages: 249684 (cd0:ahc1:0:4:0): PAUSE/RESUME. CDB: 4b 0 0 0 0 0 0 0 0 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:2c,0 (cd0:ahc1:0:4:0): Command sequence error /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 135922, unlocked dirty pages: 73338 (cd0:ahc1:0:4:0): PAUSE/RESUME. CDB: 4b 0 0 0 0 0 0 0 0 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:2c,0 (cd0:ahc1:0:4:0): Command sequence error (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present pid 79277 (tosha), uid 0: exited on signal 11 (core dumped) pid 79278 (tosha), uid 0: exited on signal 11 (core dumped) pid 79719 (tosha), uid 0: exited on signal 11 (core dumped) (cd0:ahc1:0:4:0): READ(10). CDB: 28 0 0 3 93 20 0 0 20 0 (cd0:ahc1:0:4:0): ILLEGAL REQUEST asc:21,0 (cd0:ahc1:0:4:0): Logical block address out of range (cd0:ahc1:0:4:0): cddone: got error 0x16 back cd9660: Joliet Extension unexpected vn driver lock: 0xccf008c0: type VREG, usecount 2, writecount 1, refcount 227, flags (VOBJBUF) tag VT_UFS, ino 357635, on dev #da/6 (13, 6) lock type inode: EXCL (count 1) by pid 5 (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present (cd0:ahc1:0:4:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 0 0 18 0 (cd0:ahc1:0:4:0): NOT READY asc:3a,0 (cd0:ahc1:0:4:0): Medium not present unexpected vn driver lock: 0xccf008c0: type VREG, usecount 2, writecount 1, refcount 452, flags (VOBJBUF) tag VT_UFS, ino 357635, on dev #da/6 (13, 6) lock type inode: EXCL (count 1) by pid 5 unexpected vn driver lock: 0xccf008c0: type VREG, usecount 2, writecount 1, refcount 740, flags (VOBJBUF) tag VT_UFS, ino 357635, on dev #da/6 (13, 6) lock type inode: EXCL (count 1) by pid 82130 unexpected vn driver lock: 0xccf008c0: type VREG, usecount 2, writecount 1, refcount 731, flags (VOBJBUF) tag VT_UFS, ino 357635, on dev #da/6 (13, 6) lock type inode: EXCL (count 1) by pid 82131 [truncated] Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 5:35:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 48AEE37B424 for ; Mon, 28 Aug 2000 05:35:23 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id OAA02518; Mon, 28 Aug 2000 14:33:33 +0200 (CEST) (envelope-from asmodai) Date: Mon, 28 Aug 2000 14:33:33 +0200 From: Jeroen Ruigrok van der Werven To: Soren Schmidt Cc: sthaug@nethelp.no, tstromberg@rtci.com, freebsd-current@FreeBSD.ORG Subject: Re: IDE RAID (HPT-370/Abit KT7-RAID) install questions.. Message-ID: <20000828143333.D2176@lucifer.bart.nl> References: <75069.967393912@verdi.nethelp.no> <200008271938.VAA42069@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008271938.VAA42069@freebsd.dk>; from sos@freebsd.dk on Sun, Aug 27, 2000 at 09:38:24PM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000827 23:05], Soren Schmidt (sos@freebsd.dk) wrote: >Well, this wouldn't have happend without Jeroen (asmodai) having >good contacts at HighPoint, so I thank him for making this >possible. No problem. It's all team work anyways, I couldn't write the driver. ;) Hopefully Highpoint will be so friendly to help me out on this RAID issue. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl You are more than you think, less than you could be... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 5:41:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id EB9BB37B43C for ; Mon, 28 Aug 2000 05:41:09 -0700 (PDT) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id PAA09411; Mon, 28 Aug 2000 15:40:44 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id PAA33865; Mon, 28 Aug 2000 15:40:44 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39AA5DC6.8D73081B@FreeBSD.org> Date: Mon, 28 Aug 2000 15:40:38 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.74 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Mike Meyer Cc: Donn Miller , Brooks Davis , current@FreeBSD.org Subject: Re: hints static wiring References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > Donn Miller writes: > > Mike Meyer wrote: > > > I do read cvs-all, and I missed it. Not did I find device.hints in the > > > relevant Makefiles. Can you provide a pointer to details on how > > > /boot/device.hints is used in the build process, or how having an > > > empty one keeps you from shooting yourself in the foot? > > Actually, device.hints isn't used in the build process. > > In that case, why does the kernel build process fail if it doesn't > exist? Probably because you have `hints "BLABLA.hints"' line in your kernel config file. > > KERNEL.hints file is hard-coded into the kernel when your kernel is > > built (assuming you use one). /boot/device.hints is used to override > > the "hardcoded" values of hints, KERNEL.hints, at boot time. Sometimes, > > people can make a mistake in KERNEL.hints, and it's necessary to > > override those hints with /boot/device.hints. So, device.hints is > > created after-the-fact, and not part of the kernel build. Of course, if > > you don't have any hints to override, then just install an empty > > device.hints file. > > Will the system fail to boot if there isn't an empty device.hints > file? No, it will boot, but some devices (like keyboard, console etc) would not work. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 5:54:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom1-026.telepath.com [216.14.1.26]) by hub.freebsd.org (Postfix) with SMTP id D0D3B37B424 for ; Mon, 28 Aug 2000 05:54:22 -0700 (PDT) Received: (qmail 84044 invoked by uid 100); 28 Aug 2000 12:54:21 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14762.24829.363032.115605@guru.mired.org> Date: Mon, 28 Aug 2000 07:54:21 -0500 (CDT) To: Maxim Sobolev Cc: Donn Miller , Brooks Davis , current@FreeBSD.org Subject: Re: hints static wiring In-Reply-To: <39AA5DC6.8D73081B@FreeBSD.org> References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> <39AA5DC6.8D73081B@FreeBSD.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev writes: > Mike Meyer wrote: > > > Donn Miller writes: > > > Mike Meyer wrote: > > > > I do read cvs-all, and I missed it. Not did I find device.hints in the > > > > relevant Makefiles. Can you provide a pointer to details on how > > > > /boot/device.hints is used in the build process, or how having an > > > > empty one keeps you from shooting yourself in the foot? > > > Actually, device.hints isn't used in the build process. > > In that case, why does the kernel build process fail if it doesn't > > exist? > Probably because you have `hints "BLABLA.hints"' line in your kernel config > file. That doesn't really answer the question. Yup, I use GENERIC.hints. That exists. I can see why that not existing would cause problems, but not /boot/device.hints? *Especially* when I'm building a kernel for a different machine? > > > KERNEL.hints file is hard-coded into the kernel when your kernel is > > > built (assuming you use one). /boot/device.hints is used to override > > > the "hardcoded" values of hints, KERNEL.hints, at boot time. Sometimes, > > > people can make a mistake in KERNEL.hints, and it's necessary to > > > override those hints with /boot/device.hints. So, device.hints is > > > created after-the-fact, and not part of the kernel build. Of course, if > > > you don't have any hints to override, then just install an empty > > > device.hints file. > > Will the system fail to boot if there isn't an empty device.hints > > file? > No, it will boot, but some devices (like keyboard, console etc) would not work. That's clearly not true - I just removed an empty /boot/device.hints and rebooted, and all those things work fine. I can believe that such things won't work if they aren't specified in some hints file, but an empty /boot/device.hints doesn't do anything more to specify them than one that isn't there. ; Mon, 28 Aug 2000 06:10:30 -0700 (PDT) Received: from gab200r1.ems.att.com ([135.37.94.32]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id JAA05852; Mon, 28 Aug 2000 09:10:28 -0400 (EDT) Received: from njb140bh1.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id JAA22194; Mon, 28 Aug 2000 09:12:20 -0400 (EDT) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2652.35) id ; Mon, 28 Aug 2000 09:10:28 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'George W. Dinolt'" , Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: RE: Linux ABI no longer supports staroffice Date: Mon, 28 Aug 2000 09:10:27 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Up until this weekend, I was able to use the staroffice52 port with > little problem (I had installed it earlier without benefit of the port > and it worked fine.) I did a 5.0-current kernel rebuild on > Thursday with > sources current on that day and things were fine. When I rebuilt my > kernel yesterday afternoon with sources from Saturday > morning, the port > stopped working. I get the following error messages > > I18N: X Window System doesn't support locale "C" > _X11TransSocketOpen: socket() failed for local > _X11TransSocketOpenCOTSClient: Unable to open socket for local > _X11TransOpen: transport open failed for local/dinolt1.bingdrive:0 > setup.bin: cannot open display ":0.0" > Please check your "DISPLAY" environment variable, as well as the > permissions to access that display (See "man X" resp. "man xhost" for > details) same here :( i got original Sun CD with StartOffice 5.1a and tried to install it. it failed. i used # make WITH_CDROM=yes USE_CDROM=yes install and everything was fine, but then i got exactly the same error. XFree86-3.3.6 and XFree86-contrib-3.3.6 both working just fine. ``xhost +'' did not resolve the problem. thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 6:18:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 328B337B43C for ; Mon, 28 Aug 2000 06:18:37 -0700 (PDT) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id QAA11292; Mon, 28 Aug 2000 16:18:23 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id QAA33993; Mon, 28 Aug 2000 16:18:24 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39AA6699.41E12730@FreeBSD.org> Date: Mon, 28 Aug 2000 16:18:17 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.74 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Mike Meyer Cc: Donn Miller , Brooks Davis , current@FreeBSD.org Subject: Re: hints static wiring References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> <39AA5DC6.8D73081B@FreeBSD.org> <14762.24829.363032.115605@guru.mired.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > > > Will the system fail to boot if there isn't an empty device.hints > > > file? > > No, it will boot, but some devices (like keyboard, console etc) would not work. > > That's clearly not true - I just removed an empty /boot/device.hints > and rebooted, and all those things work fine. I can believe that such > things won't work if they aren't specified in some hints file, but an > empty /boot/device.hints doesn't do anything more to specify them than > one that isn't there. That's probably because you have hints compiled into your kernel. Try to compile kernel w/o hints and use it with empty/unexistent /boot/device.hints and you will see what I mean. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 6:24:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom1-026.telepath.com [216.14.1.26]) by hub.freebsd.org (Postfix) with SMTP id 712F937B423 for ; Mon, 28 Aug 2000 06:24:52 -0700 (PDT) Received: (qmail 84835 invoked by uid 100); 28 Aug 2000 13:24:51 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14762.26659.335.344828@guru.mired.org> Date: Mon, 28 Aug 2000 08:24:50 -0500 (CDT) To: Maxim Sobolev Cc: Donn Miller , Brooks Davis , current@FreeBSD.org Subject: Re: hints static wiring In-Reply-To: <39AA6699.41E12730@FreeBSD.org> References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> <39AA5DC6.8D73081B@FreeBSD.org> <14762.24829.363032.115605@guru.mired.org> <39AA6699.41E12730@FreeBSD.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev writes: > Mike Meyer wrote: > > > > Will the system fail to boot if there isn't an empty device.hints > > > > file? > > > No, it will boot, but some devices (like keyboard, console etc) would not work. > > > > That's clearly not true - I just removed an empty /boot/device.hints > > and rebooted, and all those things work fine. I can believe that such > > things won't work if they aren't specified in some hints file, but an > > empty /boot/device.hints doesn't do anything more to specify them than > > one that isn't there. > That's probably because you have hints compiled into your kernel. Try to compile > kernel w/o hints and use it with empty/unexistent /boot/device.hints and you will see > what I mean. Well, yeah, I'd expect that. I'm still trying to figure out what *good* failing to compile unless there's an empty /boot/device.hints does. I mean, if I didn't provide kernel hints, it would make some sense if the build process could determine that it was building on the machine it was running on. ; Mon, 28 Aug 2000 06:26:29 -0700 (PDT) Received: from camtech.net.au ([203.38.173.62]) by mta03.mail.mel.aone.net.au with ESMTP id <20000828132619.WQLX359.mta03.mail.mel.aone.net.au@camtech.net.au> for ; Mon, 28 Aug 2000 23:26:19 +1000 Message-ID: <39AAF02F.96C7C86F@camtech.net.au> Date: Mon, 28 Aug 2000 23:05:20 +0000 From: Charlie Root X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 6:47:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id BA79C37B422 for ; Mon, 28 Aug 2000 06:47:48 -0700 (PDT) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id A1048E302; Mon, 28 Aug 2000 15:47:39 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000828193605.A290@zippy> References: <20000828193605.A290@zippy> Date: Mon, 28 Aug 2000 15:46:20 +0200 To: Alex Zepeda , current@FreeBSD.ORG From: Brad Knowles Subject: Re: SMP and softupdates? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:36 PM +0000 2000/8/28, Alex Zepeda wrote: > Perhaps in a rush to get started, I've compiled and > been using a SMP kernel even before the second processor arrives. This > has worked fine, however I've gotten some rather weird hangs and crashes > resulting in a nice lost+found directory on the usr fs. Personally, I'm astonished that an SMP kernel will actually boot and run on a uniprocessor machine. Before pointing any fingers at softupdates, etc... I think that the first thing I'd do on this machine is switch back to using a real uniprocessor kernel, and then see if I could replicate the problems. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 7:33:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 1C1CB37B424 for ; Mon, 28 Aug 2000 07:33:53 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 3AF4A1C6B; Mon, 28 Aug 2000 10:33:52 -0400 (EDT) Date: Mon, 28 Aug 2000 10:33:52 -0400 From: Bill Fumerola To: Systems Administrator Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Monitor dies and doesn't come back. Message-ID: <20000828103352.A33771@jade.chc-chimes.com> References: <20000828121130.J38394@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from geniusj@ods.org on Mon, Aug 28, 2000 at 06:04:42AM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 06:04:42AM -0400, Systems Administrator wrote: > I did just notice something.. why would I have sc0/sc1 and > vga0/vga1? Or is that just because of the 'options SC_PIXEL_MODE' > that I have? Before you go any further, just compile a GENERIC kernel and see if the same problems are experienced. Then start merging in what you have in your custom kernel (line by line or section by section). I once deleted the syscons device, other similar things are possible. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 7:37:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 08AEA37B42C for ; Mon, 28 Aug 2000 07:37:43 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id HAA68028; Mon, 28 Aug 2000 07:35:40 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008281435.HAA68028@pike.osd.bsdi.com> Subject: Re: SMP and softupdates? In-Reply-To: from Brad Knowles at "Aug 28, 2000 03:46:20 pm" To: Brad Knowles Date: Mon, 28 Aug 2000 07:35:38 -0700 (PDT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > At 7:36 PM +0000 2000/8/28, Alex Zepeda wrote: > > > Perhaps in a rush to get started, I've compiled and > > been using a SMP kernel even before the second processor arrives. This > > has worked fine, however I've gotten some rather weird hangs and crashes > > resulting in a nice lost+found directory on the usr fs. > > Personally, I'm astonished that an SMP kernel will actually boot > and run on a uniprocessor machine. Well, it does work. Right now if we enable multiple CPU's with SMPng the machine instantly panics, so we use a sysctl that keeps all the extra processors waiting until we are ready to kill the machine. Until that point in time, however, the machine runs happily on 1 cpu, and can build world ok, etc. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 7:46:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4A37F37B423; Mon, 28 Aug 2000 07:46:42 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id HAA25955; Mon, 28 Aug 2000 07:46:41 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id HAA33886; Mon, 28 Aug 2000 07:46:41 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 28 Aug 2000 07:46:41 -0700 (PDT) Message-Id: <200008281446.HAA33886@vashon.polstra.com> To: current@FreeBSD.ORG Cc: green@FreeBSD.ORG Subject: Re: panic: reducing sbsize: lost count, uid = 1001 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian Fundakowski Feldman wrote: > > Woops, I have the KASSERT bungled up. Please change > KASSERT(to < *hiwat && uip != NULL, > to > KASSERT(to >= *hiwat || uip != NULL, Thanks. The system comes up OK now. I'll try to provoke the lost count panic some more today, and I'll let you know what happens. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 8:15:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 3687237B423; Mon, 28 Aug 2000 08:15:30 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13TQdD-0002fM-00; Mon, 28 Aug 2000 17:15:27 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id RAA03243; Mon, 28 Aug 2000 17:15:26 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 3077; Mon Aug 28 17:14:01 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13TQbp-000L3v-00; Mon, 28 Aug 2000 17:14:01 +0200 From: Sheldon Hearn To: phk@freebsd.org Cc: current@freebsd.org Subject: devname(3) broken for DEFVS Date: Mon, 28 Aug 2000 17:14:01 +0200 Message-ID: <80966.967475641@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Poul-Henning, I've been having trouble with ps(1) printing invalid controlling terminal names for processes connected to psuedo-terminals. This only seems to be a problem for DEVFS-enabled systems. The output that makes it look like things are broken is this: $ ps -t p7 PID TT STAT TIME COMMAND 80571 #C5 Ss 0:00.10 bash It seems to be breakage in devname(3): $ gdb /usr/obj/usr/src/bin/ps/ps GNU gdb 4.18 [...] (gdb) break print.c:311 Breakpoint 1 at 0x8048cb6: file /usr/src/bin/ps/print.c, line 311. (gdb) run Starting program: /usr/obj/usr/src/bin/ps/ps PID TT STAT TIME COMMAND Breakpoint 1, tname (k=0x8090690, ve=0x8086040) at /usr/src/bin/ps/print.c:311 311 if (dev == NODEV || (ttname = devname(dev, S_IFCHR)) == NULL) (gdb) n 314 if (strncmp(ttname, "tty", 3) == 0 || (gdb) print ttname $2 = 0x807afe8 "#C5:1" Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 8:16:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id A5A5737B424 for ; Mon, 28 Aug 2000 08:16:09 -0700 (PDT) Received: (qmail 30827 invoked from network); 28 Aug 2000 15:16:06 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 28 Aug 2000 15:16:06 -0000 Date: Tue, 29 Aug 2000 02:16:04 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Matthew Jacob Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Aug 2000, Matthew Jacob wrote: > On Mon, 28 Aug 2000, Poul-Henning Kamp wrote: > > > Have you tried accessing them directly, for instance: > > > > ls -l /dev/da0s2e > > > > or whatever their names are ? > > Sure. They're not there. A reboot still just has da0[c], da1[c], and > da2[c] show up. That's more than show up on i386's :-). After booting with -s, only the whole disk devices and the root device show up. Devices for slices and partitions slices only show up when they are opened or stat'ed. This bug is normally mostly hidden by opening most partitions to mount them. > Remember that there's no such thing as slices in alpha. I thought that they worked. They should work if they are configured. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 8:24: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id BD22437B43C for ; Mon, 28 Aug 2000 08:24:04 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7SFNtN11144; Mon, 28 Aug 2000 17:23:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: devname(3) broken for DEFVS In-Reply-To: Your message of "Mon, 28 Aug 2000 17:14:01 +0200." <80966.967475641@axl.fw.uunet.co.za> Date: Mon, 28 Aug 2000 17:23:55 +0200 Message-ID: <11142.967476235@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi Poul-Henning, > >I've been having trouble with ps(1) printing invalid controlling >terminal names for processes connected to psuedo-terminals. > >This only seems to be a problem for DEVFS-enabled systems. Yes, devname(3) need to learn a few things. It's actually always been a problem if you added device nodes after boot where dev_mkdb was run. I think the DTRT solution is a sysctl where kern_conf.c can answer the question. It's on my list. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 8:26:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id B5D4637B43E for ; Mon, 28 Aug 2000 08:26:16 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7SFQ4N11165; Mon, 28 Aug 2000 17:26:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Matthew Jacob , current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: Your message of "Tue, 29 Aug 2000 02:16:04 +1100." Date: Mon, 28 Aug 2000 17:26:04 +0200 Message-ID: <11163.967476364@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Ev ans writes: >> Sure. They're not there. A reboot still just has da0[c], da1[c], and >> da2[c] show up. > >That's more than show up on i386's :-). After booting with -s, only >the whole disk devices and the root device show up. Devices for slices >and partitions slices only show up when they are opened or stat'ed. >This bug is normally mostly hidden by opening most partitions to mount >them. Well, this "bug" is built into the current diskslice/label code as you know (you wrote it :-) It doesn't have anything to do with DEVFS as such. My proposed solution for this can be found in the bio/buf paper I wrote. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 9:10:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7116D37B43E for ; Mon, 28 Aug 2000 09:10:35 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA22815; Mon, 28 Aug 2000 09:04:09 -0700 Date: Mon, 28 Aug 2000 09:00:32 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bruce Evans Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That's more than show up on i386's :-). After booting with -s, only > the whole disk devices and the root device show up. Devices for slices > and partitions slices only show up when they are opened or stat'ed. > This bug is normally mostly hidden by opening most partitions to mount > them. Hmm. Well, it turned out that after a period of time da0a showed up. Poul says I might be out of date src-wise. I'll update again and see. > > Remember that there's no such thing as slices in alpha. > > I thought that they worked. They should work if they are configured. Sorry- I meant "SRM doesnt' grok i386 labels". -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 9:38:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id EE0A237B423 for ; Mon, 28 Aug 2000 09:38:31 -0700 (PDT) Received: from work.mzaki.nom (86.pool1.ipctokyo.att.ne.jp [165.76.245.86]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id BAA04837; Tue, 29 Aug 2000 01:38:24 +0900 (JST) Date: Tue, 29 Aug 2000 01:38:23 +0900 Message-ID: <863djpl4sg.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: current@FreeBSD.org Subject: Re: hints static wiring In-Reply-To: In your message of "Mon, 28 Aug 2000 08:24:50 -0500 (CDT)" <14762.26659.335.344828@guru.mired.org> References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> <39AA5DC6.8D73081B@FreeBSD.org> <14762.24829.363032.115605@guru.mired.org> <39AA6699.41E12730@FreeBSD.org> <14762.26659.335.344828@guru.mired.org> X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh..., I tried to summarize my opinion. If you find any misunderstandings of me, please correct them. *** What's happen if there's no /boot/device.hints? kernel has no built-in hints ... some devices would not work, system would stall! You can tell whole hints to the kernel interactively on /boot/loader, however it's a tiresome task. YES, this is the abominable situation. To avoid it, you should be warned at kernel-install-time. kernel has built-in hints (i.e. config has "hints" line) B-1: wrong hints ... some devices would not work, system could stall. You can correct hints interactively on /boot/loader. You can override hints by making /boot/device.hints also. B-2: suitable hints ... everything goes OK You can override hints by /boot/device.hints. Currently, 'make install' will be aborted in every case above, but this treatment is suitable only for case A. And it would be technically possible to limit this treatment to case A. This treatment will do accoring to Makefile, which is controled by config(8) (src/usr.sbin/config/mkmakefile.c). -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 9:44:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id EA32737B43C for ; Mon, 28 Aug 2000 09:44:12 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 738551C1F; Mon, 28 Aug 2000 09:44:12 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id JAA14936; Mon, 28 Aug 2000 09:44:12 -0700 (PDT) Message-ID: <39AA96DC.B08FABE1@cup.hp.com> Date: Mon, 28 Aug 2000 12:44:12 -0400 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Yevmenkin, Maksim N, CSCIO" Cc: "'George W. Dinolt'" , current@FreeBSD.ORG Subject: Re: Linux ABI no longer supports staroffice References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Yevmenkin, Maksim N, CSCIO" wrote: > [snip] > > same here :( i got original Sun CD with StartOffice 5.1a and tried to > install it. it failed. i used > > # make WITH_CDROM=yes USE_CDROM=yes install > > and everything was fine, but then i got exactly the same error. > XFree86-3.3.6 and XFree86-contrib-3.3.6 both working just fine. > ``xhost +'' did not resolve the problem. Should be fixed already. Please re-cvsup. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10: 0:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 27B0837B423 for ; Mon, 28 Aug 2000 10:00:52 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e7SH0lG10301; Mon, 28 Aug 2000 10:00:47 -0700 Date: Mon, 28 Aug 2000 10:00:47 -0700 From: Brooks Davis To: Mike Meyer Cc: Brooks Davis , current@FreeBSD.ORG Subject: Re: hints static wiring Message-ID: <20000828100047.A10092@Odin.AC.HMC.Edu> References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14762.8323.382969.782508@guru.mired.org>; from mwm@mired.org on Mon, Aug 28, 2000 at 03:19:15AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 03:19:15AM -0500, Mike Meyer wrote: > > I do read cvs-all, and I missed it. Not did I find device.hints in the > relevant Makefiles. Can you provide a pointer to details on how > /boot/device.hints is used in the build process, or how having an > empty one keeps you from shooting yourself in the foot? Having an empty one will not help you, but installing a post hints change GENERIC without a hints file will results in a system that does not boot. Thus you are required to have a hints file. The ability to install a bogus (empty) one is for those who want static hints. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:17:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 9FE1837B42C; Mon, 28 Aug 2000 10:17:25 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA57778; Mon, 28 Aug 2000 10:17:17 -0700 (PDT) (envelope-from obrien) Date: Mon, 28 Aug 2000 10:17:17 -0700 From: "David O'Brien" To: Mike Meyer Cc: Maxim Sobolev , Donn Miller , Brooks Davis , current@FreeBSD.org Subject: Re: hints static wiring Message-ID: <20000828101717.C23712@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> <39AA5DC6.8D73081B@FreeBSD.org> <14762.24829.363032.115605@guru.mired.org> <39AA6699.41E12730@FreeBSD.org> <14762.26659.335.344828@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14762.26659.335.344828@guru.mired.org>; from mwm@mired.org on Mon, Aug 28, 2000 at 08:24:50AM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 08:24:50AM -0500, Mike Meyer wrote: > Well, yeah, I'd expect that. I'm still trying to figure out what > *good* failing to compile unless there's an empty /boot/device.hints The kernel does not fail to *BUILD*. ``make install'' is what fails. I agree that the requirement is somewhat anonying. But, it is better to have this slight anonyance than for many to to install and boot a kernel that would be broken. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:24:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id AEF2F37B422 for ; Mon, 28 Aug 2000 10:24:54 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7SHNoQ04990; Mon, 28 Aug 2000 10:23:50 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma004988; Mon, 28 Aug 2000 10:23:35 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id KAA69738; Mon, 28 Aug 2000 10:23:34 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008281723.KAA69738@bubba.whistle.com> Subject: Re: 5.0-current 20000826 snapshot problems In-Reply-To: <200008280129.SAA42115@pike.osd.bsdi.com> "from John Baldwin at Aug 27, 2000 06:29:39 pm" To: John Baldwin Date: Mon, 28 Aug 2000 10:23:34 -0700 (PDT) Cc: Mike Pritchard , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin writes: > > FreeBSD/i386 bootstrap loader, Revision 0.8 > > (root@usw2.freebsd.org, Sat Aug 26 11:14:35 GMT 2000) > > /kernel text=0x2432ca zf_read: fill error > > > > elf_loadexec: archsw.readin failed > > Your floppy is bad. Try a different one. Not necessarily. This also happens if you try to boot boot.flp instead of kern.flp. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:34:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 212A737B422 for ; Mon, 28 Aug 2000 10:34:30 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA88730; Mon, 28 Aug 2000 11:34:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA02634; Mon, 28 Aug 2000 11:34:13 -0600 (MDT) Message-Id: <200008281734.LAA02634@harmony.village.org> To: Tony Fleisher Subject: Re: hints static wiring Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 27 Aug 2000 22:32:58 PDT." References: Date: Mon, 28 Aug 2000 11:34:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Tony Fleisher writes: : Just a suggestion, but isn't this the type of thing that : should be added to UPDATING? Quoting from the UPDATING file: ... 20000825: /boot/device.hints is now required for installkernel to succeed. ... 20000612: Peter took an axe to config(8). Besure that you read his mail on the topic before even thinking about updating. You will need to create a /boot/device.hints or add a hints directive to your config file to compile them in statically. The format of the config file has changed as well. Please see GENERIC or NEWCARD for examples of the new format. ... Granted, I did commit the first entry only a few hours before you posted... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:37:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E1CEB37B422 for ; Mon, 28 Aug 2000 10:37:48 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA88766; Mon, 28 Aug 2000 11:37:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA02697; Mon, 28 Aug 2000 11:37:32 -0600 (MDT) Message-Id: <200008281737.LAA02697@harmony.village.org> To: mjacob@feral.com Subject: Re: hints static wiring Cc: Mike Meyer , Brooks Davis , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Aug 2000 01:33:18 PDT." References: Date: Mon, 28 Aug 2000 11:37:31 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : > I do read cvs-all, and I missed it. Not did I find device.hints in the : > relevant Makefiles. Can you provide a pointer to details on how : > /boot/device.hints is used in the build process, or how having an : > empty one keeps you from shooting yourself in the foot? : : cvs-all is not appropriate. I am noticing a 3-7 day lag on UPDATING. : Bad. cvs-all *IS*REQUIRED* for all people running -current. UPDATING tries to cull things from there on an as needed basis. It is a service that gets done when I have time. If someone wants to pay me a stipend to drop everything the instant something is committed to the tree and update UPDATING, then the lag will improve. Otherwise, 3-7 days really isn't that bad and will continue to be the case. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:41: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1FAE837B42C for ; Mon, 28 Aug 2000 10:41:02 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA23368; Mon, 28 Aug 2000 10:40:56 -0700 Date: Mon, 28 Aug 2000 10:37:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: Mike Meyer , Brooks Davis , current@FreeBSD.ORG Subject: Re: hints static wiring In-Reply-To: <200008281737.LAA02697@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message Matthew Jacob writes: > : > I do read cvs-all, and I missed it. Not did I find device.hints in the > : > relevant Makefiles. Can you provide a pointer to details on how > : > /boot/device.hints is used in the build process, or how having an > : > empty one keeps you from shooting yourself in the foot? > : > : cvs-all is not appropriate. I am noticing a 3-7 day lag on UPDATING. > : Bad. > > cvs-all *IS*REQUIRED* for all people running -current. UPDATING tries > to cull things from there on an as needed basis. It is a service that > gets done when I have time. If someone wants to pay me a stipend to > drop everything the instant something is committed to the tree and > update UPDATING, then the lag will improve. Otherwise, 3-7 days > really isn't that bad and will continue to be the case. > > Warner Oops- I realize that what I said might have been construed as criticism- not meant at all! What I meant is that while cvs-all can be read by everyone, it's not always obvious from the flood of mail there, or if you're not a developer, what needs to change. In my opinion, people making major changes that require something in UPDATING, should coordinate with you *before* the commit. Only 5 or 6 brain cells are needed for this- I sure wish some of my fellow committers weren't such skinflints in this area. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:43:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 41BFB37B43F for ; Mon, 28 Aug 2000 10:43:06 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA88809; Mon, 28 Aug 2000 11:43:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA02769; Mon, 28 Aug 2000 11:42:49 -0600 (MDT) Message-Id: <200008281742.LAA02769@harmony.village.org> To: Mike Meyer Subject: Re: hints static wiring Cc: Donn Miller , Brooks Davis , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Aug 2000 05:08:42 CDT." <14762.14890.276820.183791@guru.mired.org> References: <14762.14890.276820.183791@guru.mired.org> <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> Date: Mon, 28 Aug 2000 11:42:49 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14762.14890.276820.183791@guru.mired.org> Mike Meyer writes: : Will the system fail to boot if there isn't an empty device.hints : file? If the kernel doesn't have a hints file compiled into it, then you will have problems. However, you may not have a video console. I've been able to boot my laptop with a kernel that had no hints and this was the result. All the PCI based things worked, as did those things that had a PnP ID, except the video console. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:45:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mppsystems.com (mppsystems.com [208.210.148.205]) by hub.freebsd.org (Postfix) with ESMTP id 080CD37B43F for ; Mon, 28 Aug 2000 10:45:14 -0700 (PDT) Received: (from mpp@localhost) by mppsystems.com (8.9.3/8.9.3) id MAA19808; Mon, 28 Aug 2000 12:45:04 -0500 (CDT) (envelope-from mpp) Date: Mon, 28 Aug 2000 12:45:04 -0500 From: Mike Pritchard To: Archie Cobbs Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: 5.0-current 20000826 snapshot problems Message-ID: <20000828124504.A19745@mppsystems.com> References: <200008280129.SAA42115@pike.osd.bsdi.com> <200008281723.KAA69738@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008281723.KAA69738@bubba.whistle.com>; from archie@whistle.com on Mon, Aug 28, 2000 at 10:23:34AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 10:23:34AM -0700, Archie Cobbs wrote: > John Baldwin writes: > > > FreeBSD/i386 bootstrap loader, Revision 0.8 > > > (root@usw2.freebsd.org, Sat Aug 26 11:14:35 GMT 2000) > > > /kernel text=0x2432ca zf_read: fill error > > > > > > elf_loadexec: archsw.readin failed > > > > Your floppy is bad. Try a different one. > > Not necessarily. This also happens if you try to boot boot.flp > instead of kern.flp. It turns out it was a bad floppy, which I didn't even think of because I don't think I've had a bad floppy disk in years and years (plus I had been up all night beating my head on the desk over the whole mess). Thanks to everyone who replied. I'm now typing this message from the machine that I had to do the re-install on, so all is good. -Mike -- Mike Pritchard mpp@FreeBSD.org or mpp@mppsystems.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:46:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A39E637B422 for ; Mon, 28 Aug 2000 10:46:20 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA88853; Mon, 28 Aug 2000 11:46:19 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA02845; Mon, 28 Aug 2000 11:46:04 -0600 (MDT) Message-Id: <200008281746.LAA02845@harmony.village.org> To: mjacob@feral.com Subject: Re: hints static wiring Cc: Mike Meyer , Brooks Davis , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Aug 2000 10:37:19 PDT." References: Date: Mon, 28 Aug 2000 11:46:04 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : In my opinion, people making major changes that require something in : UPDATING, should coordinate with you *before* the commit. Only 5 or : 6 brain cells are needed for this- I sure wish some of my fellow : committers weren't such skinflints in this area. About 10% of the commmits that are known to need an UPDATING entry get sent to me first. About 50%-70% are posted to -current, -stable or committers, which is less well because I get busy.. The remaining entries are not well communicated and could be near the "oops" category. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 10:53:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 4CAE537B43C for ; Mon, 28 Aug 2000 10:53:10 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id KAA03246; Mon, 28 Aug 2000 10:48:46 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008281748.KAA03246@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Archie Cobbs Cc: John Baldwin , Mike Pritchard , current@FreeBSD.ORG Subject: Re: 5.0-current 20000826 snapshot problems In-reply-to: Your message of "Mon, 28 Aug 2000 10:23:34 PDT." <200008281723.KAA69738@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Aug 2000 10:48:46 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > John Baldwin writes: > > > FreeBSD/i386 bootstrap loader, Revision 0.8 > > > (root@usw2.freebsd.org, Sat Aug 26 11:14:35 GMT 2000) > > > /kernel text=0x2432ca zf_read: fill error > > > > > > elf_loadexec: archsw.readin failed > > > > Your floppy is bad. Try a different one. > > Not necessarily. This also happens if you try to boot boot.flp > instead of kern.flp. Only if you've been silly enough to only put *half* of boot.flp on a disk. If it's all there, it works just fine. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 11: 2:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id DAF5837B424; Mon, 28 Aug 2000 11:02:21 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7SI2LQ05561; Mon, 28 Aug 2000 11:02:21 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma005559; Mon, 28 Aug 2000 11:02:18 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id LAA70046; Mon, 28 Aug 2000 11:02:19 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008281802.LAA70046@bubba.whistle.com> Subject: Re: 5.0-current 20000826 snapshot problems In-Reply-To: <200008281748.KAA03246@mass.osd.bsdi.com> "from Mike Smith at Aug 28, 2000 10:48:46 am" To: Mike Smith Date: Mon, 28 Aug 2000 11:02:18 -0700 (PDT) Cc: jhb@pike.osd.bsdi.com, mpp@mppsystems.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > > > /kernel text=0x2432ca zf_read: fill error > > > > > > > > elf_loadexec: archsw.readin failed > > > > > > Your floppy is bad. Try a different one. > > > > Not necessarily. This also happens if you try to boot boot.flp > > instead of kern.flp. > > Only if you've been silly enough to only put *half* of boot.flp on a > disk. If it's all there, it works just fine. 8) Doesn't matter how silly it is -- I can guarantee you that at least one person has done it :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 28 11:22:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id B740937B43C; Mon, 28 Aug 2000 11:22:40 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.net ([24.201.203.136]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G0000083KSVTM@field.videotron.net>; Mon, 28 Aug 2000 14:02:55 -0400 (EDT) Date: Mon, 28 Aug 2000 14:06:08 -0400 (EDT) From: Bosko Milekic Subject: Re: Proposal to clarify mbuf handling rules In-reply-to: <20000827230958.B10714@lanczos.maths.tcd.ie> X-Sender: bmilekic@jehovah.technokratis.com To: David Malone Cc: Archie Cobbs , freebsd-net@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Aug 2000, David Malone wrote: [...] > (This is why the flag I was talking about in the other mail > would be useful for spotting other cases where the storage > may be writable, even if it's not a cluster). Thoughts: 1) The mbuf should be marked read-only explicitly with a single additional M_FLAG. #define M_RDONLY 0x0x2000 2) The flag should be ORed in in MEXT_ADD_REF() only if the ref_cnt is equal to or greater than 2. This is unfortunate because an additional check would have to be introduced.