Re: LINT and NOTES
On Thu, Apr 19, 2001 at 10:23:02AM -0700, Jens Schweikhardt wrote: > I just wanted to close http://www.freebsd.org/cgi/query-pr.cgi?pr=25030 > by frobbing NOTES. While 4.2-R LINT has option USER_LDT, NOTES doesn't > have it anymore. Can anybody clue me in why it disappeared? Can I simply > resurrect it? Because peter eliminated it by making the relevant code mandatory about 2 months ago. Check out the cvs logs for NOTES. > BTW, is this the right list to ask such a question? Nope. current@ would be. -- wca PGP signature
Re: make installworld runs out of space on / ...
On Sat, May 12, 2001 at 12:47:30AM -0300, The Hermit Hacker wrote: > My / directory, right now, has 12Meg free on it ... if I do a make > installworld, it will fail due to no space left on device ... > > Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on > /dev/da1s1a 63503460151240879%1858 1401212% / > > Has anyone run into this one? Is there a way of fixing it? I can't find > anything on / that isn't supposed to be there, or is relatively large ;( rm -rf /var/tmp/install.* -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: chinput can't work on KDE2.2.2
On Tue, Jan 22, 2002 at 08:56:13AM +, Liu Siwei wrote: This question is not appropriate for the -current list. I'm expanding this to include the maintainers of the KDE ports to see if anyone else has an idea what's going on. >I have a question about FreeBSD's locale. I use the zh_CN.EUC locale to > let my FreeBSD support Simplied Chinese. It's all right in gnome 1.4. But in > > recent version of KDE(aka. KDE-2.2.2), I can't set zh_CN.EUC locale for it. > For I have select the country is Asia-China, language is Simplied Chinese, > code is gb2312.1980. I need not set any locale in my environment to display > Simplied Chinese at all. But for I have not set locale, I can't use chinput > in KDE. So I set my locale to zh_CN.EUC in my $HOME/.xinitrc. But when I > restart my KDE, it can't display Chinese word proper! in kedit, kwrite, etc, > > I can use chinput through I can't input any Chinese word proper. If I set my > > locale to zh_CN.GB2312, zh_CN.GBK or nothing, the KDE can display Chinese > word proper, but I can't use chinput. >So, how to set ocale to let chinput work under KDE2.2.2? >A very inportant QUESTION is: why FreeBSD want zh_CN.EUC while KDE is > not? >My machine is AMD-K7 700, FreeBSD-current,all software are installed > from ports(sources). I'm sorry but I can't help with this specific problem since I do not use any locale other than the default. :( -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org down?
On Thu, Feb 07, 2002 at 04:44:36PM +0100, Miguel Mendez wrote: > I know this is probably offtopic but is there any problem with > current.freebsd.org at the moment? I've been unable to log in for almost an > hour, the ftp daemon is up, it just doesn't allow me in and I was about to > load -CURRENT on my laptop. Jordan announced recently that Qwest is upgrading the hardware and that there would be intermittent problems with the server for a certain period (a few days as I recall). Regards -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MODULES_WITH_WORLD=true means no modules?
On Thu, Feb 07, 2002 at 09:57:47PM +0100, BOUWSMA Beery wrote: Maybe... > I've changed my /etc/make.conf from the default, to be > MODULES_WITH_WORLD=true # do not build modules when building kernel ^^^ ...you need to read the option you enabled? > since I find myself often building new kernels (plus identical > modules) without updating the rest of the source, taking extra time. Regards. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MODULES_WITH_WORLD=true means no modules?
On Thu, Feb 07, 2002 at 09:57:47PM +0100, BOUWSMA Beery wrote: Maybe... > I've changed my /etc/make.conf from the default, to be > MODULES_WITH_WORLD=true # do not build modules when building kernel ^^^ ...you need to read the option you enabled? > since I find myself often building new kernels (plus identical > modules) without updating the rest of the source, taking extra time. Regards. -- wca 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: current.freebsd.org down?
On Thu, Feb 07, 2002 at 04:44:36PM +0100, Miguel Mendez wrote: > I know this is probably offtopic but is there any problem with > current.freebsd.org at the moment? I've been unable to log in for almost an > hour, the ftp daemon is up, it just doesn't allow me in and I was about to > load -CURRENT on my laptop. Jordan announced recently that Qwest is upgrading the hardware and that there would be intermittent problems with the server for a certain period (a few days as I recall). Regards -- wca 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: FreeBSD unfinished NIS+ implementation in Linux ?
On Sun, Feb 17, 2002 at 03:57:59PM +0100, Martin Blapp wrote: > Bill, did you ever allowed them to make it GPL only ? Looking at the code > it should be possible to import some things and make a NIS+ client > available. But only if it's not GPL'd. Interesting. I looked as nisgrep/nisgrep.c and noticed that the code structure was basically the same, but the variables were just slightly different... -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI timecounter help needed!
On Mon, Feb 25, 2002 at 10:59:16AM +0100, Poul-Henning Kamp wrote: > Machines with ACPI timecounters will now print 10 lines at boot when > the timer is tested. You should mention that this requires bootverbose. > If you are lucky you will see ten times something like: > ACPI timer looks GOOD min = 3, max = 3, width = 1 > That means that you have well implemented ACPI timer. > > If you are unlucky, one, several or all 10 lines will be marked as > "BAD". > > Please send me an email with these 10 lines and the output of > "pciconf -l -v" for your machine. I'm am interested in reports > both from good and bad machines. I will send you mine as soon as I can figure out how to extract the information usefully as the machine behaves VERY badly with the ACPI timecounter -- the only way I can see output on the syscons console is if I break into DDB repeatedly. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )
On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote: > > > currently kde doesn't work due to binuntils update. It may work now > > > after the most recent binutils update, but we have to recompile kde to > > > see that I believe, andkdelibs cannot be compiled which builds > > > kde-config which the rest of the kde meta-ports try to run. > > > > > > I think that last sentence is a huge run on and I by no means am trying > > > to complain, just wondering if anyone thinks its important to make it on > > > this snapshot. > > > > Hmm. My impression was that the libpng stuff had been fixed, could you > > confirm that KDE still doesn't build on 5.0-CURRENT? > > Its not related to libpng, I believe that has been fixed, but I > cannot tell for sure because kde cannot be compiled under -current. > I'm not the only one that is experiencing it either, here is what I > was told by Alan Eldridge <[EMAIL PROTECTED]> You said "binutils upgrade broke KDE" -- the quoted mail has nothing to do with binutils. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Preparing innocent users for -current
On Fri, Mar 08, 2002 at 02:58:40PM -0500, Michael G. Petry wrote: > Per Doug's note, is there a schedule to pull the XFree86-4 back up to 4.2.0? > Since it was pulled back because of the 4.5 release, it would be a shame for > it to be also held back by a -current snapshot. Yes, I am handling that. I've been testing a version of the upgrade on 2 of my machines for several weeks, but haven't had time to fix a few more things, which is the reason for the delay, aside from the fact that I was previously waiting on the people who actually wrote the patch to commit it. However, since my midterms are over and spring break is upon me, I will focus a large part of the next few days getting the upgrade done and committed. It should be done by Saturday, March 9 at the earliest and Saturday, March 16 at the latest, and probably on Sunday or Monday. Thanks, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: > This isn't good: > > http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log > > building TenDRA-4.1.2 on gohan17 > in directory /x/tmp/5/chroot/31459 > with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA > maintained by: [EMAIL PROTECTED] > build started at Sat Mar 9 00:37:43 GMT 2002 > ... > Operating system version = 4.4-STABLE > > I thought uname was faked out to return the proper value. > I wonder if things like this could be one of the problems. More like, the port builds in a chroot which contains the environment of a 5.0 world. So the chroot tarball for 5.0 being used here must be the wrong one, or it's screwed up. Thanks for pointing this out. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 07:30:21PM -0500, Robert Watson wrote: > uname extracts the various strings it can report from the running kernel > using sysctl. Unless you have a faked uname, it will return the > properties of the host non-chroot environment, rather than the chroot > environment. Increasingly, it's going to be harder and harder to run 5.0 > in a 4.x chroot, due to divergence in system calls, especially once > threaded applications start using KSE. Running 4.x in a 5.0 chroot should > (hopefully) continue to work fine. You are right. I made a thinko, and later realized it while talking to Kris. I was hoping nobody would notice... :) We are screwed if anybody uses sysctl() or sysctlbyname(), unless someone decides to allow us to change kernel variables and the like inside chroot() (or perhaps jail()).. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 05:54:40PM -0800, Alex Zepeda wrote: > As far as Qt goes, rip out that objprelink crap. Without it Qt will build > and work just fine. At least Qt 3.whatever works for me. I don't know > why objprelink isn't working correctly for Qt, but I don't really care. > For me disabling WITNESS does more than enough to make KDE useable on my > -current box (2xP2-450). Um.. objprelink is disabled if OSVERSION >= 500029. So it is already "ripped out" for -current. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cdrecord for ATAPI burners available..
On Wed, Mar 20, 2002 at 12:00:43AM +0100, Thomas Quinot wrote: > > These utils are ATA only (as the name implies), if our ports people > > wants to merge it into whats already there I wont complain :) > > That said I think the ATA only version covers more than a significant > > percentage of our userbase Speaking as a ports person, I don't like the idea of having to backport these changes repeatedly over the course of a product's lifetime, and a local hack for FreeBSD is gross. > In which case I'll be more than happy to continue maintaining ATAPI/CAM > as an alternative solution, which addresses 100% of our user base and > does not impose any additional work upon application authors or port > maintainers. On the other hand, I think Thomas' approach is more maintainable. I do not understand why ATA/CAM people won't cooperate on this, but then I'm just a ports person... what do I know about maintenance? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.2.0 with G200 fail to start with signal 10
On Wed, Mar 20, 2002 at 11:29:46AM +0100, Riccardo Torrini wrote: > With last update of world and ports I'm unable to start XFree86. > I have a matrox G200 (agp) and I have tryed with and without the > WITH_MATROX_GXX_DRIVER=yes but I got only a signal 10, core dump > when starting X. At the same time I switched my MoBo from tyan > trinity with k6 to a asus p2b-ds dual processor p3/500. > I have a recent system (fresh compile with SMP enabled): What is your pkg_info -Ia? I committed an updated version of the Matrox driver for XFree86-4-Server, maybe you don't have that? BTW, it's not very well tested and I certainly can't test it myself w/o Matrox hardware. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/sys acct.h acl.h bio.h buf.h callout.h conf.h cons.h disk.h disklabel.h diskslice.h domain.h errno.h event.h eventhandler.h exec.h fcntl.h file.h filedesc.h imgact.h imgact_aout.h imgact_elf.h inflate.h interrupt.h ioccom.h ipc.h ...
On Fri, Mar 22, 2002 at 06:50:55AM -0700, M. Warner Losh wrote: > : At least in the case of 'ioccom.h' this commit breaks > : the XFree86-server building in the 'drm/kernel' directory. > : > : The problem is in the '#define ioctl(a,b,c) xf86ioctl(a,b,c)' > : which is used by the XFree86 and the __P somehow makes it possible > : to build 'xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/xf86drm.c' > : and now it stops here. > > Yes. That's likely the case. I'd kicked off a build of X11 after > alfred did these changes, but it died due to lack of disk space before > I got to this point and I let the matter sit there for a while. > > A patch to X11 will be needed. The OpenBSD folks hit this same > problem a few days ago when they removed it and committed patches to > their repo to fix this problem. Please send it to me as soon as you figure out what it should be and I'll speed it to the tree w/ other patches I have. Please try to make a patch that also works on -stable. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4.2.0 ioctl question [-current ioccom.h __P related]
On Fri, Mar 22, 2002 at 01:01:57AM -0600, Eric Liedtke wrote: > While trying to build the XFree86-4-Server port this evening(cvsuped > today around 1PM CST) > the build died due to a redefinition of xf86ioctl. The file > /usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/include/xf86_ansic.h Yes, this is a problem recently identified on the -current mailing list that someone else is looking into. When they have a patch, I will integrate it ASAP. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/sys acct.h acl.h bio.h buf.h callout.h conf.h cons.h disk.h disklabel.h diskslice.h domain.h errno.h event.h eventhandler.h exec.h fcntl.h file.h filedesc.h imgact.h imgact_aout.h imgact_elf.h inflate.h interrupt.h ioccom.h ipc.h ...
On Fri, Mar 22, 2002 at 08:28:36AM -0700, M. Warner Losh wrote: > Ummm, I'm not going to be doing patches for X11 for at least a few > more days, if then. I don't have the time to do it until sometime > next week. Well if someone else does it, they need to send me the patch. :) Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: turning off malloc's AJ by default
On Sat, Mar 23, 2002 at 06:40:21PM -0800, Steve Kargl wrote: > Surely, you're joking. No wonder it's a PITA > to convince a 3rd party vendor to release a > FreeBSD product. Please don't misinterpret David's words. 3rd party apps are not our *primary* concern, FreeBSD is. And note that in this thread we are talking about turning the default off. This does not stop someone from turning AJ back on and using them to debug/fix a program. :-) Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with ssh
On Thu, Mar 28, 2002 at 12:03:17PM -0800, David O'Brien wrote: > That is NOT a fix. Some of us want S/Key (OPIE) support. > This is a temperary work around. And some of us want passphrase support. :-) SSH should just be fixed to DTRT when one doesn't have S/Key setup on the server... however, it continues to break POLA, several months after the change which caused this was committed. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
usbd(8) doesn't attach aue(4) device properly?
Hi, I'm trying to hook my new D-Link DSB-650TX up to a laptop with USB on a March ~26 -CURRENT. However, it's failing miserably: uhci0: port 0xfce0-0xfcff irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: D-Link Corp. DSB-650TX USB Ethernet, rev 1.10/1.01, addr 2 if_aue.ko is being loaded by the loader at boot time, so this should be working.. but the device is attaching to ugen(4) instead of aue(4). Ideas? The only thing I could think of was /etc/usbd.conf was out of date, but a mergemaster didn't fix this problem. Thanks, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usbd(8) doesn't attach aue(4) device properly?
On Sat, Mar 30, 2002 at 01:33:13PM +, Josef Karthauser wrote: > It's more likely that it's a new device that isn't included in usbdevs > or the driver. What's the product id that you get with 'usbdevs -v'. > Check that they're in the usbdevs file and in the driver code. Good call. Here's the info: <1 1105-0> (15:44:40) [will@altair ~]% sudo usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: full speed, power 156 mA, config 1, DSB-650TX USB Ethernet(0x400b), D-Link Corp.(0x2001), rev 1.01 port 2 powered According to sys/dev/usbdevs: /* D-Link products */ /*product DLINK DSBS25 0x0100 DSB-S25 serial adapter*/ product DLINK DSB650C 0x4000 10Mbps ethernet adapter product DLINK DSB650TX 0x4002 10/100 ethernet adapter product DLINK DSB650TX_PNA 0x4003 1/10/100 ethernet adapter product DLINK DSB6500xABC1 10/100 ethernet adapter So, like I said, you're right. :) Is this the only place I need to put information in? Somehow I doubt it. Please provide a patch so I can learn... :) BTW, I tried to override the default behavior found here by adding this information to /etc/usbd.conf but that doesn't work.. Thanks! -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: plug aue ethernet goes to panic
On Sat, Apr 13, 2002 at 12:44:36PM -0400, John Baldwin wrote: > Can you get a backtrace in ddb? It looks like a null pointer dereference, and > knowing where it happened would help. Finding the file and line of the > instruction pointer using addr2line on kernel.debug would be helpful as well. It *is* a null pointer deref. Joe and I looked at this problem, and it seems a function called device_get_ivars() isn't doing its job in sys/dev/usb/usb_port.h. So the variable is getting filled with a NULL pointer for the iface element and is later deref'd. That's the limit of my debugging, and Joe is looking into the problem actively. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: plug aue ethernet goes to panic
On Mon, Apr 15, 2002 at 11:11:36AM +0200, Nick Hibma wrote: > device_set_ivars is always called (in usbd_probe_and_attach) with as an > argument a stack variable. Also, the ivar is not stored or anything in > the if_aue.c driver. So this problem sounds like a problem in revisions > of various files. > > Please check that your kernel modules kernel are in sync. Do this by > rebuilding the kernel and the modules from scratch. > > Also, after you've installed your kernel check that all your kernel > files have been updated. Do you by any chance have a stale /modules or > /boot/modules directory lying around? You should have only kernel > modules in /boot/kernel*/ and NOT in /modules* or /boot/modules*. > > If the problem persists, please mail me the output of > > ident /sys/dev/usb/*.[ch] > find /modules /boot -type f -ls Nick, You really should talk to Joe Karthauser. He's already confirmed that it *is* an issue in the code (and not any kind of misconfiguration on my part). I've already spent enough time debugging the problem. I recently MFC'd the support for my device to -stable so I could use the machine on the network without it panicking on me. However, when Joe fixes the problem I will give it another shot [same machine has -CURRENT on another partition that I use for occasional hacking]. Thanks for the suggestions, though. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse in Xfree86 4.2.0
On Mon, Apr 15, 2002 at 03:25:12PM -0700, David O'Brien wrote: > I have requested of both the XFree86-4 Server and of Portmgr to make the > default mouse device /dev/sysmouse. But my emails have gone unanswered. They did not go unanswered. I said it was a good idea and that I would do it, but due to lack of time I haven't done it yet. This does not stop you from doing. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern kern_tc.c src/sys/sys timepps.h timetc.h
On Thu, May 02, 2002 at 03:30:40PM -0700, Brooks Davis wrote: > I haven't tryed backing the commits out yet, but I'm seeing similar behavior > on my HP Omnibook 500. In my case, it's actually not quite hung. What > appears to be happening is that nothing is causing the console buffer to > actually flush. The system is up (sort of), but the only way to see the > console output is to cause a kernel printf, say be breaking in to the > debugger. The system is basicaly useless at that point and you can't > shutdown cleanly. Similar behavior manifests itself on my -current laptop dated before April 27. I.O.W. it appears to freeze but will flush the console if you break to the debugger then hit 'c'. I believe this was caused by an earlier change to the timecounter code. Unfortunately I didn't have time to investigate further. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
