Re: HEADS UP: Destabilization due to SMP development
On Thu, Jun 22, 2000 at 01:56:56PM -0700, Greg Lehey wrote: On Thursday, 22 June 2000 at 10:07:38 -0700, Matthew Dillon wrote: On Mon, Jun 19, 2000 at 05:34:47PM -0700, Matthew Dillon wrote: Ok, I have put up a web page that will track my efforts. http://apollo.backplane.com/FreeBSDSmp/ Your first patchset contains only i386 code. What is the timeframe for alpha relative to i386? Will each i386 code step converted to it a short time later or finally after the i386 code completely has been stabilized? The alpha code is going to be dealt with by the alpha guys. I am not an alpha assembly programmer. There is going to be considerably more breakage for the alpha port in the next month then the i386 port, but hopefully it will get worked out. Hmm. This adds another dependency. We will really need to get the Alpha code in place before we can commit anything. Is there anybody out there who can do this? I think (but am not sure!) that dfr was working on SMP for axp some time ago? -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" [EMAIL PROTECTED] http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing openssl/idea.h?
Building world failed on my machine... (with USA_RESIDENT=NO) Does IDEA stuff compiled by default? I messed this up. Fix coming. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel config format migration script
Cyrille Lefevre wrote: well, at 4.x, FreeBSD sed doesn't support -E, is that GNU sed which support this option or 5.x FreeBSD sed ? for instance, GNU sed port doesn't exists ! Really? Funny. I'm not sure our sed is GNU sed. IIRC, it uses regex(3) instead of gnuregex. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Windows works, for sufficently small values of "works". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: inetd with -R -1 patch?
On Thu, 08 Jun 2000 12:37:00 +0200, Alexander Langer wrote: What about that patch to let one use unlimited numbers of connections? The standard is still 256, but if one really wants that... Personally, I'd prefer it if zero implied an unlimited number of invokations per service per minute. However, the special case isn't really necessary, since you can simply specify some large number (and then prepare to have your box dragged under). :-) Ciao, Sheldon. PS: Did you test the patch you sent? :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building stable from current
On Thu 2000-06-22 (22:12), Kent Hauser wrote: For the last while (several months), whenever I try to build a RELENG_4 release from my -current box, it fails building gcc. As -current is supposed to be "fluid" for the next several months, I wanted to make a set of -current and -stable CDs now. The current build was fine. To build stable I did the following: # cd /usr; rm -rf src.stable;mkdir src.stable # rm -rf /usr/obj/usr/src.stable # su kent % cd src.stable % cvs -R -d /home/ncvs co -r RELENG_4 src % cd src.stable; mv src/* .;rmdir src % make buildworld build.log and it blew up linking cc1plus. I built -stable as me so as to be sure no system files were touched. But I'm also confused as I thought "buildworld" was self-contained -- as long as a reasonably current make was available to jump-start the process. Thoughts corrections greatly welcomed. Can you send the last 50 or so lines of build.log? Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c
On Fri, 23 Jun 2000, Peter Jeremy wrote: ... This has bitten a number of people who have turned softupdates on for their root filesystems - and had installworld die. There is a workaround for this: Before running installworld start a shellscript in background with: while true; do; sync; sleep 2; done; this prevents my root from filling up. Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: inetd with -R -1 patch?
Thus spake Sheldon Hearn ([EMAIL PROTECTED]): Personally, I'd prefer it if zero implied an unlimited number of Yes. Fine, too. invokations per service per minute. However, the special case isn't really necessary, since you can simply specify some large number (and then prepare to have your box dragged under). :-) Heh. That counts for every piece of software where you can set "unlimited" PS: Did you test the patch you sent? :-) Yes. root:~ $ netstat -a | grep localhost.telnet | wc -l 864 (I wasn't able to stress the system more :) However, as I just saw, the -R -1 does not work (I tested it with -DTOOMANY=-1). So -R 0 for unlimited is better (because of strtol). Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c
Peter Wemm [EMAIL PROTECTED] writes: For the NetBSD version to work, what needs to happen is that the -osoftdep flag needs to be propagated to the superblock so that after reboot, fsck knows what to do. When it is next mounted, then update it to the new state. From what I can tell from a quick look at the code, it does this. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
daily/420.status-network rev 1.4
Hi, ---snip--- Index: 420.status-network === RCS file: /big/FreeBSD-CVS/src/etc/periodic/daily/420.status-network,v retrieving revision 1.4 diff -u -r1.4 420.status-network --- 420.status-network 2000/06/23 01:18:23 1.4 +++ 420.status-network 2000/06/23 10:35:41 @@ -18,7 +18,7 @@ echo "" echo "Network interface status:" - case "$daily_status_network_enable" in + case "$daily_status_network_usedns" in [Yy][Ee][Ss]) netstat -i;; *) ---snip--- seems to be the intended version. Bye, Alexander. -- It is easier to fix Unix than to live with NT. http://www.Leidinger.net Alexander+Home @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AGPGART for FreeBSD
Hi, I've just found that somebody ported linux agpgart module (used by the GXL) to FreeBSD. Could someone take a look at it and tell me whether it have a chances to be imported into base system or I should create a port of it. http://utah-glx.sourceforge.net/gart/agpgart-freebsd-2619.tar.gz Thanks! -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Destabilization due to SMP development
Using a non opensource commercial version control system is just to ask for bad carma, extended murphy fields and whatnot in an opensource volounteer project... I would like to understand the discussed weakness of cvs regarding branches. Could someone explain it (in private) or point me to a link? I ask because I had to work a lot with MKS SI (RCS based) and it was OK to manage different branches with it. So I assumed cvs as a kind of successor to rcs is able to do this too. Or do people just like an improved architecture? I understand that systems like Perforce are handling diffs to the code base not file orientated but rather goal orientated which might give a much better overview. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem with normal exit all threads of task...
Hello! I have a problem with normal exit all threads of task by signal... At Linux, as i know, all threads of task receive a signal, but under FreeBSD only one. Any idea? -- Rgdz, Sergey Osokin aka oZZ, [EMAIL PROTECTED] http://www.freebsd.org.ru/~osa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ftp client bug
Hi! There is a problem in ftp client in all FreeBSD versions. It isn't dangerous but probably should be fixed. uname -a FreeBSD work.dv.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #6: Thu Jun 22 19:41:50 MSD 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/WORK i386 ftp localhost Connected to localhost. 220 work.dv.ru FTP server (Version 6.00LS) ready. Name (localhost:dv): 331 Password required for dv. Password: 230 User dv logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp site %s Segmentation fault (core dumped) Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: daily/420.status-network rev 1.4
Hi, Oops - committed - thanks ! ---snip--- Index: 420.status-network === RCS file: /big/FreeBSD-CVS/src/etc/periodic/daily/420.status-network,v retrieving revision 1.4 diff -u -r1.4 420.status-network --- 420.status-network2000/06/23 01:18:23 1.4 +++ 420.status-network2000/06/23 10:35:41 @@ -18,7 +18,7 @@ echo "" echo "Network interface status:" - case "$daily_status_network_enable" in + case "$daily_status_network_usedns" in [Yy][Ee][Ss]) netstat -i;; *) ---snip--- seems to be the intended version. Bye, Alexander. -- It is easier to fix Unix than to live with NT. http://www.Leidinger.net Alexander+Home @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current kernel broken?
On Fri, 16 Jun 2000 20:34:06 -0400, Donn Miller wrote: I saw this as well. It turns out the optimizations I was using when building my kernel was causing it. I was using -march=pentium -Os -pipe. Falling back to -O -pipe solved this. Clearly, the new warning about optimization in make.conf is not enough. We need to burn a huge fiery warning into the console as the kernel loads up that warns about the "non-standard" optimization with which it was compiled. Were you seeing the copyright notice? :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp client bug
hi, there!
On Fri, 23 Jun 2000, Dmitry Valdov wrote:
There is a problem in ftp client in all FreeBSD versions. It isn't dangerous
but probably should be fixed.
uname -a
FreeBSD work.dv.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #6: Thu Jun 22 19:41:50
MSD 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/WORK i386
ftp localhost
Connected to localhost.
220 work.dv.ru FTP server (Version 6.00LS) ready.
Name (localhost:dv):
331 Password required for dv.
Password:
230 User dv logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp site %s
Segmentation fault (core dumped)
that's easy:
--- cmds.c.orig Fri Jun 23 20:12:24 2000
+++ cmds.c Fri Jun 23 19:58:19 2000
@@ -1461,7 +1461,7 @@
len += len1;
}
}
- if (command(buf) == PRELIM) {
+ if (command("%s", buf) == PRELIM) {
while (getreply(0) == PRELIM)
continue;
}
/fjoe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Problems building ports/x11-toolkits/wxGTK
Hello,
I tried to build the wxGTK-2.1.16 port, and noticed that
a few AC_CHECK(..) macros in the configure script
don't work.
The first header file which is not found is
X11/XKBlib.h
because on FreeBSD systems there is no link
/usr/include/X11 - /usr/X11R6/include
(shouldn't there be such a link ? - i heard this is a standard)
The opengl header file GL/gl.h is also not found, and
the link test with "libGL" or "libMesaGL" fails too.
And shouldn't there be a line in the Makefile of the port
which shows how to compile wxGTK with opengl support ?
(it took me an hour to find out how to do this!)
So i would propose to make the following changes to the
ports Makefile:
CONFIGURE_ENV= GTK_CONFIG="${X11BASE}/bin/gtk12-config"\
CCFLAGS="-I/usr/X11R6/include"\
LDFLAGS="-L/usr/X11R6/lib"
CONFIGURE_ARGS= "--with-opengl=yes"
--
email: [EMAIL PROTECTED]
web: http://gul.sourceforge.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Missing openssl/idea.h?
On Fri, 23 Jun 2000 08:36:32 +0200, Mark Murray wrote: Building world failed on my machine... (with USA_RESIDENT=NO) Does IDEA stuff compiled by default? I messed this up. Fix coming. Current sources as of 10H40 on 23 June 2000 build and install without problems (provided one pays attention to the new world order with respect to config(8)). The kernel boots and the system lives at least as long as it took me to type and send this message. :-) I can't find any local deltas in either of src/secure and src/crypto which might influence this. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing dependancies after config changes (atapi)
On Thu, 22 Jun 2000 16:34:13 +0200, Alexander Leidinger wrote: Unfortunally I haven't seen someone else complain about this. Can some reproduce this? Nope, I built an ata + atadisk + atapicd kernel today from sources dated 10H40 on 23 June 2000 without a problem. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Destabilization due to SMP development
"Daniel C. Sobral" wrote: "Jordan K. Hubbard" wrote: Everyone talks about using bitkeeper but none of the people who recommend it have ever actually tried to use it for anything. Before such recommendations will bear weight, this needs to change. :) OCVS? (Or was it OVCS? I can never recall...) I know of at least 4 open source successors to CVS: Eivind Eklund's OVCS http://www.OpenVCS.org/ Josh MacDonald's PRCS http://www.cs.berkeley.edu/~jmacd/prcs.html Jonathan Shapiro's DCMS http://www.eros-os.org/~majordomo/dcms-dev/ tigris.org's Subversion http://subversion.tigris.org/ Of these, PRCS the only one out of the design phase, though it doesn't yet have a client-server mode. Oh yeah, there's Bitkeeper too, but it's not really open source... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems building ports/x11-toolkits/wxGTK
Sorry, it should be:
/usr/include/X11 - /usr/X11R6/include/X11
and
CONFIGURE_ENV= GTK_CONFIG="${X11BASE}/bin/gtk12-config"\
CCFLAGS="-I${X11BASE}/include"\
LDFLAGS="-L${X11BASE}/lib"
Norbert Irmer wrote:
Hello,
I tried to build the wxGTK-2.1.16 port, and noticed that
a few AC_CHECK(..) macros in the configure script
don't work.
The first header file which is not found is
X11/XKBlib.h
because on FreeBSD systems there is no link
/usr/include/X11 - /usr/X11R6/include
(shouldn't there be such a link ? - i heard this is a standard)
The opengl header file GL/gl.h is also not found, and
the link test with "libGL" or "libMesaGL" fails too.
And shouldn't there be a line in the Makefile of the port
which shows how to compile wxGTK with opengl support ?
(it took me an hour to find out how to do this!)
So i would propose to make the following changes to the
ports Makefile:
CONFIGURE_ENV= GTK_CONFIG="${X11BASE}/bin/gtk12-config"\
CCFLAGS="-I/usr/X11R6/include"\
LDFLAGS="-L/usr/X11R6/lib"
CONFIGURE_ARGS= "--with-opengl=yes"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Missing openssl/idea.h?
On Fri 2000-06-23 (16:31), Sheldon Hearn wrote: Current sources as of 10H40 on 23 June 2000 build and install without problems (provided one pays attention to the new world order with respect to config(8)). The kernel boots and the system lives at least as long as it took me to type and send this message. :-) I can't find any local deltas in either of src/secure and src/crypto which might influence this. Do you have "WITH_IDEA" set? I had to manually set CFLAGS+= -DNO_IDEA in secure/libssh, secure/ssh, secure/ssh-keygen, and secure/sshd's Makefile from about 6 hours ago or so. (well, a .if !defined(WITH_IDEA) CFLAGS+=-DNO_IDEA .endif ) Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing openssl/idea.h?
On Fri, 23 Jun 2000 16:46:34 +0200, Neil Blakey-Milner wrote: Do you have "WITH_IDEA" set? I had to manually set CFLAGS+= -DNO_IDEA in secure/libssh, secure/ssh, secure/ssh-keygen, and secure/sshd's Makefile from about 6 hours ago or so. I don't think so... $ grep IDEA /etc/make.conf /etc/defaults/make.conf $ Where is it defined, or am I looking in the right place? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -e option to umount?
[I think this thread belongs only on -current for the moment. Please followup there.] On Thu, Jun 22, 2000 at 01:44:47PM -0700, Brian Fundakowski Feldman wrote: For what it's worth, there's a port, ports/sysutils/eject, which is made to do this. I'm not one to deny a simple feature in the base system, though, even if this feature is not /really/ that simple. There are two problems with ports/sysutils/eject: = It uses only CDIOCEJECT, which will not work for all removable media (e.g. SCSI disks, tapes). = It tries to unmount the device after ejecting it. This doesn't make since for all devices. Even for those that it _does_ make sense, it can be hard to correctly determine how (by what name) the device is mounted. So I wrote a simple utility that ejects media as follows: = Check to see if the given device is known to cam, and if so use camlib to eject it. = If that doesn't work, try the CDIOCEJECT ioctl. = If that didn't work, give up. It is available as a port at: http://www.nectar.com/freebsd/neject.tar Included in the port distfile is a patch (umount.patch) that adds a `-e' option to umount. If you use it, then umount will run eject for each local filesystem that is unmounted. I figure umount should call eject, rather than the other way around, since umount already knows the device name and mount point. I actually think that there should be load/eject media ioctls defined that are not specific to CDs. I'll post a separate message to that effect on -current. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
comments wanted: media load/eject ioctls (was Re: -e option to umount?)
We've had a CDIOCEJECT ioctl `forever'. Several drivers support it, such as cd, acd, and wfd. However, there are other drivers that support removable media but do not support CDIOCEJECT: da and sa. Likewise we have CDIOCCLOSE which should cause a device to load its media. I want to add these ioctls to da and sa [1]. I don't like the CDIO name, though. I'd like to give these ioctls a different name. I'm not sure what header file might be appropriate for them. I'd like to keep the new ioctls binary-compatible with CDIOC(EJECT|CLOSE)-- i.e. use ioctls 24 28. Or maybe I'm the only one who wouldn't like to invoke the name CDIOCEJECT to unload a tape :-) Thanks, -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] [1] Are there other drivers which should support media load/eject, that do not already? Do any systems have system-ejectable PC cards for example (never seen such myself)? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Destabilization due to SMP development
On Thu, 22 Jun 2000, Greg Lehey wrote: On Thursday, 22 June 2000 at 10:07:38 -0700, Matthew Dillon wrote: On Mon, Jun 19, 2000 at 05:34:47PM -0700, Matthew Dillon wrote: Ok, I have put up a web page that will track my efforts. http://apollo.backplane.com/FreeBSDSmp/ Your first patchset contains only i386 code. What is the timeframe for alpha relative to i386? Will each i386 code step converted to it a short time later or finally after the i386 code completely has been stabilized? The alpha code is going to be dealt with by the alpha guys. I am not an alpha assembly programmer. There is going to be considerably more breakage for the alpha port in the next month then the i386 port, but hopefully it will get worked out. Hmm. This adds another dependency. We will really need to get the Alpha code in place before we can commit anything. Is there anybody out there who can do this? If neither Doug nor Andrew have volunteered for this, I'll take it on. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing dependancies after config changes (atapi)
On Fri, 23 Jun 2000 16:34:12 +0200, Sheldon Hearn wrote: Nope, I built an ata + atadisk + atapicd kernel today from sources dated 10H40 on 23 June 2000 without a problem. GMT Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing openssl/idea.h?
On Fri, 23 Jun 2000 16:31:51 +0200, Sheldon Hearn wrote: Current sources as of 10H40 on 23 June 2000 build and install without problems [...] GMT Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
: usb tty and modems aren't supported, as far as I know. : : They're "nearly" there, AFAIR. I sent Nick some code a while back that : addressed the last problem I understood he had. I'll have to ask him about it then. Picked it up, looked at it, got distracted by Reality and must have dropped it again. I wish Reality would just back off for a while... Yes, the driver is here and it seems to work according to Mike Meyer (IIRC), he's fixed up a few other bits and pieces and I am ready to commit it, but I haven't had time to test it yet. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing dependancies after config changes (atapi)
On 23 Jun, Sheldon Hearn wrote: Unfortunally I haven't seen someone else complain about this. Can some reproduce this? Nope, I built an ata + atadisk + atapicd kernel today from sources dated 10H40 on 23 June 2000 without a problem. Strange... I haven't anything modified in my local tree which could result in such behavior: ---snip--- (24) root@ttyp1# grep ^M /usr/src/update.log M sbin/dump/dumprmt.c M sbin/dump/itime.c M sbin/dump/main.c M sbin/dump/optr.c M sbin/dump/tape.c M sbin/restore/dirs.c M sbin/restore/symtab.c M sbin/restore/tape.c M sys/kern/kern_exec.c Merging differences between 1.13 and 1.14 into forward.c M usr.bin/tail/tail.c M usr.sbin/ntp/config.h M usr.sbin/ntp/ntpd/Makefile ---snip--- Thanks, Alexander. -- The dark ages were caused by the Y1K problem. http://www.Leidinger.net Alexander+Home @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c
: :Right, but if mounting with -osoftdep, does what a "tunefs -n enable" :does (and vice versa) fsck will have that knowledge and the tunefs :step would be un-needed. : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 Slight problem: We've run out of mount option flags. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AGPGART for FreeBSD
--- Maxim Sobolev [EMAIL PROTECTED] wrote: Hi, I've just found that somebody ported linux agpgart module (used by the GXL) to FreeBSD. Could someone take a look at it and tell me whether it have a chances to be imported into base system or I should create a port of it. http://utah-glx.sourceforge.net/gart/agpgart-freebsd-2619.tar.gz I haven't looked at the code yet but there is really no need for this since the AGP driver which I committed to -current last week should work just fine for most reasonable uses. I will be merging this driver to 4.x as soon as it gets more testing in -current. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing dependancies after config changes (atapi)
On Fri, 23 Jun 2000 18:21:48 +0200, Alexander Leidinger wrote: Strange... I haven't anything modified in my local tree which could result in such behavior: Too much is going on right now for any one success datapoint to convince you that everything's fine. :-) Check all the usual culprits (blow away kernel and userland obj trees, watch your optimizations etc) and if it still doesn't work for you, by then maybe someone else will be seeing your problem. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AGPGART for FreeBSD
Doug Rabson wrote: --- Maxim Sobolev [EMAIL PROTECTED] wrote: Hi, I've just found that somebody ported linux agpgart module (used by the GXL) to FreeBSD. Could someone take a look at it and tell me whether it have a chances to be imported into base system or I should create a port of it. http://utah-glx.sourceforge.net/gart/agpgart-freebsd-2619.tar.gz I haven't looked at the code yet but there is really no need for this since the AGP driver which I committed to -current last week should work just fine for most reasonable uses. I will be merging this driver to 4.x as soon as it gets more testing in -current. Ah, well. Stupid question probably: are the linux newagpgart and our agp the same thing functionally or not? Looking at ioctls in include files it seems to me that answer is yes, but why then different names? -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Extend test and expr to 64 bit integers
These simple changes make "test" and "expr" operate on 64 bit
integers (tested on i86 only, but I plan to test them on Alpha
next week).
Motivation:
I recently found a third party shell skript, which used "test"
to verify the (numeric) match of a checksum. The algorithm
worked on unsigned integers, and thus "test" failed when the
checksum happened to come out MAXINT ...
Interestingly, the built in test command in Bash seemed to work,
but when I performed a few tests, I've got the impression, that
bash just silently fails! (Try "test 30 -lt 31"
and "test 30 -gt 31" in Bash ... :)
Obvious cost of my proposed changes is a little processing overhead
(diminishing if compared to the cycles spent loading test or expr).
But there are other issues that I'm worried about:
1) I choose "quad_t" for long integers. Is this a good choice ?
In the kernel I'd use int64_t, but I'm not sure what is most
appropriate here.
2) There is a new dependency on sys/types.h in test.c (for any
of our 64 bit integer types).
3) The changes to "expr" rely on 32 bit integers being promoted
to 64 bit integers in function calls (actually only invocations
of make_integer().) This is in contrast to the old code, which
strictly conformed to KR C. I can fix the need for an implicit
conversion by adding casts in all invocations of make_intereger().
Any opinios ?
What does Posix say about these programs ?
Regards, STefan
Index: /usr/src/bin/test/test.c
===
RCS file: /usr/cvs/src/bin/test/test.c,v
retrieving revision 1.29
diff -u -2 -r1.29 test.c
--- /usr/src/bin/test/test.c1999/12/28 09:34:57 1.29
+++ /usr/src/bin/test/test.c2000/06/23 15:56:26
@@ -154,4 +154,6 @@
static int isoperand __P((void));
static int getn __P((const char *));
+static quad_t getq __P((const char *));
+static int intcmp __P((const char *, const char *));
static int newerf __P((const char *, const char *));
static int olderf __P((const char *, const char *));
@@ -299,15 +301,15 @@
return strcmp(opnd1, opnd2) 0;
case INTEQ:
- return getn(opnd1) == getn(opnd2);
+ return intcmp(opnd1, opnd2) == 0;
case INTNE:
- return getn(opnd1) != getn(opnd2);
+ return intcmp(opnd1, opnd2) != 0;
case INTGE:
- return getn(opnd1) = getn(opnd2);
+ return intcmp(opnd1, opnd2) = 0;
case INTGT:
- return getn(opnd1) getn(opnd2);
+ return intcmp(opnd1, opnd2) 0;
case INTLE:
- return getn(opnd1) = getn(opnd2);
+ return intcmp(opnd1, opnd2) = 0;
case INTLT:
- return getn(opnd1) getn(opnd2);
+ return intcmp(opnd1, opnd2) 0;
case FILNT:
return newerf (opnd1, opnd2);
@@ -442,4 +444,46 @@
return (int) r;
+}
+
+/* atoi with error detection and 64 bit range */
+static quad_t
+getq(s)
+ const char *s;
+{
+ char *p;
+ quad_t r;
+
+ errno = 0;
+ r = strtoq(s, p, 10);
+
+ if (errno != 0)
+ errx(2, "%s: out of range", s);
+
+ while (isspace((unsigned char)*p))
+ p++;
+
+ if (*p)
+ errx(2, "%s: bad number", s);
+
+ return r;
+}
+
+static int
+intcmp (s1, s2)
+ const char *s1, *s2;
+{
+ quad_t q1, q2;
+
+
+ q1 = getq(s1);
+ q2 = getq(s2);
+
+ if (q1 q2)
+ return 1;
+
+ if (q1 q2)
+ return -1;
+
+ return 0;
}
Index: /usr/src/bin/expr/expr.y
===
RCS file: /usr/cvs/src/bin/expr/expr.y,v
retrieving revision 1.14
diff -u -2 -r1.14 expr.y
--- /usr/src/bin/expr/expr.y1999/08/27 23:14:22 1.14
+++ /usr/src/bin/expr/expr.y2000/06/23 16:21:13
@@ -14,5 +14,7 @@
#include ctype.h
#include err.h
-
+#include sys/types.h
+#include regex.h
+
enum valtype {
integer, numeric_string, string
@@ -23,5 +25,5 @@
union {
char *s;
- int i;
+ quad_t i;
} u;
} ;
@@ -88,5 +90,5 @@
struct val *
make_integer (i)
-int i;
+quad_t i;
{
struct val *vp;
@@ -140,9 +142,9 @@
-int
+quad_t
to_integer (vp)
struct val *vp;
{
- int i;
+ quad_t i;
if (vp-type == integer)
@@ -153,5 +155,5 @@
/* vp-type == numeric_string, make it numeric */
- i = atoi(vp-u.s);
+ i = strtoq(vp-u.s, (char**)NULL, 10);
free (vp-u.s);
vp-u.i = i;
@@ -174,5 +176,5 @@
}
- sprintf (tmp, "%d", vp-u.i);
+ sprintf (tmp, "%lld", vp-u.i);
vp-type = string;
vp-u.s = tmp;
@@ -240,5 +242,5 @@
if (result-type == integer)
- printf ("%d\n", result-u.i);
+ printf ("%lld\n", result-u.i);
else
printf
Gnome INSANE shared memory usage
This is a plea for help. I used to have a problem with Gnome - it ate up all of my SysV shared memory. My window manager (sawmill) 's title bars would come up blank because of this. I eventualy found the "use MIT-SHM" checkbox in the imlib settings and turned it off, and the problem mostly went away. I have recently upgraded to Gnome 1.2 and it has come back with a vengence. The checkbox no longer has any effect. I have bumped up the amount of shared memory, but it all gets used, no matter how much is available. It is driving me crazy. I can't run other programs (samba, fxtv) because there is never any shared memory left. Something is eating it all - gnome, gtk, imlib, I don't know how these pieces fit together or exactly where the fault lies. I am desperately looking for a solution that doesn't involve just giving up this very pleasant and otherwise useful software. I have asked a co-worker who also runs Gnome on FreeBSD to check his shared memory usage, and it was fine. The only difference is that I am running -current and he has 4.0-release. I can't find any evidence that I am not the only person on the planet having this problem, but I am completely out of ideas. Does anyone know what's going on here? Look at this output of "icps -mbop", it's ridiculous: Shared Memory: T ID KEYMODE OWNERGROUP NATTCH SEGSZ CPID LPID m 655365432010 --rwa--pgsqlpgsql 2120246246 m 655375432001 --rw---pgsqlpgsql 2 1063936246246 m 655385432007 --rw---pgsqlpgsql 2 96424246246 m 196611 0 --rw-r--r-- rootwheel 7 4096324599 m 262148 0 --rwarwarwachrischris 2 65536410324 m 262149 0 --rwarwarwachrischris 2 65536408324 m 1441798 0 --rw-r--r-- rootwheel 15 4096324 5409 m 1441799 0 --rwarwarwachrischris 2 65536410324 m 262152 0 --rwarwarwachrischris 2 65536410324 m 262153 0 --rwarwarwachrischris 2 65536408324 m 196618 0 --rwarwarwachrischris 2 65536410324 m 131083 0 --rwarwarwachrischris 2 65536402324 m 131084 0 --rwarwarwachrischris 2 65536402324 m 131085 0 --rwarwarwachrischris 2 65536402324 m 131086 0 --rwarwarwachrischris 2 65536402324 m 131087 0 --rwarwarwachrischris 2 65536402324 m 131088 0 --rwarwarwachrischris 2 65536402324 m 131089 0 --rwarwarwachrischris 2 65536400324 m 131090 0 --rwarwarwachrischris 2 65536400324 m 131091 0 --rwarwarwachrischris 2 65536400324 m 131092 0 --rwarwarwachrischris 2 65536400324 m 131093 0 --rwarwarwachrischris 2 65536400324 m 131094 0 --rwarwarwachrischris 2 65536400324 m 131095 0 --rw-r--r-- rootwheel 3 4096324563 m 131096 0 --rwarwarwachrischris 2 65536408324 m 131097 0 --rwarwarwachrischris 2 65536410324 m 131098 0 --rwarwarwachrischris 2 65536408324 m 131099 0 --rwarwarwachrischris 2 65536410324 m 131100 0 --rwarwarwachrischris 2 65536408324 m 131101 0 --rwarwarwachrischris 2 65536408324 m 131102 0 --rwarwarwachrischris 2 65536412324 m 131103 0 --rwarwarwachrischris 2 65536412324 m 131104 0 --rwarwarwachrischris 2 65536412324 m 131105 0 --rwarwarwachrischris 2 65536412324 m 131106 0 --rwarwarwachrischris 2 65536412324 m 65571 0 --rwarwarwachrischris 2 65536412324 m 65572 0 --rw-r--r-- rootwheel 6 4096324599 m 65573 0 --rw-r--r-- rootwheel 8 4096324400 m 65574 0 --rw-r--r-- rootwheel 11 4096324 12638 m 196647 0 --rwarwarwachrischris 2 32768548324 m 196648 0 --rwarwarwachrischris 2 32768548324 m 196649 0 --rwarwarwachrischris 2 32768548324 m 196650 0 --rwarwarwachrischris 2 32768548324 m 196651 0 --rwarwarwachrischris 2 32768548324 m 196652 0 --rwarwarwachrischris 2 32768548324 m 196653 0 --rwarwarwachrischris 2 32768567324 m 262190 0
Re: Gnome INSANE shared memory usage
Christopher Masto wrote: This is a plea for help. I used to have a problem with Gnome - it ate up all of my SysV shared memory. My window manager (sawmill) 's title bars would come up blank because of this. I eventualy found the "use MIT-SHM" checkbox in the imlib settings and turned it off, and the problem mostly went away. I have recently upgraded to Gnome 1.2 and it has come back with a vengence. The checkbox no longer has any effect. I have bumped up the amount of shared memory, but it all gets used, no matter how much is available. It is driving me crazy. I can't run other programs (samba, fxtv) because there is never any shared memory left. Something is eating it all - gnome, gtk, imlib, I don't know how these pieces fit together or exactly where the fault lies. I am desperately looking for a solution that doesn't involve just giving up this very pleasant and otherwise useful software. I have asked a co-worker who also runs Gnome on FreeBSD to check his shared memory usage, and it was fine. The only difference is that I am running -current and he has 4.0-release. Hmm, where my crystal ball... Aha, I see - probably you are using Xfree 4.0, while your friend Xfree3.5*. It is where the problem lie (see below). I can't find any evidence that I am not the only person on the planet having this problem, but I am completely out of ideas. Does anyone know what's going on here? Look at this output of "icps -mbop", it's ridiculous: Some time ago I've answered question like this, so let me quote myself: Subject: Re: Shared memory changes in current? Date: Tue, 06 Jun 2000 15:32:19 +0300 From: Maxim Sobolev [EMAIL PROTECTED] To: Alexander Sanda [EMAIL PROTECTED] "It has noting to do with kernel/gnome. XFree 4.0 is known to be very hungry for the shared memory, so you should increase SHMSEG parameter in your kernel config file. There are no guidelines as to what exact number will be sufficient, so you should define it in experimental way. I personally set it to 100 (options SHMSEG=100) and do not see any warnings anymore." -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing openssl/idea.h?
I can't find any local deltas in either of src/secure and src/crypto which might influence this. Do you have "WITH_IDEA" set? I had to manually set CFLAGS+= -DNO_IDEA in secure/libssh, secure/ssh, secure/ssh-keygen, and secure/sshd's Makefile from about 6 hours ago or so. The real fix is to set it in src/secure/Makefile.inc. (And your fix is incomplete - it must check for "yes"). I'll fix. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, Jun 23, 2000 at 08:22:00PM +0300, Maxim Sobolev wrote: Hmm, where my crystal ball... Aha, I see - probably you are using Xfree 4.0, while your friend Xfree3.5*. It is where the problem lie (see below). That is correct. "It has noting to do with kernel/gnome. XFree 4.0 is known to be very hungry for the shared memory, so you should increase SHMSEG parameter in your kernel config file. There are no guidelines as to what exact number will be sufficient, so you should define it in experimental way. I personally set it to 100 (options SHMSEG=100) and do not see any warnings anymore." Unfortunately, these are my current settings: options SHMALL=1025 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=256 options SHMSEG=128 I can increase it more, but I think this is quite a ridiculous amount of shared memory to be using. Something must be wrong. I am now searching for a way to disable the MIT-SHM extension in the X server, but I think I may have to recompile. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c
On 2000-06-23 09:41 -0700, Matthew Dillon [EMAIL PROTECTED] wrote:
Slight problem: We've run out of mount option flags.
But there already ist MNT_SOFTDEP in sys/mount.h ...
#define MNT_SUIDDIR 0x0010 /* special handling of SUID on dirs */
#define MNT_SOFTDEP 0x0020 /* soft updates being done */
#define MNT_NOSYMFOLLOW 0x0040 /* do not follow symlinks */
Hmmm, just checked in ufs/ffs/fs.h and found that the soft-updates state
is already kept in the fs_flags element of struct fs (the super-block).
/*
* Super block for an FFS file system.
*/
struct fs {
...
int8_t fs_flags; /* see FS_ flags below */
...
};
/*
* Filesystem flags.
*/
#define FS_UNCLEAN0x01/* filesystem not clean at mount */
#define FS_DOSOFTDEP 0x02/* filesystem using soft dependencies */
And in fsck/setup.c, I found:
bufinit();
if (sblock.fs_flags FS_DOSOFTDEP)
usedsoftdep = 1;
else
usedsoftdep = 0;
return (1);
So its obvious, that we could make "-o softdep" a mount option, do away
with the tunefs option, and have the *kernel* record the use of soft-updates
on a R/W mounted file system when it marks the file system FS_UNCLEAN in
the fs_flags files in the super-block. If a file system is unmounted
cleanly, the FS_DOSOFTDEP flag can be cleared along with the FS_UNCLEAN
bit, since the next mount is free to decide whether to use soft-updates
or not.
This is more safe than the tunefs method, since FS_DOSOFTDEP will only be
set if the last R/W mount was on a kernel that supported soft-updates ...
Only problem I see (but that is not different from the current situation)
is that "mount -u" can't change the soft-updates state, if a file-system
is mounted R/W. This should probably be inforced in the kernel (not the
mount command) and there should be *no* way to "force" mount to override
this lock.
Regards, STefan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, Jun 23, 2000 at 01:22:00PM EDT Christopher Masto wrote: This is a plea for help. I used to have a problem with Gnome - it ate up all of my SysV shared memory. My window manager (sawmill) 's title bars would come up blank because of this. I eventualy found the "use MIT-SHM" checkbox in the imlib settings and turned it off, and the problem mostly went away. I have recently upgraded to Gnome 1.2 and it has come back with a vengence. The checkbox no longer has any effect. I have bumped up the amount of shared memory, but it all gets used, no matter how much is available. It is driving me crazy. I can't run other programs (samba, fxtv) because there is never any shared memory left. Something is eating it all - gnome, gtk, imlib, I don't know how these pieces fit together or exactly where the fault lies. I am desperately looking for a solution that doesn't involve just giving up this very pleasant and otherwise useful software. I have asked a co-worker who also runs Gnome on FreeBSD to check his shared memory usage, and it was fine. The only difference is that I am running -current and he has 4.0-release. Hmm, where my crystal ball... Aha, I see - probably you are using Xfree 4.0, while your friend Xfree3.5*. It is where the problem lie (see below). Here, I'm not running Gnome or -current, but I am running sawfish (sawmill) and Xfree 4.0: ~% uname -v FreeBSD 4.0-STABLE #13: Wed Jun 21 13:48:15 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/NIGHTRAIN ~% X -version XFree86 Version 4.0 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 8 March 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 4.0-CURRENT i386 [ELF] Module Loader present ~% sawfish --version sawfish version 0.27.1 ~% uptime 2:12PM up 16:43, 5 users, load averages: 0.85, 0.77, 0.72 ~% ipcs -mbop Shared Memory: T ID KEYMODE OWNERGROUP NATTCH SEGSZ CPID LPID m 262144 0 --rw-r--r-- rootusers 6 4096285 11546 m 327681 0 --rw-r--r-- rootusers 5 4096285 11546 m 196610 0 --rw-r--r-- rootusers 5 4096285 11546 m 196611 0 --rw-r--r-- rootusers 2 4096285 309 m 131076 0 --rw-r--r-- rootusers 2 4096285 309 m 4063237 0 --rw-r--r-- rootusers 2 4096285 308 m 4456454 0 --rw-r--r-- rootusers 4 4096285 308 m 131092 0 --rw-r--r-- rootusers 2 4096285 11766 PID 11546 is an xterm, as is 308. 309 is sawfish. 11766 has gone away. I have not had any of the problems he's describing. I have never modified my shared memory settings in my kernel config either. If the problem is indeed Xfree 4.0, then I guess it must be a driver issue (I'm using the neomagic driver). -- Shawn Halpenny |Maniacal@I Ache, Ohm| "Universal Danger!" +- - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - \ | vi:G3kfM~lxfAPXh~l~2x2FirllpfcxlrifaprmfOX~Xp2hr.lrcelyl2p - - - - - - - -|fU~X~refsPprnlxppri2lxlpr,pFrpprrfaPlpfiprgllxp~3Xlpfndw To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, Jun 23, 2000 at 02:30:42PM -0400, Shawn Halpenny wrote: I have not had any of the problems he's describing. I have never modified my shared memory settings in my kernel config either. If the problem is indeed Xfree 4.0, then I guess it must be a driver issue (I'm using the neomagic driver). I think you may have a point there. While trying to find out whether XFree86 had an option to disable the MIT-SHM extension (it doesn't as far as I could tell - I ended up editing the binary and NOPping it out) I noticed that some of the code seems to be in the hardware driver area. I'm using a dual-headed configuration with a Voodoo 3 and a Number Nine (S3 ViRGE VX). -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, 23 Jun 2000, Christopher Masto wrote: Unfortunately, these are my current settings: options SHMALL=1025 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=256 options SHMSEG=128 I can increase it more, but I think this is quite a ridiculous amount of shared memory to be using. Something must be wrong. I have recently seen the same thing with 4.0-STABLE and XF86-4.0. I found that I had to up both SHMSEG and SHMMAXPGS. Specifically, on each machine setting SHMSEG to 100 and SHMMAXPGS to 2048 did the trick. I think that besides using many separate shared memory segments, the segments themselves are somewhat large. Seeing as how XF86-4 is in everyone's future, is there any reason not to nip these sort of problems now and up increase the default values for SHMSEG and SHMMAXPGS? The amount of additional kernel memory required is negligable for modern systems. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, 23 Jun 2000, Shawn Halpenny wrote: I have not had any of the problems he's describing. I have never modified my shared memory settings in my kernel config either. If the problem is indeed Xfree 4.0, then I guess it must be a driver issue (I'm using the neomagic driver). You are running sawfish, and I'm willing to bet a not very graphics intensive config at that. Try running enlightenment with the default config. The problem may not be solely attributable to XF86-4, but rather a combination of XF86-4 and imlib's aggressive use of shared memory. I suspect if you select a window manager with more eye-candy, you'll see the same results. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
Nick Hibma writes: Yes, the driver is here and it seems to work according to Mike Meyer (IIRC), he's fixed up a few other bits and pieces and I am ready to commit it, but I haven't had time to test it yet. I've still got the problems I reported to the bsd-usb list, but I suspect those are specific to my modem, not umodem. I've been updating my development box to -current, along with creating space so I can install Win98 on a second disk to investigate this some more. Unfortunately, I probably won't be able to look into it for a couple of weeks, as Reality is about to make a serious intrustion. It's a lot better than what's in the tree now, and I'd certainly like to see it committed. Thanx, mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 4:00 PM -0400 6/23/00, Kelly Yancey wrote: On Fri, 23 Jun 2000, Shawn Halpenny wrote: I have not had any of the problems he's describing. I have never modified my shared memory settings in my kernel config either. If the problem is indeed Xfree 4.0, then I guess it must be a driver issue (I'm using the neomagic driver). You are running sawfish, and I'm willing to bet a not very graphics intensive config at that. Note that Chris (who posted the original message) is also running sawmill/sawfish... (they are the same thing, right?) --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, Jun 23, 2000 at 08:22:00PM +0300, Maxim Sobolev wrote: Hmm, where my crystal ball... Aha, I see - probably you are using Xfree 4.0, while your friend Xfree3.5*. It is where the problem lie (see below). Well, I use XFree86 4.0 with two displays, and GNOME 1.2, and I don't have the kind of usage that Christopher has. [just trying to halt a possible goose chase] -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 16:30 23.06.2000 -0400, Garance A Drosihn wrote: modified my shared memory settings in my kernel config either. If the problem is indeed Xfree 4.0, then I guess it must be a driver issue (I'm using the neomagic driver). You are running sawfish, and I'm willing to bet a not very graphics intensive config at that. Note that Chris (who posted the original message) is also running sawmill/sawfish... (they are the same thing, right?) Same here. Latest sawfish, and yes, they're the same. The name was changed from sawmill to sawfisch because of some trademark/copyright problems. I'am ready to try another WM and see whether the SHM problems stay or not (other solutions didn't exactly work, I _dramatically_ increased all the SHM limits in the kernel but still get tons of shm errors from imlib or gdk). Yet, I still see excessive shm usage in the output of ipcs (similar to the output reported by the original poster). BTW: It's for sure _not_ a -current issue and might have nothing to do with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with Xfree 4.0 and Gnome 1.2. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, 23 Jun 2000, Jacques A . Vidrine wrote: On Fri, Jun 23, 2000 at 08:22:00PM +0300, Maxim Sobolev wrote: Hmm, where my crystal ball... Aha, I see - probably you are using Xfree 4.0, while your friend Xfree3.5*. It is where the problem lie (see below). Well, I use XFree86 4.0 with two displays, and GNOME 1.2, and I don't have the kind of usage that Christopher has. I don't think it is gnome per-se. Just switching from WindowMaker to enlightenment was enough to start my XSHM adventure. I suspect the culprit is really imlib/XF86-4.0 interaction. Gnome may contribute to the problem as it uses imlib itself, but enlightenment really gives imlib a workout. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Sat, Jun 24, 2000 at 12:29:56AM +0200, Alexander Sanda wrote: BTW: It's for sure _not_ a -current issue and might have nothing to do with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with Xfree 4.0 and Gnome 1.2. Which video card/driver are you using? (Mine is tdfx and s3virge) -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, 23 Jun 2000, Garance A Drosihn wrote: At 4:00 PM -0400 6/23/00, Kelly Yancey wrote: On Fri, 23 Jun 2000, Shawn Halpenny wrote: I have not had any of the problems he's describing. I have never modified my shared memory settings in my kernel config either. If the problem is indeed Xfree 4.0, then I guess it must be a driver issue (I'm using the neomagic driver). You are running sawfish, and I'm willing to bet a not very graphics intensive config at that. Note that Chris (who posted the original message) is also running sawmill/sawfish... (they are the same thing, right?) Sawmill is *very* customizable. As a matter of fact, when I last tried it the default config was kind of bare. However, a lisp wizard can really jazz it up with loads of graphics, etc. So it is possible that Shawn is using a 'simpler' config and Chris is the aforementioned lisp wizard :) Sawmill/sawfish uses imlib, so if Chris is using a config with loads of graphics, it would lend credence to my theory that imlib and XF86-4.0 are interacting to create large/many shared memory segments. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 18:41 23.06.2000 -0400, Christopher Masto wrote: BTW: It's for sure _not_ a -current issue and might have nothing to do with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with Xfree 4.0 and Gnome 1.2. Which video card/driver are you using? (Mine is tdfx and s3virge) nVidia GeForce DDR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
