Greg Lehey writes:
> What chip set are you using?
Aladdin (it's a Super Socket 7 motherboard):
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #1: Wed May 12 17:3
NAKAGAWA Yoshihisa writes:
> > Then explain to us why newbus is wrong and why the 4.4BSD scheme is
> > right.
> Because, you are misunderstanding 4.4BSD scheme (and newconfig).
This is pointless. All you're doing is pointing your finger and
screaming "It's not right! It's not fair!" without sayin
I'm using an Alladin chipset in a -current machine...
CPU: AMD-K6(tm) 3D processor (337.19-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x580 Stepping=0
Features=0x8001bf
real memory = 134217728 (131072K bytes)
avail memory = 126808064 (123836K bytes)
chip0: at device 0.0 on pci0
pcib1
On Thu, May 13, 1999 at 09:32:06PM -0500, Thomas T. Veldhouse wrote:
> Have you tried using the C++ standard way? It works.
>
> #include
> #include
>
> using namespace std;
>
> Of course, there are many times you won't want to include the entire
> namespace.
You don't need to. EGCS is still
> This is pointless. All you're doing is pointing your finger and
> screaming "It's not right! It's not fair!" without saying anything of
> actual value.
OK OK, you are right. I have language barrier, so I can't explain
well. I talk other newconfig member, one of member, Furuta-san
will go to Usen
NAKAGAWA Yoshihisa writes:
> OK OK, you are right. I have language barrier, so I can't explain
> well. I talk other newconfig member, one of member, Furuta-san
> will go to Usenix and presentation of newconfig paper.
Any chance of getting a preview of that paper? Is it, or will it be,
available o
> Any chance of getting a preview of that paper? Is it, or will it be,
> available on the Web?
I don't know, probably the paper not yet available on Web. Please
ask to Furuta-san.
--
NAKAGAWA, Yoshihisa
y-nak...@nwsl.mesh.ad.jp
nakag...@jp.freebsd.org
To Unsubscribe: send mail t
Mikhail Teterin wrote:
>
> Mike Smith once wrote:
>
> > For a usable dynamic architecture, loadable modules need to be
> > compiled to support both UP and SMP architectures simultaneously. Thus
> > the locking primitives need to be conditionalised at _runtime_.
>
> What about
>
>
Wilko Bulte wrote:
>
> Sounds very reasonable to me. Running the same command twice to get
> things really clean sounds suspicious ;-)
>
> In any case: I'm rebuilding now after a cvsup && chflags -R noschg
> /usr/obj/* && rm -rf /usr/obj/*
>
> We'll see what happens next.
Nothing will happen, I
"Rodney W. Grimes" wrote:
>
> > I periodically see this one reported, and It is always repaired
> > by the reporter making sure their tree is _really_ clean before
> > doing a make world. "Really clean" means "make cleandir" _twice_,
>
> This indicates to me, the original author of ``cleandir'',
>> In article ,
Dag-Erling Smorgrav writes:
> Any chance of getting a preview of that paper? Is it, or will it be,
> available on the Web?
Nakagawa-san slightly misunderstands. I have no time to write full
paper, so I have already submitted presentation slide.
Instead of it, I will
On Thu, 13 May 1999 23:14:25 +0930, Matthew Thyer wrote:
> This is the PS/2 Intellimouse clone. (I'm note sure if 'real'
> MicroSoft Intellimice work ??).
Mine does under CURRENT.
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the bod
Stefan Bethke wrote:
>
> Any pointer on Forth literature/web pages would be appreciated, especially
> if it's not the ANSI standard (I've looked at it, and it is that: a
> standard, not a reference manual or a tutorial). My Forth knowledge is
> rather rusty, I realised... last time I remember I w
NAKAGAWA Yoshihisa wrote:
>
> > Then explain to us why newbus is wrong and why the 4.4BSD scheme is
> > right.
>
> Because, you are misunderstanding 4.4BSD scheme (and newconfig).
The *GOAL* here is the following:
You bought a computer with the super-ultra-new Microsoft (tm)
Microsoft Bus (tm),
John-Mark Gurney wrote:
>
> I did a couple installs using normal slices and standard MBR, and when
> the machine restarted, I got the "Operating System Missing" error...
> the only way I was able to install on the system was to use dangerous
> dedicated mode... I've seen this happen a couple time
David Schwartz wrote:
>
> Believe it or not, good ideas can even come from people who can't
> code at
> all, and the ideas are just as good. Slapping these people down just ensures
> they don't contribute in the future.
>
> Now if their ideas genuinely are bad, you are more than
On Fri, May 14, 1999 at 02:17:28AM +0200, a little birdie told me
that Sheldon Hearn remarked
>
>
> On Fri, 14 May 1999 01:13:36 +0200, Gianmarco Giovannelli wrote:
>
> > Here it continues to panic with screen, same errors of yesterday... I'll
> > try with X right now but I think it is the same
On Fri, 14 May 1999 07:39:29 EST, "Matthew D. Fuller" wrote:
> I have one here with sources cvsup'd around 4am (CDT) today (as in,
> ~4 hours ago). Start X, start up screen in an xterm, and *bing*.
> However, I strut my skill in manpiluating DDB while staring at a
> frozen X session ;>
Unfortu
Well, this apparently doesn't involve X, only screen.
(X may still be broken/flaky, but this doesn't involve it specifically)
This time I just ran screen on a vty, and *poof*
--
Looking at the trace below, does this look like a (if not the) problem?
#10 0xc0162490 in ttyflush (tp=0xc029dc20,
Ilya Naumov writes:
> GR> I'm currently running into a problem, that when I start my system,
> GR> it spontaneously reboots when starting X. Has anyone else run into
> GR> this?
> yes, i'm experiencing the same problem with today's (May, 12) kernels.
Me three. The box freezes solid before switch
This morning after cvsupping I made a world again, but "screen" continue to
go in panics.
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x14
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc685bd64
stack pointer = 0x10:0xc685bd64
frame pointer =
Dear Soren,
Do you remember that currently your famous driver (after new-bus
announcement) don't probed on ISA hardwsre (in my case Toshiba CDX445)?
Sincerely,
Maxim
?
?
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Of course, DB 2 is still available as an easily installed port/package.
John
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Fri, May 14, 1999 at 11:15:35AM -0400, John R. LoVerso wrote:
> Of course, DB 2 is still available as an easily installed port/package.
Not so easily, it conflict with libc's DB in subtle but harmful manner.
--
Andrey A. Chernov
http://nagual.pp.ru/~ache/
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C
On Fri, May 14, 1999 at 07:21:23PM +0400, Andrey A. Chernov wrote:
> Not so easily, it conflict with libc's DB in subtle but harmful manner.
Talking about upgrades: people on the mutt-dev list say our (outdated) ncurses
is to blame for not dealing properly with SIGWINCH. Newer versions (4.2 at
lea
> Talking about upgrades: people on the mutt-dev list say our (outdated) ncurses
> is to blame for not dealing properly with SIGWINCH.
Works fine with libslang.
> Newer versions (4.2 at least) are said to get it right. Would
> installing the ncurses port be able to cause similar problems?
Mutt
On Fri, May 14, 1999 at 09:17:24AM -0700, David O'Brien wrote:
> Works fine with libslang.
Indeed it does.
--
Jos Backus _/ _/_/_/ "Reliability means never
_/ _/ _/ having to say you're sorry."
_/
Look for that setting in the SCSI BIOS
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org
> [mailto:owner-freebsd-curr...@freebsd.org]on Behalf Of Brian Feldman
> Sent: Thursday, May 13, 1999 7:52 PM
> To: Jordan K. Hubbard
> Cc: Poul-Henning Kamp; Soren Schmidt; Dag-Erling
"Alok K. Dhir" writes:
> Look for that setting in the SCSI BIOS
I think not.
DES
--
Dag-Erling Smorgrav - d...@yes.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On 14 May 1999, Dag-Erling Smorgrav wrote:
> "Alok K. Dhir" writes:
> > Look for that setting in the SCSI BIOS
>
> I think not.
I think not too. EIDE drives tend to not mess with SCSI too much...
>
> DES
> --
> Dag-Erling Smorgrav - d...@yes.no
>
>
> To Unsubscribe: send mail to major
It seems that screen was trying to flush the master pty, before the slave
tty was even open. We were lucky that this didn't crash our machines before
the dev_t changes, it only caused the console to be flushed instead. But
after the dev_t changes, it is fatal. Try this fix (band-aid only, better
fi
Sorry - I spaced. I read 'UltraSCSI', not 'UltraDMA'.
*sheepish grin*
Al
> -Original Message-
> From: Brian Feldman [mailto:gr...@unixhelp.org]
> Sent: Friday, May 14, 1999 1:10 PM
> To: Dag-Erling Smorgrav
> Cc: ad...@forumone.com; Jordan K. Hubbard; Poul-Henning Kamp; Soren
> Schmi
This looks a lot like the "I didn't use 'config -r' to generate my
latest kernel build tree" problem.
> Well, this apparently doesn't involve X, only screen.
> (X may still be broken/flaky, but this doesn't involve it specifically)
> This time I just ran screen on a vty, and *poof*
>
> --
> It seems that screen was trying to flush the master pty, before the slave
> tty was even open. We were lucky that this didn't crash our machines before
> the dev_t changes, it only caused the console to be flushed instead. But
> after the dev_t changes, it is fatal. Try this fix (band-aid only, b
> > This was due to a kludge in mfs implementation. Try change NUMCDEV in
> > kern_conf.c to 255.
>
> Are you saying that there is a bug in the mfs implementation and a fix
> will be commited soon? (and change NUMCDEV until then)
>
> Or are you saying, the mfs implementation is now considered co
In message <199905141824.oaa06...@lor.watermarkgroup.com>, Luoqi Chen writes:
>> > This was due to a kludge in mfs implementation. Try change NUMCDEV in
>> > kern_conf.c to 255.
>>
>> Are you saying that there is a bug in the mfs implementation and a fix
>> will be commited soon? (and change NUMC
On Fri, May 14, 1999 at 01:36:41PM -0400, a little birdie told me
that Luoqi Chen remarked
> Here's the better fix, please let me know if it works,
I won't be in a position to crash this box again until tomorrow, but I'll
give it a whirl then.
Thanks.
> Index: tty_pty.c
> ===
On Fri, 14 May 1999, Luoqi Chen wrote:
> > > This was due to a kludge in mfs implementation. Try change NUMCDEV in
> > > kern_conf.c to 255.
> >
> > Are you saying that there is a bug in the mfs implementation and a fix
> > will be commited soon? (and change NUMCDEV until then)
> >
> > Or are
It seems Maxim Sobolev wrote:
>Dear Soren,
>
>Do you remember that currently your famous driver (after new-bus
>announcement) don't probed on ISA hardwsre (in my case Toshiba CDX445)?
>
Yes, and I have the patches right here, I just need to test it a bit
more and get the time to commit it (hopefu
At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote:
> Are we going to get this license? I am interested in NTFS
> source code a lot...
I would be very careful about getting an NT source license if
your intention is to write NTFS support for some other operating
system. Microsoft is not doing this li
It seems Kevin Day wrote:
>
> I'm using an Alladin chipset in a -current machine...
>
> ad3 is the one getting the heaviest use, from me... However, I notice a few
> things from when I went to the ata driver, from a 3.1 kernel using the wd0
> driver.
>
> The drive is now much slower... While I d
Hi:
I just wanted to say that I really appreciate the work you have/are
doing. The disk drive performance under IDE is very important for the
practical use of FreeBSD.
Thank you!
Rick Whitesel
Scientist
NBase-Xyplex
Eml: rwhite...@nbase-xyplex.com
"They that can give up essential liberty to
A recent commit by "Justin T. Gibbs" :
> Nuke ucmpdi2.c from i386/libkern to serve as a reminder that switch
> statements on 64bit values generate poor code.
Looking thru libkern, many of the functions shouldn't be there since
gcc should be generating in-line code. I believe the following are
"Andrey A. Chernov" wrote:
> On Fri, May 14, 1999 at 11:15:35AM -0400, John R. LoVerso wrote:
> > Of course, DB 2 is still available as an easily installed port/package.
>
> Not so easily, it conflict with libc's DB in subtle but harmful manner.
Only if it is configured with --enable-compat185. J
Maxim Sobolev wrote:
> i586_bzero() bandwidth = -2082577916 bytes/sec
> bzero() bandwidth = 184877056 bytes/sec
It seems that on a fast machines with a lot of cache long type is not
sufficient to print i586_bzero bandwith values in bytes/s (in my case it was
slightly overruned). Following is the
If anyone has applied reasonable stress to a recent MP kernel,
preferrably with X, VESA, VM86, and found it stable, do please report
on your last cvs update time: I, for one, would very much like to
isolate a fairly stable post-newbus world. Presumably this would be
helpful to other readers as we
>Looking thru libkern, many of the functions shouldn't be there since
>gcc should be generating in-line code. I believe the following are
>(or should be) superfluous: adddi3.c anddi3.c ashldi3.c ashrdi3.c
>cmpdi2.c iordi3.c lshldi3.c lshrdi3.c negdi2.c notdi2.c subdi3.c
>ucmpdi2.c udivdi3.c umoddi
On Friday, 14 May 1999 at 14:36:58 +0200, Gianmarco Giovannelli wrote:
>
> This morning after cvsupping I made a world again, but "screen" continue to
> go in panics.
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x14
> fault code = supervisor read, page not present
>
> You bought a computer with the super-ultra-new Microsoft (tm)
> Microsoft Bus (tm), for which you bought the latest and greatest
> device X.
It is extremely vulgar joke. I doubt your character.
--
NAKAGAWA, Yoshihisa
y-nak...@nwsl.mesh.ad.jp
nakag...@jp.freebsd.org
To Unsubscr
In old mail, John Polstra wrote:
>In article <19990424190901.d3a791...@spinner.netplex.com.au>,
>Peter Wemm wrote:
>> ...
>> So: things like:
>> device sio1 at isa? tty port "IO_COM2" tty irq 3
>> become:
>> device sio1 at isa? port IO_COM2 irq3
>
>What do you do about the "ppc" device? Formerl
Bruce Evans wrote:
> In old mail, John Polstra wrote:
>>
>>What do you do about the "ppc" device? Formerly, it needed to be "net
>>irq ..." if the "plip" device was going to be used, but "tty irq ..."
>>otherwise. Which one did you pick?
>
> tty was picked (see isa_compat.h). Also, support for
On Fri, 14 May 1999, Rick Whitesel wrote:
> I just wanted to say that I really appreciate the work you have/are
> doing. The disk drive performance under IDE is very important for the
> practical use of FreeBSD.
>
> Thank you!
I second that - thank you !
Andrew.
--
+--
| Andrew Atrens
From: NAKAGAWA Yoshihisa
y-nakaga> > You bought a computer with the super-ultra-new Microsoft (tm)
y-nakaga> > Microsoft Bus (tm), for which you bought the latest and greatest
y-nakaga> > device X.
y-nakaga>
y-nakaga> It is extremely vulgar joke. I doubt your character.
No, I don't think this is
In message ,
Julian Elischer writes:
>
>On Fri, 14 May 1999, Luoqi Chen wrote:
>
>> > > This was due to a kludge in mfs implementation. Try change NUMCDEV in
>> > > kern_conf.c to 255.
>> >
>> > Are you saying that there is a bug in the mfs implementation and a fix
>> > will be commited soon? (a
54 matches
Mail list logo
