Re: GEOM code ready for testing

On Tue, 12 Mar 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Carl Makin writes: On Mon, 2002-03-11 at 06:34, Poul-Henning Kamp wrote: The GEOM code is now ready for early testing: Would GEOM support accessing a device via multiple paths? (ie could we write a method

Re: GEOM code ready for testing

In message [EMAIL PROTECTED], Rasmus Skaarup writes: On Tue, 12 Mar 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Carl Makin writes: On Mon, 2002-03-11 at 06:34, Poul-Henning Kamp wrote: The GEOM code is now ready for early testing: Would GEOM support accessing a device

Re: GEOM code ready for testing

On Tue, 12 Mar 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Rasmus Skaarup writes: On Tue, 12 Mar 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Carl Makin writes: Would GEOM support accessing a device via multiple paths? (ie could we write a method

Re: GEOM code ready for testing

In message [EMAIL PROTECTED], Rasmus Skaarup writes: Basically when a new g_provider is created it is offered to each method in turn and if that method likes it, it can stick g_geom on top of it. Ahh.. But do you rule out the possibility that two methods could apply to a g_provider? Or is

list

list Ing. Ramses H. Th. van Pinxteren CMG Finance BV. afdeling AV-Advanced Technologies 1 Laan van Kronenburg 14 postbus 133 1180 AC Amstelveen tel: +31 (0)20 503 3000 fax: +31 (0)20 503 3011 email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe

Re: GEOM code ready for testing

On Tue, 12 Mar 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Rasmus Skaarup writes: How you would recognize the same disk on thre different paths is a good question. We could implement (if we don't already have it) an ioctl/BIO_GETATTR which returns the serial number(s)

Re: GEOM code ready for testing

In message [EMAIL PROTECTED], Rasmus Skaarup writes: Well, the recognition/configuration issue is not one GEOM magically can solve for you, but GEOM promises that if you can recognize it and configure it, GEOM will not get in your way for doing what you want. But what if the name of the

early vfs_mountroot commit 20020308

Hi, Since the commit of the early vfs_mountroot on Mar 8, I have been unable to boot current. After reverting to the previous versions of init_main.c (1.187) vfs_conf.c (1.65) and sys/mount.h (1.117) current boots fine. My kernel configuration is: # # # machine i386 #cpu

Re: GEOM code ready for testing

On Tue, Mar 12, 2002 at 11:58:02 +0100, Rasmus Skaarup wrote: On Tue, 12 Mar 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Carl Makin writes: On Mon, 2002-03-11 at 06:34, Poul-Henning Kamp wrote: The GEOM code is now ready for early testing: Would GEOM support

Re: GEOM code ready for testing

FWIW, Justin and I have been thinking about (for years, actually) doing multipath support inside CAM. Actually, the multipathing support would be in new-bus and CAM would be one newbus client able to detect redundant paths and register them accordingly. The main thing to remember is that there

Re: GEOM code ready for testing

In message [EMAIL PROTECTED], Kenneth D. Merry writes: Would GEOM support accessing a device via multiple paths? (ie could we write a method that would do that?) Yes, that would be possible. FWIW, Justin and I have been thinking about (for years, actually) doing multipath support inside

4.5-5.0 kldxref:No such file or directory

make DESTDIR=/5.0 world kernel encountered the following problem: [...] -- Kernel build for GENERIC completed on Tue Mar 12 20:26:10 GMT 2002 --

Re: Adding realloc()

* Archie Cobbs [EMAIL PROTECTED] [020311 22:00] wrote: Hi, I've had the need for a realloc() in the kernel several times before and am having it once again. Finally figured it's time to do something about it. Does anyone have problems with the attached patch? This patch adds realloc()

Re: Adding realloc()

Alfred Perlstein writes: I've had the need for a realloc() in the kernel several times before and am having it once again. Finally figured it's time to do something about it. Where is the update to malloc(9)? What about reallocf? Good points, thanks.. try this one instead. -Archie

Re: gcc -O broken in CURRENT

On Tue, Mar 12, 2002 at 01:49:02AM +0100, Martin Blapp wrote: Hi all, Here are my test news. The -O bug doesn't happen with gcc295 from ports ! Since this problem was apparently introduced recently, can you check the commits against the gcc code in -current with the patches to the port?

Re: Adding realloc()

* Archie Cobbs [EMAIL PROTECTED] [020312 14:45] wrote: Alfred Perlstein writes: I've had the need for a realloc() in the kernel several times before and am having it once again. Finally figured it's time to do something about it. Where is the update to malloc(9)? What about

port: glibtop failure on -current / Gnome won't build

On: FreeBSD adam12.midearth.org 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sat Mar 9 13:55:57 CST 2002 [EMAIL PROTECTED]:/usr2/obj/usr/src/sys/MIDEARTH i386 make of libgtop fails with the following error, causing a make of /usr/ports/x11/gnome to fail... any suggestions? [snip] cc -DHAVE_CONFIG_H

Re: Adding realloc()

Alfred Perlstein writes: I've had the need for a realloc() in the kernel several times before and am having it once again. Finally figured it's time to do something about it. Where is the update to malloc(9)? What about reallocf? Good points, thanks.. try this one

Re: 4.5-5.0 kldxref:No such file or directory

On Tue, Mar 12, 2002 at 02:05:06PM -0700, [EMAIL PROTECTED] wrote: make DESTDIR=/5.0 world kernel encountered the following problem: [...] -- Kernel build for GENERIC completed on Tue Mar 12 20:26:10 GMT 2002

eaccess(2) breaks execution of 4.x binaries on 5.x

Subject says it all, really; this is the cause of part of my problems in getting 5.x packages built on the bento cluster, because it seems that /bin/sh has come to depend on this syscall. Executing a 5.x /bin/sh on a 4.x system causes a SIGSYS if it hits this code (e.g. test -x /some/binary)

Re: 4.5-5.0 kldxref:No such file or directory

* Crist J. Clark ([EMAIL PROTECTED]) wrote: *** Error code 1 (ignored) ^ Note. Since there is no kldxref in 4.5, this should probably included in the bootstrap process somehow. A known issue. The install process deliberately ignores this as a

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

On Tue, Mar 12, 2002 at 07:12:11PM -0800, Kris Kennaway wrote: Subject says it all, really Herf. Subject is the wrong way around; this breaks execution of 5.x binaries under 4.x, not the other way around. ; this is the cause of part of my problems in getting 5.x packages built on the bento

automatic reboot without panic writing to local fat32 fs

Copying remote files (large backup, 200/300Megs) from my home file server (4.5-STABLE) using nfs or ftp or scp to a local msdos fat32 partition reboot machine without any error :-( Yes, local machine that has msdos mounted fs is -CURRENT: # uname -v FreeBSD 5.0-CURRENT #22: Tue Mar 5 20:50:06

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

On Tue, 12 Mar 2002, Kris Kennaway wrote: Subject says it all, really; this is the cause of part of my problems in getting 5.x packages built on the bento cluster, because it seems that /bin/sh has come to depend on this syscall. Executing a 5.x /bin/sh on a 4.x system causes a SIGSYS if

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

On Tue, Mar 12, 2002 at 10:59:07PM -0500, Robert Watson wrote: On Tue, 12 Mar 2002, Kris Kennaway wrote: Subject says it all, really; this is the cause of part of my problems in getting 5.x packages built on the bento cluster, because it seems that /bin/sh has come to depend on this

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

rwatson Certainly we can MFC eaccess(), but that's not going to make rwatson the problem go away. Fundamentally our model is backward rwatson compatibility, not forward compatibility. We need to build rwatson 5.0 packages on 5.0. That's why I build FreeBSD 5-current snapshots on a 5-current

MAKEDEV - Installation fails - 20020312

Installing on a Sony VAIO PCG-SRX7E/P Boot from 4.5-INSTALL CD (iLINK) set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot Visual configuration, leave only: ata0 atkbd0 psm0 sc0 pcic0 npx0 Partition disk, select Developer and Ports Select 5.0-20020312-CURRENT as release Select -CURRENT FTP

Re: port: glibtop failure on -current / Gnome won't build

On Tue, 2002-03-12 at 20:06, Stephen L. Palmer wrote: On: FreeBSD adam12.midearth.org 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sat Mar 9 13:55:57 CST 2002 [EMAIL PROTECTED]:/usr2/obj/usr/src/sys/MIDEARTH i386 make of libgtop fails with the following error, causing a make of

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

Kris, Robert, On 20:11-0800, Mar 12, 2002, Kris Kennaway wrote: On Tue, Mar 12, 2002 at 10:59:07PM -0500, Robert Watson wrote: On Tue, 12 Mar 2002, Kris Kennaway wrote: Subject says it all, really; this is the cause of part of my problems in getting 5.x packages built on the bento

Re: port: glibtop failure on -current / Gnome won't build

Replaced file with the one you attached, did 'make clean' and 'make' and got the following. [snip] cc -DHAVE_CONFIG_H -I. -I. -I../.. -D_IN_LIBGTOP -D_GNU_SOURCE -DGLIBTOP_NAMES - I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I../../intl -I/usr/X11R6 /include/gnome-1.0

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

any change that has to be added to 4.x tomake it run on 5.x is the wrong answer. 4.x binaries should all run on 5.x (unless something was accidentally committed to 4.x that should be backed out.) any change for allowing 4.x binaries to run on 5.x should be done on the 5.x side of things,

Re: 4.5-5.0 kldxref:No such file or directory

On Wed, Mar 13, 2002 at 04:13:35AM +0100, Emiel Kollof wrote: * Crist J. Clark ([EMAIL PROTECTED]) wrote: *** Error code 1 (ignored) ^ Note. Since there is no kldxref in 4.5, this should probably included in the bootstrap process somehow.

Re: port: glibtop failure on -current / Gnome won't build

My mistake, I guess it helps if I 'gzip -d' the patch ;-) Sorry about that, it seems to work great! --- Stephen L. Palmer [EMAIL PROTECTED] On Tue, 12 Mar 2002, Stephen L. Palmer wrote: Replaced file with the one you attached, did 'make clean' and 'make' and got the following. [snip]

Re: eaccess(2) breaks execution of 4.x binaries on 5.x

On 21:33-0800, Mar 12, 2002, Julian Elischer wrote: any change that has to be added to 4.x tomake it run on 5.x is the wrong answer. 4.x binaries should all run on 5.x (unless something was accidentally committed to 4.x that should be backed out.) any change for allowing 4.x binaries to

Re: 4.5-5.0 kldxref:No such file or directory

* Crist J. Clark ([EMAIL PROTECTED]) wrote: The warning is just how make(1) works, AFAIK, you can use shell cmd's in bsd make... # Calling kldxref(8) for each module is expensive. .if !defined(NO_XREF) .MAKEFLAGS:=${.MAKEFLAGS} -DNO_XREF afterinstall: -kldxref

$B7HBS5a?M>pJs%5!<%S%9(B

$B7HBS5a?M>pJs%5!<%S%9!!L5NA%-%c%s%Z!<%s$N$*CN$i$;(B $B$46=L#$N$J$$>pJs$G$7$?$i@?$K$*!W$K!!G[?.ITMW!!$H=q$-$4JV?.2<$5$$!#(B ML$B$+$i:o=|$5$l$^$9!#$b$7$b%a!<%k$,=EJ#$7$?(B $B>l9g$O$4MF

Re: 4.5-5.0 kldxref:No such file or directory

* Emiel Kollof ([EMAIL PROTECTED]) wrote: # Calling kldxref(8) for each module is expensive. .if !defined(NO_XREF) .MAKEFLAGS:=${.MAKEFLAGS} -DNO_XREF afterinstall: @if [ -x /usr/sbin/kldref ]; then \ kldxref ${DESTDIR}${KMODDIR}; \ fi .endif Gah! I musn't

Re: 4.5-5.0 kldxref:No such file or directory

On Wed, Mar 13, 2002 at 04:13:35AM +0100, Emiel Kollof wrote: A known issue. The install process deliberately ignores this as a non-fatal error. Why not test for it like this (or similar): [ -x /usr/sbin/kldxref ] /usr/bin/kldxref (etcetera...) If the new CURRENT testers upgrading