Re: Proper permissons on /tmp
On Thu, Nov 16, 2000 at 06:54:23AM +0100, Leif Neland wrote: > What is the proper perms on /tmp? 1777 Kris PGP signature
Proper permissons on /tmp
Something keeps changing permissions on /tmp to 755, which causes pine to claim the mailbox is in use by another process. This change has occurred a couple of times lately, but I haven't found a pattern. When I reset the perms to 777, pine works normal again. What is the proper perms on /tmp? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NTFS patch ready to be committed
On Wed, 15 Nov 2000, Rogier R. Mulhuijzen wrote: > NTFS is still broken in -CURRENT > > I've submitted a patch to gnats (and posted about it): > > http://www.freebsd.org/cgi/query-pr.cgi?pr=22756 > > I've been running it for a while now, without problems. Can someone commit it? Yes, patch is correct and matches the one in my tree. I'll commit it this evening if no one will do it before :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does floppies work with 384MByte RAM ?
> > I have two reports about machines with 384MB RAM panicing when > the floppies are accessed. I don't have the message right now > except for a report that "it said something about bouncebuffers" I apologize for the vagueness of this response, but perhaps it might help shed some light. I've got a Dell dual-Pentium-III XEON system at work that I was running -current on. Some time ago (didn't notice when exactly, sigh) when building new kernels, I started getting isa_dmainit(foo, bar) failed messages during the booting process for both the fdc device as well as my CS423x sound device. A cursory examination revealed that this was while trying to allocate bounce buffers for both the floppy and sound device DMA channels. On a lark, I rebuilt a kernel with MAXMEM=(256*1024) (the system has 512M of memory installed), and the isa_dmainit() failures stopped happening. Recently, I installed 4.1.1-STABLE on this machine because, well, I needed a stable system and didn't need to track the -current bleeding edge. It's probably hard for me currently to reproduce this problem myself right now. I'd suggest the MAXMEM hack to see if this mirrors my experience. Certainly this system was working just fine until sometime around the SMPNG milestone; but I can't really attribute the failure to any particular change. Again, sorry for the lack of detail; hope this might provide a hint. louie > Can somebody with 384MB ram check if the floppy works under > current ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: cvs commit: src/sys/alpha/alpha trap.c src/sys/i386/i386 tra
On 16-Nov-00 John Baldwin wrote: > jhb 2000/11/15 18:16:45 PST > > Modified files: > sys/alpha/alpha trap.c > sys/i386/i386trap.c > sys/ia64/ia64trap.c > sys/kern kern_mutex.c kern_shutdown.c kern_sig.c > kern_subr.c kern_synch.c > Log: > Don't release and acquire Giant in mi_switch(). Instead, release and > acquire Giant as needed in functions that call mi_switch(). The releases > need to be done outside of the sched_lock to avoid potential deadlocks > from trying to acquire Giant while interrupts are disabled. > > Submitted by: witness It is now safe to turn on WITNESS in -current kernels without having the machine panic or lockup At least it is on my set of test boxes. As such, I plan to turn on the various debugging options in -current's GENERIC sometime tomorrow (including WITNESS, but without DIAGNOSTIC). -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does floppies work with 384MByte RAM ?
Poul-Henning Kamp wrote: > I have two reports about machines with 384MB RAM panicing when > the floppies are accessed. I don't have the message right now > except for a report that "it said something about bouncebuffers" > > Can somebody with 384MB ram check if the floppy works under > current ? works fine on my current, i tried a mount, cp files in, rm files, and then a umount, all work normally. -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Patches to make witness work..
[ Bcc'd to -current, send followups to -smp ] I've been spending my time recently trying to get the kernel to boot with witnees turned on. The witness code itself was not broken (with a tiny exception), but our kernel code did have some bugs. However, while fixing the problems witness pointed out, I ended up with a kernel that is not stable on SMP systems (go figure). Part of this may be due to a broken atkbd driver, whose interrupt thread seems to chew up a lot more CPU time than it should be. I've tried to commit as many of the safe changes as I could w/o actually breaking SMP systems. The rest of the patches that are needed are at http://www.FreeBSD.org/~jhb/patches/giant.patch. This patchset does two primary things: 1) It fixes msleep() and mawait() to release the sched_lock before calling CURSIG() and to pick the lock back up again afterwards. 2) It moves the dropping/reacquiring of Giant out of mi_switch() and out into the code that calls mi_switch(). This is needed because Giant needs to be released/reacquired when it is not under the sched_lock Any feedback, etc. is welcome. At the very least, UP systems (both x86 and alpha) appear to be fine with this patch, and can run kernels with witness enabled without any problems. Thus this patch can be used to debug deadlocks, etc. on UP systems at least. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with stdbool.h...
As some of you may have noticed, apsfilter will no longer
compile on -current. The reason is that the configure
script checks for , and uses it if it exists;
but this file, as I understand it, is intended only for
use with C99, and unfortunately, if it is included by the
standard compiler, the results are bad. An example:
/* test.c */
#include
int main()
{
return(0);
}
$ cc -o test test.c
In file included from test.c:1:
/usr/include/stdbool.h:51: conflicting types for `_Bool'
/usr/include/stdbool.h:38: previous declaration of `_Bool'
Apparently, stdbool.h defines _Bool, then redefines it if
__STDC_VERSION__ < 199901L.
Fixing the port to compile anyway would be simple enough,
but I think the real problem is in stdbool.h, no? It
shouldn't break the standard compiler like this, should
it?
Please forgive the cross-posting... Although this affects
ports, I have no way of knowing if the maintainer of this
file reads the ports mailing list...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Bad commit?
In message <[EMAIL PROTECTED]> Kirk McKusick writes: : I have checked in revision 1.15 for subr_rman.c which should fix : the problems being experienced with version 1.14. If you continue : to experience problems with version 1.15, please let me know. I've tested this and it appears to work. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad commit?
Date: Wed, 15 Nov 2000 11:47:07 -0700 From: Warner Losh <[EMAIL PROTECTED]> Subject: Bad commit? Sender: [EMAIL PROTECTED] As near as I can tell on my laptop, the following change causes panics with kernel page faults. With it, my laptop panics every time on boot (although in slightly different places for my two different kernels) and without it I'm rock solid. Has anybody else seen this? Warner mckusick2000/11/14 12:46:02 PST Modified files: sys/sys rman.h sys/kern subr_bus.c subr_rman.c Log: In preparation for deprecating CIRCLEQ macros in favor of TAILQ macros which provide the same functionality and are a bit more efficient, convert use of CIRCLEQ's in resource manager to TAILQ's. Approved by: Garrett Wollman <[EMAIL PROTECTED]> Revision ChangesPath 1.13 +3 -3 src/sys/sys/rman.h 1.83 +3 -5 src/sys/kern/subr_bus.c 1.14 +30 -35src/sys/kern/subr_rman.c I have checked in revision 1.15 for subr_rman.c which should fix the problems being experienced with version 1.14. If you continue to experience problems with version 1.15, please let me know. Kirk McKusick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to build world
On Wed, Nov 15, 2000 at 09:20:06PM +, Joel Lindau wrote: > When i try to build my -current world cvsupped today ( 15 nov ) i get the > following errors: When was the last time up built world? I'd like to know if this has anything to do with the Binutils upgrade, or if is something you would have experienced if you had tried to build world yesterday To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Does floppies work with 384MByte RAM ?
I have two reports about machines with 384MB RAM panicing when the floppies are accessed. I don't have the message right now except for a report that "it said something about bouncebuffers" Can somebody with 384MB ram check if the floppy works under current ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: binutils commit breaks kernel builds?
On Wed, Nov 15, 2000 at 04:15:55PM +0100, Harti Brandt wrote: > with fresh sources from today 6:00 MET kernel builds fail. The victim is I'm done with the upgrade - you may have easily CVSuped during the upgrade process. Can you wait an hour or so, CVSup again and see if you still see the problem? Is anyone else experience[31~ing this? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NTFS patch ready to be committed
NTFS is still broken in -CURRENT I've submitted a patch to gnats (and posted about it): http://www.freebsd.org/cgi/query-pr.cgi?pr=22756 I've been running it for a while now, without problems. Can someone commit it? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
APM problems with 5.0-20001112-CURRENT
Hi I have a Compaq Armada E500 and the apm support doesnt work. It seems that the kernel doesnt find the apm controller just that it is on the pci bus. I am using freebsd 5.0-20001112-current and have tried with both the generic kernel and my custom kernel. in the kernel configuration I have just "device apm" any one got any idea whats wrong? My dmesg output is in down under here... Regards Claes Leufven --dmesg output Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-20001112-CURRENT #4: Wed Nov 15 22:05:44 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/chewie Calibrating clock(s) ... TSC clock: 497464932 Hz, i8254 clock: 1193258 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 497435562 Hz CPU: Pentium III/Pentium III Xeon/Celeron (497.44-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 67043328 (65472K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00312000 - 0x03fe7fff, 63791104 bytes (15574 pages) avail memory = 62279680 (60820K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fa000 bios32: Entry = 0xf (c00f) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x478 pnpbios: Found PnP BIOS data at 0xc00f5100 pnpbios: Entry = f:512e Rev = 1.0 pnpbios: Event flag at f5126 pnpbios: OEM ID 51b1110e Other BIOS signatures found: Preloaded elf kernel "kernel" at 0xc02f9000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f90a8. null: random: mem: Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 22 00 00 01 7f 00 00 01 0b 01 00 01 21 01 00 01 2a 01 00 01 00 01 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 05 01 16 01 17 01 18 01 07 01 19 01 VESA: 40 mode(s) found VESA: v2.0, 8128k memory, flags:0x0, mode table:0xc029e3a2 (122) VESA: ATI MACH64 VESA: ATI Technologies Inc. MACH64RM 01.00 Using $PIR table, 268435454 entries at 0xc00f0970 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: physical bus=0 found-> vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base 5000, size 26, enabled found-> vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x104c, dev=0xac1c, revid=0x01 bus=0, slot=4, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=2 secondarybus=2 intpin=a, irq=11 map[10]: type 1, range 32, base 4110, size 12, enabled found-> vendor=0x104c, dev=0xac1c, revid=0x01 bus=0, slot=4, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=3 secondarybus=3 intpin=a, irq=11 map[10]: type 1, range 32, base 4118, size 12, enabled found-> vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 3420, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[20]: type 4, range 32, base 3400, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x03 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 4, range 32, base 4000, size 4, enabled found-> vendor=0x125d, dev=0x1978, revid=0x10 bus=0, slot=8, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 4, range 32, base 3000, size 8, enabled found-> vendor=0x8086, dev=0x1229, revid=0x09 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 4128, size 12, enabled map[14]: type 4, range 32, base 3440, size 6, enabled map[18]: type 1, range 32, base 4120, size 17, enabled found-> vendor=0x11c1, dev=0x0445, revid=0x00 bus=0, slot=9, func=1 class=07-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 4, range 32, base 3430, size 3, enabled map[14]: type 1, range 32, base 4130, size 12, enabled pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: physical bus=1 found-> vendor=0x1002, dev=0x4c4d, revid=0x64 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: t
Re: Bad commit?
In message <[EMAIL PROTECTED]> Mike Smith writes: : Yes; I think it's broken the resource manager. I'm testing kirk's fix right now on the laptop in question... It boots one of the kernels that was always crashing before. Looks like we have a winner. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad commit?
> > As near as I can tell on my laptop, the following change causes panics > with kernel page faults. With it, my laptop panics every time on > boot (although in slightly different places for my two different > kernels) and without it I'm rock solid. > > Has anybody else seen this? Yes; I think it's broken the resource manager. > Warner > > mckusick2000/11/14 12:46:02 PST > > Modified files: > sys/sys rman.h > sys/kern subr_bus.c subr_rman.c > Log: > In preparation for deprecating CIRCLEQ macros in favor of TAILQ > macros which provide the same functionality and are a bit more > efficient, convert use of CIRCLEQ's in resource manager to TAILQ's. > > Approved by:Garrett Wollman <[EMAIL PROTECTED]> > > Revision ChangesPath > 1.13 +3 -3 src/sys/sys/rman.h > 1.83 +3 -5 src/sys/kern/subr_bus.c > 1.14 +30 -35src/sys/kern/subr_rman.c > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unable to build world
Hi, When i try to build my -current world cvsupped today ( 15 nov ) i get the following errors: [ -- ] >>> stage 2: build tools -- cd /usr/current/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh /usr/current/src/tools/install.sh" PATH=/usr/obj/usr/current/src/i386/usr/sbin:/usr/obj/usr/current/src/i386/usr/bin:/usr/obj/usr/current/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 build-tools cd /usr/current/src/bin/sh; make build-tools cc -O2 -pipe -DSHELL -I. -I/usr/current/src/bin/sh -Wall -Wformat -c /usr/current/src/bin/sh/mkinit.c cc -O2 -pipe -DSHELL -I. -I/usr/current/src/bin/sh -Wall -Wformat -static mkinit.o -o mkinit /usr/lib/crt1.o: In function `_start': /usr/lib/crt1.o(.text+0x60): undefined reference to `_fini' /usr/lib/crt1.o(.text+0x6a): undefined reference to `_init' *** Error code 1 [ -- ] /usr/lib/crt1.o ? / Joel.L a.k.a Nevyn -- #FreeBSD.se, #unix.se To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: clock/apm broken in CURRENT ?
In message <[EMAIL PROTECTED]> Warner Losh writes: : Add : device pmtimer : to your config file. Fixes it for me. Tell people on #bsdcode about : this. I've gone ahead and updated GENERIC with this fix. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: clock/apm broken in CURRENT ?
Ollivier Robert wrote: > Am I the only to have problem with the clock on a laptop using APM in > CURRENT? Speaking with some people on #bsdcode apparently no. > > In short, the clock stops during suspend time... > > This is on a VAIO Z505SX running current from Nov, 8th. > > Any idea when this will be fixed? There is entry in src/UPDATING: 2914: The new pmtimer device is necessary for laptops. Failure to include the device will cause suspended laptops losing time when they resume. Include device pmtimer in your config file and hint.pmtimer.0.at="isa" to your /boot/device.hints file. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bad commit?
As near as I can tell on my laptop, the following change causes panics with kernel page faults. With it, my laptop panics every time on boot (although in slightly different places for my two different kernels) and without it I'm rock solid. Has anybody else seen this? Warner mckusick2000/11/14 12:46:02 PST Modified files: sys/sys rman.h sys/kern subr_bus.c subr_rman.c Log: In preparation for deprecating CIRCLEQ macros in favor of TAILQ macros which provide the same functionality and are a bit more efficient, convert use of CIRCLEQ's in resource manager to TAILQ's. Approved by: Garrett Wollman <[EMAIL PROTECTED]> Revision ChangesPath 1.13 +3 -3 src/sys/sys/rman.h 1.83 +3 -5 src/sys/kern/subr_bus.c 1.14 +30 -35src/sys/kern/subr_rman.c To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: clock/apm broken in CURRENT ?
In message <[EMAIL PROTECTED]> Ollivier Robert writes: : Am I the only to have problem with the clock on a laptop using APM in : CURRENT? Speaking with some people on #bsdcode apparently no. : : In short, the clock stops during suspend time... : : This is on a VAIO Z505SX running current from Nov, 8th. : : Any idea when this will be fixed? Add device pmtimer to your config file. Fixes it for me. Tell people on #bsdcode about this. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current has hosed the i8254 timecounter...
On Tue, Nov 14, 2000, John Baldwin wrote: > > I'm seeing something similar with -current on this laptop here. Magically, > > if I jiggle the mouse whilst playing an mp3, things start to skip and the > > clock goes *way* off way (sometimes by a few seconds in a few seconds. :) > > That is probably due to the random harvesting thread. Or rather, that the > overhead of ithreads together with the random kthread and the load of playing > mp3's is starving your CPU. Do you have any idle time at all when this happens? Yup, plenty. Its a fast laptop. I can get real numbers back again tomorrow. Adrian -- Adrian Chadd"Programming is like sex: <[EMAIL PROTECTED]> One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fetch
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [001115 03:39] wrote:
>
>
> Hello,
> i'm using libfetch.
> I want to get a file in passive mode in my local disk.
> If I read trace from the remote machine, the transfert is okay
> but i can't find my new imported file in the local disk.
> Can you help me to find it ? :o{
Not really, we don't have access to your system, disk or source.
Perhaps if you posted a short code example we could help you
find the problem.
-Alfred
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
vmwareport does not work
I cvsuppped today to 4.2 beta the problem is that i cannot get the vmnet module to run properly if i issue (qfetr installation) : /usr/local/etc/rc.d/vmware.sh start i get kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko: File exists sysctl: unknown oid 'net.link.ether.bridge_refresh' kldload: can't load if_tap.ko: File exists ifconfig: ioctl (SIOCAIFADDR): File exists what' s wrong then ? thanks a lot in advance To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
clock/apm broken in CURRENT ?
Am I the only to have problem with the clock on a laptop using APM in CURRENT? Speaking with some people on #bsdcode apparently no. In short, the clock stops during suspend time... This is on a VAIO Z505SX running current from Nov, 8th. Any idea when this will be fixed? -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
binutils commit breaks kernel builds?
Hello, with fresh sources from today 6:00 MET kernel builds fail. The victim is 'size' which is executed during the build and which dumps core in bfd_close() (after printing the sizes). The build breaks when done via make buildkernel, it works when I invoke make from the kernel build directory. This seem to indicate, that the 'size' built from the updated source via 'make buildworld' is broken. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATM - FORE PCA-200E
In message <[EMAIL PROTECTED]>, Adam Obszynski writes: >Hello freebsd-current, > > Is somebody here who using fore adapter (subject) in current tree ? how it > is stable ? which signalisation are you using ? sigpvc ? spans ? uni ? > maybe some LANE code were added ? yes. yes. sigpvc. Not that I know off. PS: anyone looking to buy a bunch of these please contact me, I may know of a source for some cheap cards if bought in (minor) quantities. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATM - FORE PCA-200E
Hello freebsd-current, Is somebody here who using fore adapter (subject) in current tree ? how it is stable ? which signalisation are you using ? sigpvc ? spans ? uni ? maybe some LANE code were added ? -- Regards, Adam Obszyński [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fetch
Hello,
i'm using libfetch.
I want to get a file in passive mode in my local disk.
If I read trace from the remote machine, the transfert is okay
but i can't find my new imported file in the local disk.
Can you help me to find it ? :o{
Please answer me directly, i'm not a subscriber of this list.
Thank you
Gilles Guerrini
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Re[2]: if_tap and linprocfs modules are broken in -current
On Wed, 15 Nov 2000, Harti Brandt wrote: > > i do not use devfs. anyway, the patch by Maksim Yevmenkin doesn't > > help. kernel still reports "link_elf: symbol lminor undefined". > > > > and what's wrong with linprocfs? it seems to be broken too. > > Are you sure, that you don't have a stale linprocfs or if_tap in /modules > or elsewhere? sorry, i forgot to remove obsolete /modules. everything's fine now. thank you. sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PXE build?
> Does anyone know of any current issues with PXE? Some ROMs out there are pretty bad. > I've searched the mailing > lists and I don't see any mention of a problem similar to mine. > > I'm running FreeBSD-CURRENT from 2000 09 15 on a server. The client has an > Intel 21143 based ethernet card that claims it has PXE 2.0 (Build 74) > support. Are you *sure* the card is 21143-based? At any rate, the Intel PXE codebase is buggy for the 8255x chips up to build 082, so you're probably running bad code there. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "make modules" kicks the first module directory twice
On Tue, 14 Nov 2000, Warner Losh wrote:
> make depend is already *REQUIRED* when you are updating a kernel from
> an older version of the kernel. For config -r FOO kernels it isn't.
It is neither necessary nor sufficient for updating. config -r removes
conflicting garbage from previous builds. Removing the conflicting
garbage is sufficient. `make clean' normally suffices to remove it,
but there are cases where .depend itself is garbage and must be removed
to unbreak `make depend'.
> Even a make clean after a make depend will require that make depend be
> run again.
This was broken in rev.1.348 of sys/conf/files, etc. `make clean'
removes the generated bus interface headers, and there are no longer
enough dependencies for make(1) to know how to rebuild them. There
are enough dependencies to rebuild them for `make depend', and for
plain `make' when .depend doesn't exist (minor magic involving
${BEFORE_DEPEND}). .depend still doesn't contain all the dependencies
on headers, because at least the generated bus interface .c files are
handled too specially.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Re[2]: if_tap and linprocfs modules are broken in -current
On Tue, 14 Nov 2000, Ilya Naumov wrote: Hi, > >> when i try to kldload if_tap module, the kernel says "symbol lminor > >> undefined" and fails to load the module. for linprocfs module the > >> message is "symbol tsleep undefined". these modules are necessary for > >> VMWare 2.0 port. > >> > >> >How-To-Repeat: > >> > >> kldload if_tap > >> kldstat linprocfs > > HB> No problems here with source from today 6.00 MET. if_tap was > HB> fixed on 09/19. > > it's ok, i'm expiriencing them right now, with today's kernel/modules > (built on 13:07 MSK). > > HB> NB: there is a commit request pending for if_tap. It is currently unusable > HB> with devfs. Would be REALLY nice if a committer could look at the patch. > > i do not use devfs. anyway, the patch by Maksim Yevmenkin doesn't > help. kernel still reports "link_elf: symbol lminor undefined". > > and what's wrong with linprocfs? it seems to be broken too. Are you sure, that you don't have a stale linprocfs or if_tap in /modules or elsewhere? lminor was removed from if_tap two month ago as I already said. Go into you build directory and do a 'nm if_tap.ko | grep minor' - no lminor should be there. If it is, you have a stale source file. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
