Re: Kernel preemption, yes or no? (was: Filesystem gets a hugeperformance boost)
IIRC, didn't the NT driver for some NIC (Intel?) switch to polling, anyway, under heavy load? The reasoning being that you _know_ that you're going to get something... why bother an IRQ hit? THis is very interesting. How does this affect performance? JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SSLeay refuses to build.
I am trying to make the port p5-Net-SSLeay-1.05 (as a dependency for webmin). The make stops and askes for the location of OpenSSL. A 'where openssl' results in '/usr/bin/openssl'. The SSLeay build will not accept /usr/bin, /usr/bin/, or /usr/bin/openssl . It always reponds with : "Could not find OpenSSL in /usr/bin" or whatever other Directory I type. Can someone please shed some light on the issue? Thanks, JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SSLeay refuses to build.
No. I will try this right now. I still fail to see why the port would not find the thing. A simple 'where' statement does the trick... I any case, thanks for the help JAn On Sat, 10 Mar 2001, Alfred Perlstein wrote: * [EMAIL PROTECTED] [EMAIL PROTECTED] [010310 10:26] wrote: I am trying to make the port p5-Net-SSLeay-1.05 (as a dependency for webmin). The make stops and askes for the location of OpenSSL. A 'where openssl' results in '/usr/bin/openssl'. The SSLeay build will not accept /usr/bin, /usr/bin/, or /usr/bin/openssl . It always reponds with : "Could not find OpenSSL in /usr/bin" or whatever other Directory I type. Can someone please shed some light on the issue? Did you try '/usr' ? :) -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current paging strategy
what exacly do you mean with critical path, here? JAn On Sun, 5 Nov 2000, Bernd Walter wrote: On Thu, Nov 02, 2000 at 12:45:30AM -0800, David Greenman wrote: Interesting. THis needs about two bytes per page for the counter? Actually, we found that a single byte per page was sufficient. Pages tended to be either heavily accessed or rarely accessed. Even in the unusual case where all pages are frequently accessed, the page reclaim rate (and thus adjustment rate of the page references count) increases high enough to still provide for a decent distribution of the counters and for the page LOU to be effective. One byte sounds good for i386. Maybe it makes sense to have it 4 or 8 byte on risc platforms. I wonder if it's a critical path and if there are more of this in the kernel source. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] 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
Re: Other Linux stuff...
It's not a matter of our emulator. The problem is that Linux allows the execution of shared objects. Technically speaking this is wrong and our ELF loader doesn't do that. We can change our ELF loader, but that would Could you elaborate on this, please. I am interested in what is meant with execution of shared objects (as opposed to programs). Why is this wrong? Thanks, Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
I am not sure, if anybody care for this fix, but I just copied libc.so.5 to libc.so.4 when kde was complaining about not finding it. I am not sure if this should work, but it does work just fine... JAn On Sat, 25 Nov 2000, David O'Brien wrote: On Sat, Nov 25, 2000 at 12:44:34PM -0600, Bill Fumerola wrote: Huh? Why the worst of both worlds?? Incompatible changes AND no way to differentiate between the two. (plus we don't even know what changed it, so we have no way of telling people "your libc before X won't work with binarys that use the frobozz() interface) There wasn't an incompatible change. There is too much confusion on this issue. There were two things that caused a problem. 1. a bug in libc_r such that programs that ran before, crashed. 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. #1 just showed off incorrect application code. #2 has never been officially supported. People who have binaries they can't recompile will need them. The fact that it pains our CVS tree really isn't an issue to me, This is -current, so people should be able to deal with the issue. I'll probably put a 4.2-RELEASE libc.so.4 up for people to download and put in /usr/lib/compat manually. I'd like to think we have software engineering that utilizes source code management, and not the other way around. I would like to think that way too -- but that isn't the truth. As I said, I'm willing to commit a compat lib now, but I don't want any crap when I update it and the diff is the size of the file itself. -- -- David ([EMAIL PROTECTED]) 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
kde2 upgrade fails in wierd fashion
This is strange. I deinstalled all kde11 type ports and then made installed the kde2 port. However, each time I got and startx, I stay with kde 1.1.2. I am using Xfree86 4.01 and a reasonably recent version of CURRENT. Has anybody got an explanation for this behavior? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: slight improvement in locore.s?
It does not impair readability. As long as that is true, I believe its prudent to save every byte possible... Only my 2 cents worth. JAn On Thu, 23 Nov 2000, David Greenman wrote: locore.s includes: #define ALLOCPAGES(foo) \ movlR(physfree), %esi ; \ movl$((foo)*PAGE_SIZE), %eax ; \ addl%esi, %eax ; \ movl%eax, R(physfree) ; \ movl%esi, %edi ; \ movl$((foo)*PAGE_SIZE),%ecx ; \ xorl%eax,%eax ; \ cld ; \ rep ; \ stosb might it be a very slight optimisation to change this to: #define ALLOCPAGES(foo) \ movlR(physfree), %esi ; \ movl$((foo)*PAGE_SIZE), %eax ; \ movl%eax, %ecx ; \ addl%esi, %eax ; \ movl%eax, R(physfree) ; \ movl%esi, %edi ; \ xorl%eax,%eax ; \ cld ; \ rep ; \ stosb ?? Improvement in what way? Readability? I don't think so. Performance? This macro is only used in the initial bootstrap of the kernel. ...changing it might save a few bytes, however. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. 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
state of usb?
What is the current state of the usbd? I keep getting messages that complain about a host controller error and a shutdown of the usb interface. And I don't even have any devices on my usb ports... JAN To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/etc/local/rc.conf not working?
the rc.conf on my computer sets the sendmail enable flag to NO, and yet on bootup the sendmail daemon is started. ps -ax confirms this with sendmail: accepting connections JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/local/rc.conf not working?
OOPs, well this was the problem. That leaves me wondering, why this is on two places... Thanks, JAN On Sun, 19 Nov 2000, Doug Barton wrote: [EMAIL PROTECTED] wrote: the rc.conf on my computer sets the sendmail enable flag to NO, and yet on bootup the sendmail daemon is started. ps -ax confirms this with sendmail: accepting connections Do you actually have the file in /etc/local as the subject of your email suggests? If so, that's your problem. You want to have rc.conf and/or rc.conf.local in /etc/ itself. Good luck, Doug -- Life is an essay test. Long form. Spelling counts. Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fonts won't show in Xfree86
I just reinstalled from the snap server. Now, whenever I go int Xwindows, I get wierd stuff instead of characters. It looks almost as if the fonts have been replaced with barcodes. If I go an move the window such that it is obstructed behind something and then move it back, sometimes the characters reappear correctly. I also just tried this with 4.2 BETA and I get the same problem. I did not have this problem with 4.1. I have a RAGE128 graphics card, in case this helps. Has anybody seen this type of behavior before? Thanks, JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA RAID - sysinstall solution
OK, i tested this. Sysinstall works fine now, and the system installs OK
from the SNAP 5 ftp server. ON reboot, however, the computer thing refuses
to boot of the RAID device. After the BIOS message "verifying
DMI.."(or similar) the system hangs.
Does anybody know why this could be?
jan
On Mon, 6 Nov 2000, [iso-8859-2] Ivan Debnár wrote:
I'm using HTP 370 ATA RAID controller, which should have been supported in
stable and current according to CVS messages from Soren.
But as few of us found, it is not, in fact.
KERNEL recognises device ar0.
4.2 sysinstall does not offer ar0 as disk drive
5.0-current sysinstall offers it, but is not able to create slices on it.
(DEBUG: MakeDev unknown major/minor).
So I looked through sysinstall source and libdisk source and guess what ! -
libdisk doesn't know about ar? devices yet.
Could someone update the libdisk source in stable and current to include the
device?
The files affected are:
/src/lib/libdisk/create_chunk.c
/src/lib/libdisk/disk.c
--- disk.c.orig Thu Sep 14 14:10:45 2000
+++ disk.c Mon Nov 6 23:41:45 2000
@@ -461,7 +461,7 @@
}
#endif
-static char * device_list[] = {"wd", "ad", "da", "wfd", "fla", "idad",
"mlxd", "amrd", "twed", 0};
+static char * device_list[] = {"wd", "ad", "da", "wfd", "fla", "idad",
"mlxd", "amrd", "twed", "ar", 0};
char **
Disk_Names()
--- create_chunk.c.orig Fri Jul 14 08:30:59 2000
+++ create_chunk.c Mon Nov 6 23:46:59 2000
@@ -300,6 +300,8 @@
cmaj = 147, p += 4;
else if (!strncmp(p, "da", 2)) /* CAM support */
cmaj = 13, p += 2;
+else if (!strncmp(p, "ar", 2)) /* ATA RAID */
+ cmaj = 157, p += 2;
else {
msgDebug("MakeDev: Unknown major/minor for devtype %s\n", p);
return 0;
Unfortunately I am not able to compile and try this, but if someone can
create a set of 4-STABLE or 5-CURRENT installation disks and e-mail them,
I'm willing to try.
Those diffs are against 2000-10-30 stable, so they are just to show changes
what I thing should be done to actual current files. This should make
Current install on ATA RAID hopefully. I don't know, if it will make STABLE
sysinstall recognize the ar device. I hope so.
Ivan Debnár
Online Consulting, s.r.o.
tel.://+421 88 4146721
fax://+421 88 4142231
http://www.o-c.sk
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
latest build install disks broken
I tried the latest build from current.freebsd.org. (11-7)
I tried multiple floppies to make sure that it was not a problem with bad
sectors (fdimage should catch this anyway). On boot from the kern.flp
image the computer stops at the boot loader with the message
elf_loadexec: cannot seek
can't load file '/kernel':input/output error
Hit enter to boot immediately, or any other key for command prompt.
{I hit enter}
booting [/kernel]
can't load 'kernel.ko'
Type '?' for a list of commands, 'help' for more detailed help.
ok _
{on 'ls' i get:}
d boot
kernel.gz
Can anybody reproduce this error? I have tried two machines with the same
result.
the image from yesterday, (11-6) works fine.
Jan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
install disk problem
I am installing the current version of freebsd with the install floppies. The installation breaks of with the error message that it cannot create the device in /dev. It seems to me that the ar device entry for the raid I am using is not on the disk by default, and sysinstall is unable to create it. Then again, it could be something else. Has anybody else encountered this problem? JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: making an install CD
I tried this, but the make fails with error install:/usr/obj/usr/src/include/osreldate.h: No such file or directory I just got the brand new current source, rebuilt the world and updated the kernel. If the source file is supposed to be there, its probably missing on the server. Any toughts - am I doing something wrong? Jan On Wed, 1 Nov 2000, Daniel O'Connor wrote: On 01-Nov-00 [EMAIL PROTECTED] wrote: Does anybody have a link to instructions for making an install CD with the 'current' state. Well, you need to have the CVS repo handy for starters, then try cd /usr/src/release make release CHROOTDIR=/some/place/with/space CVSROOT=/my/cvsroot Read the Makefile for handy tips :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current paging strategy
What paging strategy does FreeBSD currently use? Is it LRU or some approximation to it? How much memory does this strategy take up in its current implementation? Thank you for any information or links, Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current paging strategy
Interesting. THis needs about two bytes per page for the counter? JAn On Wed, 1 Nov 2000, David Greenman wrote: What paging strategy does FreeBSD currently use? Is it LRU or some approximation to it? How much memory does this strategy take up in its current implementation? It's probably nothing like anything you've heard of before. It's closest to LOU (least often used). We look at the page's reference flag and increment/decrement a counter depending on it. The rate that we look at the reference flag is also roughly proportional to the rate at which new pages are needed. This algorithm has proven to be extremely effective and does much better than simple LRU. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
making an install CD
I would line to make an Install CD with a non-release kernel and sysinstall. Only the newer software supports the device I want to install on, So I need both the new kernel and sysinstall. Does anybody have a link to instructions for making an install CD with the 'current' state. jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Wierdness with cvsup
I am using cvsup to update my sources. in the supfile, there is a line that states *default compress. The comment above indicates to comment this out when you have a fast connection. I DO have a fast connection (100+ K sustained to ftp.freebsd.org) But when I comment this line out, cvsup indicates a smaller update rate than when I leave it in. Can someone shed light on this? Thanks, JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INVARIANTS and -current
Could someone give a quick explanation what INVARIANTS does?
JAn
On Wed, 1 Nov 2000, Boris Popov wrote:
On Tue, 31 Oct 2000, Eivind Eklund wrote:
I want to enable INVARIANTS by default in -current. This result in some
slowdown, but it also makes it more likely that we'll find bugs quickly.
People that want to run -current should know enough to disable it if it is
in the way, anyway.
Well-reasoned objections welcome.
Yes, running kernel with INVARIANTS is a very good idea (in fact,
my -current setup runs it for over a year now). But this option will
produce inconsistent data structures in the kernel and modules (just like
with SMP case). While it is recommended to avoid modules on -current - I'm
don't agree with this statement because many people use them.
In any way, fix for this is very simple (it assumes that
INVARIANTS defined somewhere in the make.conf or sys.mk):
Index: conf/kmod.mk
===
RCS file: /home/ncvs/src/sys/conf/kmod.mk,v
retrieving revision 1.83
diff -u -r1.83 kmod.mk
--- conf/kmod.mk 2000/09/05 22:37:46 1.83
+++ conf/kmod.mk 2000/09/30 05:55:55
@@ -90,6 +90,10 @@
CFLAGS+= ${COPTS} -D_KERNEL ${CWARNFLAGS}
CFLAGS+= -DKLD_MODULE
+.if defined(INVARIANTS)
+CFLAGS+= -DINVARIANTS
+.endif
+
# Don't use any standard or source-relative include directories.
# Since -nostdinc will annull any previous -I paths, we repeat all
# such paths after -nostdinc. It doesn't seem to be possible to
--
Boris Popov
http://www.butya.kz/~bp/
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
/stand/sysinstall fdisk won't work
After installing the latest version of the current source, /stand/sysinstall's fdisk will not find any devices. Can anybody tell me what I forgot to do? I did do the /dev/MAKEDEV all. JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /stand/sysinstall fdisk won't work
Thank you all for the help JAn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HPT 370 on abit KT7-RAID
This has been discussed here before, but I just got my mainboard and wanted totry this out. The BIOS RAID does not work for me either - no surprise here. So I was trying to use vinum, but disklabel gives me different information than fdisk does. According to the disklabel command, my harddrives are not partitioned at all. This is strange. Can anybody shed some light on this? As far as I know, vinum needs the disklabel assigned to work, so I am stuck. I there a way to override this? I currently have the FreeBSD installed on an old 2GB drive, and wantto use the two 40 GB drives on the ata-100 bus to store /usr on. One last loosely related thing: Does FreeBSD currently support booting off a sofware RAID. I think linux does, but I am trying to avoid that OS. Thanks to anybody who can help. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
