Marcel Moolenaar wrote:
On Mon, Jun 30, 2003 at 08:10:02PM -0700, Tim Kientzle wrote:
In general I think that the more portable the build tool, the better.
If the shell script is not gross or overly ugly compared to the C
program, then replacing the latter may not be a bad idea.
The attached diff r
TB --- 2003-07-01 04:43:41 - starting CURRENT tinderbox run for amd64/amd64
TB --- 2003-07-01 04:43:41 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-07-01 04:45:46 - building world
TB --- cd /
TB --- 2003-07-01 04:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-07-01 04:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-07-01 04:03:02 - building world
TB --- cd /
On Mon, Jun 30, 2003 at 08:10:02PM -0700, Tim Kientzle wrote:
>
> Looking through the build tools for /bin/sh, it's definitely
> not worth the effort to try copying build tools around.
> Although it sounds easy to add a build-tools target to
> handle this, I'm not sure I see exactly how to do this
Marcel Moolenaar wrote:
On Mon, Jun 30, 2003 at 04:54:02PM -0700, Gordon Tetlow wrote:
That's why ru@ suggested to add a build-tools target. That way you
populate the seperate tree in sync with the phases of a world,
thereby avoiding the phase ordering problem.
Is there a way to leverage the existi
On Monday 30 June 2003 08:34 pm, Jud wrote:
> I think Jesse Guardini's suggestion works when Win and FreeBSD are on the
> same drive. You can still use the NT/2K/XP bootloader when the OSs are on
> different drives, but problem is, I could never figure out exactly what the
> FAQ was trying to tell
On Tue, Jul 01, 2003 at 01:59:03AM +0200, Christian Brueffer wrote:
> Hi,
>
> I've been getting this LOR for some time now:
Alan says this one is harmless.
Kris
pgp0.pgp
Description: PGP signature
* Vincent Poy <[EMAIL PROTECTED]> [ Date: 2003-06-30 ]
[ w.r.t. /usr/src/libexec/talkd notification broken on pty's when user is
using misc/screen ports in -CURRENT ]
> Greetings evertone:
>
> /usr/src/libexec/talkd aka /usr/libexec/ntalkd appears to be broken when
> one runs the screen-3
On Tue, 1 Jul 2003 01:34:36 +0100, Andrew Boothman <[EMAIL PROTECTED]>
wrote:
On Monday 30 June 2003 11:36 pm, Scott Reese wrote:
On Mon, 2003-06-30 at 22:10, Andrew Boothman wrote:
> On Monday 30 June 2003 7:19 pm, Scott Reese wrote:
> > Previously, I had a dual-boot setup with FreeBSD 5.0 and W
On Mon, Jun 30, 2003 at 04:54:02PM -0700, Gordon Tetlow wrote:
> >
> > That's why ru@ suggested to add a build-tools target. That way you
> > populate the seperate tree in sync with the phases of a world,
> > thereby avoiding the phase ordering problem.
>
> Is there a way to leverage the existing
On Monday 30 June 2003 11:36 pm, Scott Reese wrote:
> On Mon, 2003-06-30 at 22:10, Andrew Boothman wrote:
> > On Monday 30 June 2003 7:19 pm, Scott Reese wrote:
> > > Previously, I had a dual-boot setup with FreeBSD 5.0 and Windows XP. I
> > > was using booteasy as the boot loader and I had no pro
Hi,
I've been getting this LOR for some time now:
FreeBSD fangorn.middleearth 5.1-CURRENT FreeBSD 5.1-CURRENT #4: Sun Jun 29 14:39:58
CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/FANGORN i386
lock order reversal
1st 0xc2a4eafc vm object (vm object) @ /usr/src/sys/vm/vm_object.c:432
2nd
On Mon, Jun 30, 2003 at 03:52:06PM -0700, Marcel Moolenaar wrote:
>
> Since you create a seperate object tree for rescue, you need to
> go through the same phases as a world does. That way tools (like
> build-tools) will be compiled against the right headers and linked
> against the right librarie
On Mon, Jun 30, 2003 at 03:28:20PM -0700, Gordon Tetlow wrote:
> On Tue, Jul 01, 2003 at 01:23:53AM +0300, Ruslan Ermilov wrote:
> > Hi there!
> >
> > As seen by the latest series of tinderbox failures,
> > the rescue/ stuff breaks cross compiles. The problem
> > is that some bits like bin/sh hav
Greetings evertone:
/usr/src/libexec/talkd aka /usr/libexec/ntalkd appears to be broken when
one runs the screen-3.9.15_1 from ports and has the pty sessions under
screen. Prior to running screen, ntalkd is showing the incoming talk
request. After running screen, the talk request doesn't show up
On Mon, 2003-06-30 at 22:10, Andrew Boothman wrote:
> On Monday 30 June 2003 7:19 pm, Scott Reese wrote:
> >
> > Previously, I had a dual-boot setup with FreeBSD 5.0 and Windows XP. I
> > was using booteasy as the boot loader and I had no problem booting into
> > either Windows or FreeBSD. Howeve
For those people testing/playing with the driver I posted yesterday, please
take care with it. I've discovered that the receive code is broken and
looses packets, or puts them in funny places in memory. Don't use it on a
valuable machine. I will try and fix it by the end of the week.
Duncan
_
On Mon, 2003-06-30 at 22:14, Doug White wrote:
> On Mon, 30 Jun 2003, Andrew Boothman wrote:
>
> > This seems to be a recurring problem after 5-RELEASE. I had exactly the same
> > problem, and I know of others that are the same. For some reason -current
> > doesn't seem to be inter-operating well
On Tue, Jul 01, 2003 at 01:23:53AM +0300, Ruslan Ermilov wrote:
> Hi there!
>
> As seen by the latest series of tinderbox failures,
> the rescue/ stuff breaks cross compiles. The problem
> is that some bits like bin/sh have the so-called
> "build tools". These are small utilities not normally
>
Hi there!
As seen by the latest series of tinderbox failures,
the rescue/ stuff breaks cross compiles. The problem
is that some bits like bin/sh have the so-called
"build tools". These are small utilities not normally
visible in the world except during the build stage.
As such, "make buildworld"
On Mon, 30 Jun 2003, Andrew Boothman wrote:
> This seems to be a recurring problem after 5-RELEASE. I had exactly the same
> problem, and I know of others that are the same. For some reason -current
> doesn't seem to be inter-operating well with the WinXP/Win2k loader anymore.
> I'm not sure if it
On Monday 30 June 2003 7:19 pm, Scott Reese wrote:
>
> Previously, I had a dual-boot setup with FreeBSD 5.0 and Windows XP. I
> was using booteasy as the boot loader and I had no problem booting into
> either Windows or FreeBSD. However, I found myself having to reinstall
> FreeBSD so I decided t
Please try out the patch at:
http://root.org/~nate/freebsd/ec-burst.diff
This adds support for the embedded controller to use burst mode by
default. It removes our non-working EventWaitIntr() implementation. It
has a debug print that will show:
"EC Waited max 2 cycles"
Please report the m
TB --- 2003-06-30 21:19:57 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-06-30 21:19:57 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-30 21:23:24 - building world
TB
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Mon, Jun 30, 2003 at 09:19:56PM +, Tinderbox wrote:
> TB --- 2003-06-30 20:31:30 - starting CURRENT tinderbox run for ia64/ia64
> TB --- 2003-06-30 20:31:30 - checking out the source tree
> TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
> TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd
TB --- 2003-06-30 20:31:30 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-06-30 20:31:30 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-30 20:33:56 - building world
TB --- cd /home
Peter Holm wrote:
>
> On Mon, Jun 30, 2003 at 03:26:13PM +0200, Eirik Oeverby wrote:
> > Hi,
> >
> > Good to see I'm not the only one.
> > I'm currently going back to a kernel dated 2003.06.27.12.00.00, and I'll test
> > again with that one.
> >
>
> Ok.
>
> I see that alc@ made some recent chang
--On Monday, June 30, 2003 21:46:37 +0200 Juan Francisco Rodriguez Hervella
<[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED]:/usr/home/jrh$ file .eboard/timeseal.FreeBSD
.eboard/timeseal.FreeBSD: 386 compact demand paged pure executable not
stripped
What does this mean ?
it's an old a.out executabl
[EMAIL PROTECTED]:/usr/home/jrh$ file .eboard/timeseal.FreeBSD
.eboard/timeseal.FreeBSD: 386 compact demand paged pure executable not
stripped
What does this mean ?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-cu
On Sun, 29 Jun 2003, Systems Engineering wrote:
> I am attempting an installation via the 5.1-R iso. During the
> partitioning process, fdisk reports that the detected disk geometry is
> probably incorrect. Subsequently, I attempt to specify the geometry
> reported by bios (CSH:19158,255,16). T
Hi,
today my laptop started hanging. after investigating on the console, i
could isolate this problem:
whatever i do, the load keeps growing and the machine stops responding a
few minutes(sometimes 10 or 20) after booting with this message:
swap_pager: indefinite wait buffer: device: ad0s1b, blk
TB --- 2003-06-30 16:49:34 - starting CURRENT tinderbox run for amd64/amd64
TB --- 2003-06-30 16:49:34 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-30 16:51:58 - building world
TB --- cd /
TB --- 2003-06-30 16:00:00 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-06-30 16:00:00 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-30 16:06:49 - building world
TB --- cd /
On Sun, Jun 29, 2003 at 08:13:15PM +, Tinderbox wrote:
>
> mkdep -f .depend -a
> /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sbin/mdmfs/mdmfs.c
> /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sbin/mdmfs/mdmfs.c:53:23:
> pathnames.h: No such file or directory
> mkdep: compil
Hi,
I've found a kernel that works, from the 20th of June.
The regression happened somewhere between 2003.06.20.12.00.00 and
2003.06.27.12.00.00 ... Hope that helps. :)
/Eirik
On Mon, 30 Jun 2003 10:27:08 -0400
Josh Elsasser <[EMAIL PROTECTED]> wrote:
> I think I experienced the same bug on my
Did you rebuild the Vmware kernel module(s) from scratch? Make sure you
do so each time you update to a newer kernel version, as it's important
the data structures referenced by the module be the same version as the
ones referenced by the kernel you're running. I've seen precisely this
output whe
I think I experienced the same bug on my Sony Vaio FX200 with -CURRENT
from Sat Jun 28. I had an unrelated panic, and after rebooting, the
machine locked up after a minute or so during the background fsck.
After rebooting several times, I finally had to boot it single-user
and fsck -y, which did n
Jeff Roberson writes:
> On Fri, 27 Jun 2003, John Baldwin wrote:
>
> >
> > On 27-Jun-2003 Andrew Gallatin wrote:
> > >
> > > Jeff Roberson writes:
> > > >
> > > > Can you call kseq_print(0) and kseq_print(1) from ddb?
> > > >
> > >
> > > I found a different problem which is nearly a
VMWare.
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>
On Mon, 30 Jun 2003, Eirik Oeverby wrote:
> Reinstalling what? VMWare or FreeBSD?
>
> On Mon, 30 Jun 2003, Lutz Bichler wrote:
>
> > I got the same problem/message and
Hi,
Kernel from 27.06 has same behaviour. I would prefer not to have to
install yet another kernel right now, since I need to get some work
done. If anyone else has any possible clues as to when this regression
happened, that would help me (or whoever else would want to test by
adding date=.mm
I've fixed this problem changing the jumpers of the motherboard.
I've changed 2 jumpers:
1. On-board VGA = off
2. IRQ assigned by motherboard (or something like that) = off
And now I've got the Nvidia driver working fine.
Thanks!!!
On Friday 20 June 2003 12:35, Juan Rodriguez Hervella wrote:
>
I get the same problem on a smp machine and my laptop both running
kernels as from today.
On Mon, Jun 30, 2003 at 03:26:13PM +0200, Eirik Oeverby wrote:
> Hi,
>
> Good to see I'm not the only one.
> I'm currently going back to a kernel dated 2003.06.27.12.00.00, and I'll test
> again with that on
Hi,
Good to see I'm not the only one.
I'm currently going back to a kernel dated 2003.06.27.12.00.00, and I'll test
again with that one.
/Eirik
On Mon, 30 Jun 2003, Peter Holm wrote:
> On Mon, Jun 30, 2003 at 01:42:15PM +0200, Eirik Oeverby wrote:
> > Hi folks,
> >
> > I am having some very wei
Hi,
Reinstalling what? VMWare or FreeBSD?
/Eirik
On Mon, 30 Jun 2003, Lutz Bichler wrote:
> I got the same problem/message and "solved" it by reinstalling ;-)
>
> Lutz
>
> --
> Lutz Bichler
> Institute for Software Technology, Department of Computer Science
> Univ. of the Fed. Armed Forces Muni
On Mon, Jun 30, 2003 at 01:42:15PM +0200, Eirik Oeverby wrote:
> Hi folks,
>
> I am having some very weird problems on my laptop,
I can repeat the problem (noticed with savecore) on a
kernel from Jun 30 05:23 UTC:
current# df -h .
FilesystemSize Used Avail Capacity Mounted on
/dev/ad0s1f
From: "Allan Bowhill" <[EMAIL PROTECTED]>
> > When you upgraded to -current, did you read /usr/src/UPDATING?
> > You might find the following entry interesting:
> >
> > 20020831:
> > gcc has been upgraded to 3.2. It is not all binary compatible
> > with earlier versions of gcc f
Hi,
As of yesterday (I think), VMWare 3.2.1 is no longer working on my
5-CURRENT box. When I try to start it, I get
=
[EMAIL PROTECTED] ~$ vmware
Setting TMPDIR=/var/tmp.
VMware Workstation Err
VMware Workstation Error:
Version mismatch with vmmon module: expecting
Hi folks,
I am having some very weird problems on my laptop, which I at first
thought were due to a failing drive. However after a lot of testing and
trial and error I've concluded that it must be a software problem - I'm
smelling filesystem issues or something.
Whenever I transfer large files to
From: "Kenneth D. Merry" <[EMAIL PROTECTED]>
> I sent dmesg and pciconf output last week...I've attached it again.
Thanks. The penny is starting to drop here. A night's sleep does wonders.
When you boot your machine it gets things right:
bcm0: mem 0xfaffe000-0xfaff irq 11
at device 0.
/usr/src/libexec/talkd appears to be broken when one runs the screen
program from ports and creates the pty's. When you try to talk to
someone on the initial login pty, it will show the talk request but in
screen, the talk request doesn't show up with either the talk or ytalk
client unless the tt
51 matches
Mail list logo
