Latest kernel/module restructuring
With the latest kernel/module restructuring, the kernel is now installed as /boot/kernel/kernel.ko. So, basically, if one opts to _not_ build modules w/kernel as per /etc/make.conf, no modules are installed in /boot/kernel other than the kernel itself, kernel.ko. This means that various modules will not be found at boot time, since they are stored in /boot/kernel.old. To remedy this, I suggest we have an option in /etc/defaults/make.conf to _not_ wipe out any modules in /boot/kernel (except kernel.ko of course) if modules are not built with kernel. Correct me if there already exists such an option. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Compilation problem only in -CURRENT
In trying to create a port, I'm running into the following problem: Everything compiles fine on 3.5 -STABLE (last built on Jul 14), but on -CURRENT (Aug 29) one of the .so files reports: 'Undefined symbol "__pure_virtual"' The port defines USE_NEWGCC, so gcc 2.95.2 19991024 is used on both systems. -- Johann To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem with forwarded connections with OpenSSH/FreeBSD
Does anyone has any idea why forwarded connections (with an entry in .ssh/config or with -L local-port:remote-machine:remote-port) often ends up taking ages to setup ? During that time the connection itself is blocked with some data in the Recv-Q... localhost.euroco.6674 *.*tcp0 0 LISTEN localhost.euroco.1853 localhost.euroco.6674 tcp0 0 ESTABLISHED localhost.euroco.6674 localhost.euroco.1853 tcp 64 0 ESTABLISHED ^^ My entry in .ssh/config is : Host xxx.xxx.xxx Cipher blowfish RhostsAuthentication no RhostsRSAAuthentication no Compression yes CompressionLevel 4 LocalForward 6674 irc.ais.net:6667 It happens with 2.2.0 also. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FIXIT problems with /dev
Kent Hauser wrote: Hi All, I just did something foolhardy -- and yet instructive. Pls let me relate. Longish story about MAKEDEV limitations.. I suggest you become familiar with the chroot command. Regards, Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
bouncebuffers broken ?
On -current trying to do fdwrite kern.flp I get panic: isa_dmastart: bad bounce buffer Can anybody confirm/deny this is a general problem ? The machine is a K7 with 512M RAM -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
boot brokenness...
I just installed a freshly made release. The machine cannot boot :-( FreeBSD/i386 bootstrap loader, Revision 1.0 ([EMAIL PROTECTED], Tue Sep 12 09:49:16 GMT 2000) Loading /boot/defaults/loader.conf Error: stack underflow | can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. ok unload ok boot /kernel Error: stack underflow ok unload ok boot /kernel Error: stack underflow ok boot can't load 'kernel' no bootable kernel ok unload ok load /kernel /kernel text=0x27cf8a data=0x31c7c+0x26ff4 syms=[0x4+0x38720+0x4+0x40117] ok boot 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-2912-PHK #0: Tue Sep 12 10:30:17 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 231776789 Hz ... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CFR: acpi userland manpages
On Sun, Sep 10, 2000 at 07:58:26AM +0900, Mitsuru IWASAKI wrote: Sheldon can probably render an opinion on their usage of the macros. OK, I'm looking forward to see it :-) If he doesn't in the next couple of days (no pressure, Sheldon :-) ) then go ahead and commit. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VMWare on -current, how fast should I expect it to be?
Hi guys, For those of you running VMWare (2) on -current, how fast do you expect it to be? I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the following disk controller / disk atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB FUJITSU MHJ2181AT [35152/16/63] at ata0-master using UDMA33 This is -current from about three weeks ago. It works, but it's a bit slow. Applications themselves run at a reasonable speed, but every now and then (can be as frequent as 10-15 seconds) the guest OS (Windows 98 in this case) will freeze or run very slowly -- the mouse pointer doesn't track properly, keystrokes are queued up. After a couple of second things settle back down, the queued keystrokes and mouse movements manifest in the window, and so on, only to repeat shortly afterwards. I don't have this sort of problem with other apps (unless I load 56 copies of Netscape, naturally). Is this a common issue people are seeing? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, 12 Sep 2000 05:33:10 -0400, Donn Miller wrote: To remedy this, I suggest we have an option in /etc/defaults/make.conf to _not_ wipe out any modules in /boot/kernel (except kernel.ko of course) if modules are not built with kernel. This sounds like a very bad idea, since it encourages folks to use modules which are not synchronized with the running kernel. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
To remedy this, I suggest we have an option in /etc/defaults/make.conf to _not_ wipe out any modules in /boot/kernel (except kernel.ko of course) if modules are not built with kernel. This sounds like a very bad idea, since it encourages folks to use modules which are not synchronized with the running kernel. Some of us rebuild kernels without supping. I, for one, play with all sorts of kernel options to see what they do. When 5.0-stable comes out, a lot of people would like this. Having to rebuild the modules when I want to add USER_LDT to my kernel would be bad. ==ml -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, 12 Sep 2000 10:00:06 -0400, Michael Lucas wrote: Some of us rebuild kernels without supping. I, for one, play with all sorts of kernel options to see what they do. Then you probably want the kernel reinstall target. I don't think that this target is available from src/Makefile.inc1, so you'd have to use the old style of kernel building. If you want something like ``make reinstallkernel'' from /usr/src to work, you should probably ask marcel nicely. But the original proposal was ill-conceived and simply won't cut it. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMWare on -current, how fast should I expect it to be?
Nik Clayton wrote: Hi guys, For those of you running VMWare (2) on -current, how fast do you expect it to be? I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the following disk controller / disk atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB FUJITSU MHJ2181AT [35152/16/63] at ata0-master using UDMA33 This is -current from about three weeks ago. It works, but it's a bit slow. Applications themselves run at a reasonable speed, but every now and then (can be as frequent as 10-15 seconds) use only virtual disks and see if it still happens. I found (on vmware 1) that using the raw disks was a recipe for poor performance. Since we don't have block devices any more, we are screwed in this regard. Virtual disks (files) are however buffered and so can sometimes work faster. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMWare on -current, how fast should I expect it to be?
Julian Elischer ([EMAIL PROTECTED]) wrote: Nik Clayton wrote: Hi guys, For those of you running VMWare (2) on -current, how fast do you expect it to be? I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the following disk controller / disk atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB FUJITSU MHJ2181AT [35152/16/63] at ata0-master using UDMA33 This is -current from about three weeks ago. It works, but it's a bit slow. Applications themselves run at a reasonable speed, but every now and then (can be as frequent as 10-15 seconds) use only virtual disks and see if it still happens. I found (on vmware 1) that using the raw disks was a recipe for poor performance. Since we don't have block devices any more, we are screwed in this regard. Virtual disks (files) are however buffered and so can sometimes work faster. I'm confused... I thought one of the justifications for removing the block devices was "look - Linux doesn't have any." So, if Vmware runs on Linux, and Linux doesn't have any block devices, why would Vmware need block devices? [Of course, I'm speaking in absence of knowledge - does Linux have/not have block devices?] - Dave Rivers - -- [EMAIL PROTECTED] Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: VMWare on -current, how fast should I expect it to be?
I have seen this too ... Let me first ask ... do you use the "suspend/resume" option?? If Yes then :) This caused the same "lockup" every few seconds on my machine too - a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted it worked fine. I guess it is something in VMware that syncs to a resume/suspend state file. You can see this in that the second and there after times you press the suspend button it doesn't say "Saving state" or what ever, it just suspends immediately. So bottom line - I've stopped using the suspend/resume and since then so "hick-ups" every few seconds ... Hope this helps Reinier On 12-Sep-00 Nik Clayton wrote: Hi guys, For those of you running VMWare (2) on -current, how fast do you expect it to be? I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the following disk controller / disk atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB FUJITSU MHJ2181AT [35152/16/63] at ata0-master using UDMA33 This is -current from about three weeks ago. It works, but it's a bit slow. Applications themselves run at a reasonable speed, but every now and then (can be as frequent as 10-15 seconds) the guest OS (Windows 98 in this case) will freeze or run very slowly -- the mouse pointer doesn't track properly, keystrokes are queued up. After a couple of second things settle back down, the queued keystrokes and mouse movements manifest in the window, and so on, only to repeat shortly afterwards. I don't have this sort of problem with other apps (unless I load 56 copies of Netscape, naturally). Is this a common issue people are seeing? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ### # # # R.N. Bezuidenhout NetSeq Firewall # # [EMAIL PROTECTED] http://www.nanoteq.co.za# # # ### -- Date: 12-Sep-00 Time: 16:35:32 This message was sent by XFMail -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, Sep 12, 2000 at 04:04:20PM +0200, Sheldon Hearn wrote: On Tue, 12 Sep 2000 10:00:06 -0400, Michael Lucas wrote: Some of us rebuild kernels without supping. I, for one, play with all sorts of kernel options to see what they do. Then you probably want the kernel reinstall target. I don't think that this target is available from src/Makefile.inc1, so you'd have to use the old style of kernel building. If you want something like ``make reinstallkernel'' from /usr/src to work, you should probably ask marcel nicely. But the original proposal was ill-conceived and simply won't cut it. Hmm, how about those of us doing buildworlds/buildkernels on one (nfs)server for subsequent installworlds/installkernels on multiple other machines? With the current targets, you either have to build modules over and over againg for each `client', or you have to accept that /boot/kernel/* gets nuked when running installkernel (or, as you point out, one can use the old manual scheme). Sheldon. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMWare on -current, how fast should I expect it to be?
On Tue, 12 Sep 2000 10:13:16 -0400 (EDT) Thomas David Rivers [EMAIL PROTECTED] wrote: Julian Elischer ([EMAIL PROTECTED]) wrote: I'm confused... 'fraid so. It is raw devices (for discs) that linux doesn't have, they are all block devices - although I may be out of date it's been a while. So, if Vmware runs on Linux, and Linux doesn't have any block devices, why would Vmware need block devices? Vmware needs buffering for performance. ISTR some discussion when this came up (a while ago) of having buffered devices without block semantics. I'm not sure what came of it. -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMWare on -current, how fast should I expect it to be?
On Tue, Sep 12, 2000 at 02:27:45PM +0100, Nik Clayton wrote: For those of you running VMWare (2) on -current, how fast do you expect it to be? I'm running it on my PIII 366 laptop. It's not great, but it's usable. The biggest factors I've seen effecting performance are memory related. Running out will cause the system to temporarily hang while it pages large chunks of memory in and out. Also, the J option to malloc did really bad things to performance when I had it on. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, 12 Sep 2000 18:11:20 +0200, "Niels Chr. Bank-Pedersen" wrote: Hmm, how about those of us doing buildworlds/buildkernels on one (nfs)server for subsequent installworlds/installkernels on multiple other machines? You run buildkernel once, and then installkernel multiple times. That's if all your machines want the same kernel and modules. If they require different kernels and modules, you'll want something like: master make KERNEL=HOST1 buildkernel master make KERNEL=HOST2 buildkernel master make KERNEL=HOST3 buildkernel host1 make installkernel host2 make installkernel host3 make installkernel With the current targets, you either have to build modules over and over againg for each `client', or you have to accept that /boot/kernel/* gets nuked when running installkernel (or, as you point out, one can use the old manual scheme). Right now, the general feeling seems to be that the options specified in the kernel config might affect the way in which modules for that kernel are built. I don't like this idea, but that's the prevailing wisdom. So yes, you have to build each machine's modules separately. If you agree with me that the prevailing wisdom is stupid, then you can build every kernel after HOST1's with -DNO_MODULES and copy HOST1's modules into the obj dir for the remaining hosts' kernels. You could probably even get away with a symlink. Folks, I agree that it would be nice to have a reinstallkernel target in src/Makefile.inc1. Other than that, it really does sound like everyone's just arguing for the sake of being heard. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
On that subject, can you give me a rough projection as to when 5.0-RELEASE is likely to arrive? FreeBSD 2.2.1 1997-04-xx [FBD] FreeBSD 3.0 1998-10-16 [FBD] FreeBSD 4.0 2000-03-13 [FBD] You forgot FreeBSD 4.1, 2000-07-27 (www.freebsd.org/releases). This makes FreeBSD 4.2 scheduled for 2000-11-xx since we do a release every 4 months (not that anyone asked about 4.2 in this thread, but I saw some other speculation about it which I'll conveniently answer in this one). I'm also not sure where the rumors about a FreeBSD 4.1.5 got started since I'd certainly never planned on such a thing, that, I think, being more the product of wishful thinking on certain security-minded people's behalf after RSA released their code. :-) That said, it's something I'm still contemplating. I need to see what merge-in-progress work is currently underway or certainly people will complain that 4.1.5 should have waited for their own wishlist items rather than being slaved solely to the RSA release event. As to FreeBSD 5.0, I think you can count on that being a mid-summer item for 2001 and certainly not any sooner. There's a lot of work which still needs to be done before we'll be ready for anything like 5.0, given the extent of the SMPng changes planned for that release. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
On Tue, 12 Sep 2000, Jordan Hubbard wrote: I'm also not sure where the rumors about a FreeBSD 4.1.5 got started since I'd certainly never planned on such a thing, that, I think, A certain user called jkh on IRC :-). I asked you and you agreed to it as a net-only release. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No block devices (was: VMWare on -current, how fast should I expect it to be?)
On Tuesday, 12 September 2000 at 10:13:16 -0400, Thomas David Rivers wrote: Julian Elischer ([EMAIL PROTECTED]) wrote: Nik Clayton wrote: Hi guys, For those of you running VMWare (2) on -current, how fast do you expect it to be? I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the following disk controller / disk atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB FUJITSU MHJ2181AT [35152/16/63] at ata0-master using UDMA33 This is -current from about three weeks ago. It works, but it's a bit slow. Applications themselves run at a reasonable speed, but every now and then (can be as frequent as 10-15 seconds) use only virtual disks and see if it still happens. I found (on vmware 1) that using the raw disks was a recipe for poor performance. Since we don't have block devices any more, we are screwed in this regard. Virtual disks (files) are however buffered and so can sometimes work faster. I'm confused... I thought one of the justifications for removing the block devices was "look - Linux doesn't have any." No, that's never been a justification for removing block devices. Linux has block devices but no character disk devices. FWIW, I was never happy with the removal of block devices either. I was shouted down with "can you point to any one use they are?", to which I replied "just because I don't know of one doesn't mean there isn't one, or that there will never be one in the future". This is an example where they could presumably be useful. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
A certain user called jkh on IRC :-). I asked you and you agreed to it as a net-only release. Hmmm. I must have been on drugs. :) Very well, I'll see what can be done. A test release is actually building right now. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
