On 30-Oct-99 Andrew Atrens wrote:
> I remember this now, I was one of those that got bit by this problem. What
> I recall is that MTRR support made a dramatic speed improvement, but alas
> was _extremely_ unstable. That was when I had an ATI Expert@Work card.
> Since then I've gotten a 3dfx V
On Sun, 31 Oct 1999, Nik Clayton wrote:
> Folks,
>
> Is there any interest in a /usr/share/calendar/calendar.freebsd file
> (which would actually be in the CVS tree in src/usr.bin/calendar/calendars).
>
> Milestones in FreeBSD development (50 committers, 100 committers, the
> first 1000 ports
> From: "Jonathan M. Bresler" <[EMAIL PROTECTED]>
[snip]
> 7:39PM up 29 mins, 1 user, load averages: 0.24, 0.32, 0.31
> Aspen:[209] uname -a
> FreeBSD Aspen.Bresler.ORG 3.0-CURRENT FreeBSD 3.0-CURRENT #3: Sun Jan
> 17 08:06:24 EST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ASPEN
> i386
> A
Folks,
Is there any interest in a /usr/share/calendar/calendar.freebsd file
(which would actually be in the CVS tree in src/usr.bin/calendar/calendars).
Milestones in FreeBSD development (50 committers, 100 committers, the
first 1000 ports), dates of releases, committer birthdays, that sort
of
i gets lots of "copy-on-write optimized faults". bu tthis may be a
corner case.
just rebooted my box. its used for ppp with nat aliasing and is in the
middle of a cvsup follwed by 'cvs update -PAd'. the box is fairly
weak40MB in a AMD 5x86-133MHz.
Aspen:[208] uptime
7:39PM up 29 mins,
On 1999-10-28 11:30 +0200, Reinier Bezuidenhout <[EMAIL PROTECTED]>
wrote:
> It seems that the qt-1.42 package of current is different than that
> of the 3.3. packages ... I just installed the current version of
> qt-1.42 and now kde 1.1.2 is working fine ...
Well, KDE and Qt are written in C++
On Sat, 30 Oct 1999, Leif Neland wrote:
> On Sat, 30 Oct 1999, Vincent Poy wrote:
>
> > I was just worried
> > that rebooting with a new kernel before a world build might actually
> > render the system bootless.
> >
>
> If you're worried, then just
> cp /usr/src/sys/compile/NAME/kernel /kerne
On Sat, 30 Oct 1999, Vincent Poy wrote:
> I was just worried
> that rebooting with a new kernel before a world build might actually
> render the system bootless.
>
If you're worried, then just
cp /usr/src/sys/compile/NAME/kernel /kernel.new
and reboot, using kernel.new
If it fails, you have
On Sat, 30 Oct 1999, Jordan K. Hubbard wrote:
> > Hmmm, I can understand the build/install portion but will it boot
> > since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE.
>
> Are you still running current, Vince? I thought we established over a
> year a go that -current w
"Peter S. Housel" <[EMAIL PROTECTED]> writes:
> > Ever since the libtermcap / libncurses consolidation, change emacs has
> > problems positioning the cursor and properly updating the screen for
> > character-only devices like the console. It also affects the display
> > in an xterm in non-X mode
> > 2062637 copy-on-write optimized faults <
> [cut]
>
> > I must have something configured wrong, or???
>
> No, but you didn't read Allan's original posting, the change only applied to
> -CURRENT, your box is running -STABLE ...
>
OKOKOKOK! Don't nag me anymore. I forgot, I run current at
> I think a lot of the people who run older versions of -current, and
> upgrade sporadically, have done so because there are particular things
> missing out of -STABLE that they need (or want).
Which is a fair point, and hopefully we'll be branching 4.0 sooner
this time so the wait is not so long
> Hmmm, I can understand the build/install portion but will it boot
> since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE.
Are you still running current, Vince? I thought we established over a
year a go that -current was *not* for you since you don't take the
requisite tim
Chris Costello writes:
> On Sat, Oct 30, 1999, Vincent Poy wrote:
> >Well, I try to stay up to date but there are times when I am busy
> > so things do get behind... I've ran -current since 1993. There is no
> > real reason to use -STABLE.
>
>Give me one single reason why there is
On Sat, 30 Oct 1999, Andrew Atrens wrote:
>
> On Fri, 29 Oct 1999, Brian Fundakowski Feldman wrote:
> >
> > I disabled (or asked Peter to, actually) the K6-2+ MTRR driver a while
> > back because with XFree86 3.9.16 (an alpha which uses MTRR support) it
> > would cause memory corruption. It's
On Sat, Oct 30, 1999, Vincent Poy wrote:
> Well, I try to stay up to date but there are times when I am busy
> so things do get behind... I've ran -current since 1993. There is no
> real reason to use -STABLE.
Give me one single reason why there is on real reason to use
-STABLE and I'l
On Sat, 30 Oct 1999, Will Andrews wrote:
> On 30-Oct-99 Vincent Poy wrote:
> > Hmmm, I can understand the build/install portion but will it boot
> > since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE.
>
> I highly advise that you read the last month's archive of the -curr
On Sat, Oct 30, 1999 at 06:54:07PM +0200, Leif Neland wrote:
>
>
> > I would appreciate it if people running -current would run a "vmstat -s"
> > and tell me if they see a NON-ZERO value for copy-on-write optimized
> > faults. About six months ago, I implemented a simpler and more general
> > o
On 30-Oct-99 Vincent Poy wrote:
> Hmmm, I can understand the build/install portion but will it boot
> since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE.
I highly advise that you read the last month's archive of the -current mailing
list archives: http://docs.FreeBSD.ORG/m
On Fri, 29 Oct 1999, Brian Fundakowski Feldman wrote:
>
> I disabled (or asked Peter to, actually) the K6-2+ MTRR driver a while
> back because with XFree86 3.9.16 (an alpha which uses MTRR support) it
> would cause memory corruption. It's very strange, and something I
> really haven't figured
John Hay wrote:
> Is there anyone that have wine working on -current?
>
> I have tried old binaries of wine that I have compiled and used a few
> months ago on -current and have recompiled them (99.07.31) and have
> also tried the latest (99.09.23), but they all just coredump. It did
> work a few
> I would appreciate it if people running -current would run a "vmstat -s"
> and tell me if they see a NON-ZERO value for copy-on-write optimized
> faults. About six months ago, I implemented a simpler and more general
> optimization at an earlier "fork in the road". (In effect, I avoid
> the
> -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions
> -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o
> /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
> *** Signal 12
...snip...
> Any ideas?
YES. DELETE, YES DELETE, CURRENT FROM YOUR MACH
Is there anyone that have wine working on -current?
I have tried old binaries of wine that I have compiled and used a few
months ago on -current and have recompiled them (99.07.31) and have
also tried the latest (99.09.23), but they all just coredump. It did
work a few months ago, so I would gues
On Sat, 30 Oct 1999, Chris D. Faulhaber wrote:
> On Sat, 30 Oct 1999, Vincent Poy wrote:
>
> > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
> > *** Signal 12
> >
>
> Read /usr/src/UPDATING (19990929 entry) and build/install a new kernel
> before making world
Hmmm, I can
On Sat, 30 Oct 1999, Vincent Poy wrote:
> /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
> *** Signal 12
>
Read /usr/src/UPDATING (19990929 entry) and build/install a new kernel
before making world
-
Chris D. Faulhaber <[EMAIL PROTECTED]> | All the true gurus I've met never
Sy
echo '#include "i386/att.h"' >> tm.h
echo '#include "i386/freebsd.h"' >> tm.h
echo '#include "i386/perform.h"' >> tm.h
cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions
-DIN_GCC -I/usr/obj/usr/src/tmp/usr/
Doug White wrote:
> On Fri, 29 Oct 1999, Ben Rosengart wrote:
> > On Fri, 29 Oct 1999, Doug White wrote:
> > > I still hate the way the signal change was handled.
> > How would you have done it differently? As I understand it, the pain
> > was more or less inevitable.
>
> Perhaps, but there must
28 matches
Mail list logo
