On Sat, 20 Nov 1999, Byung Yang wrote:
I lowered the optimization level from -O6 to -O and now it shows the cpu
name properly. I was using "-O6 -march=pentium" for the optimization flag
before, but would it affect the performance of the kernela lot if I lower
the optimization flag to -O?
ok/Asmodai wrote:
-On [19991120 04:01], Byung Yang ([EMAIL PROTECTED]) wrote:
as I see the source code, it is not doing what it is supposed to do.. any
suggestions? (it's not a big deal but still it's a bug)
I did not modify any of the source codes.
I think someone else suggeste
On Sat, 20 Nov 1999 23:12:19 +0800, Peter Wemm [EMAIL PROTECTED] said:
IMHO: Either change su to use '-' or forget about it.. I don't recall
whether csh/tcsh attribute anything magic to having the leading "-" or
not..
Same thing as every other shell: a leading `-' means that the shell is
a
I am quite well aware of the mailing list etiquette. I read through many of
them frequently.
Then you're aware that cross posts are also strongly frowned upon,
especially on both -current and -hackers. Only one mailing list at a
time please, no cross posts.
- Jordan
To Unsubscribe: send
printf("CPU: ");
Look again, the AMD identification can fill cpu_model using cpuid.
The code doesn't appear to have changed lately, so if there is a
problem it's probably a matter of some processor being incorrectly
identified as supporting the feature. Or the processor is broken.
I
"Andrey A. Chernov" wrote:
So the question is: should csh/tcsh use setproctitle() or should su be fixed
to not use "_"?
IMHO: Either change su to use '-' or forget about it.. I don't recall
whether csh/tcsh attribute anything magic to having the leading "-" or
not..
On Sat, Nov 20, 1999 at
So the question is: should csh/tcsh use setproctitle() or should su be fixed
to not use "_"?
On Sat, Nov 20, 1999 at 03:18:27AM +0300, Andrey A. Chernov wrote:
With recent -current I got
_su (tcsh)
\___
in "ps ax" instead of
-su (tcsh)
as before.
From su.c:
/* csh strips the
In article [EMAIL PROTECTED]
Brian Fundakowski Feldman [EMAIL PROTECTED] said:
1. /usr/libexec/cpp now has no predefined symbols like __FreeBSD__,
which makes imake unable to detect OS type automatically.
I'm certain XFree86 should build using gcc -E and not the C preprocessor
if they used an MII transceiver, then it should work okay, but if
not you could be in for trouble. I wish I didn't have to say that,
but I just don't have the hardware to test with.
You know what I tell people who use that excuse... ;)
- Jordan
To Unsubscribe: send mail to [EMAIL
On Fri, 19 Nov 1999, Poul-Henning Kamp wrote:
If you're using the ata driver, please remove the ad_sleep() call
at the bottom of the adopen() in ata-disk.c and see if that
helps you.
Yes, i am using ata driver, but your suggestion didn't help. Still
same story. Crash dumps are available..
-On [19991120 04:01], Byung Yang ([EMAIL PROTECTED]) wrote:
as I see the source code, it is not doing what it is supposed to do.. any
suggestions? (it's not a big deal but still it's a bug)
I did not modify any of the source codes.
I think someone else suggested lowering the optimisation level
On Sat, 20 Nov 1999, Blaz Zupan wrote:
With the following patch my kernel compiles and the NE2000 is correctly
probed. I guess the reason why this #ifdef has been put in has since
disappeared.
I suspect so. Fixed.
*** sys/dev/ed/if_ed_pci.c.orig Fri Oct 15 05:12:47 1999
---
Mike Smith wrote:
Does anybody can explain why kernel with NewATA driver booted on machine
with ISA based IDE adapter trying to mount wd* as root f/s, while
exactly *the same* kernel booted on PCI based mobo mounts ad* as root?
/etc/fstab ?
No, I do not talking about
I have a WaveLan card and a PCI Compex NE2000 compatible in the same
machine. For the Wavelan I need to have pccard compiled in. The NE2000 is
not recognized by the kernel, after closer examination I see that the
compilation of if_ed_pci.c is conditional on pccard (if pccard is in the
system,
Could someone with MSS compatible non-Yamaha card (AD1848, Opti 931, Gus
PnP, ...) and using newpcm please check out the patch in PR kern/14634 and
report to me if the mixer synth and CD are correct after the patch?
If not, could you please try the below patch and see if this is a no-op on
your
Hi,
I am running 4.0-current of:
FreeBSD gmarco.eclipse.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Nov 18
09:33:43 CET
1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GMARCO i386
But I have now a lot of errors (as you can see in this logs) on my scsi chain.
I had never experienced such
Matthew Jacob [EMAIL PROTECTED] wrote:
Too many people have objected. I didn't make my case clearly enough,
but because enough people of have raised issues, the default won't
be changed.
Too bad. I think your idea was absoultely right, and i'm rather tired
myself to have to `fix' it for
"Rodney W. Grimes" [EMAIL PROTECTED] wrote:
Can you give me a model of a QIC drive that has the ``can't write 2
FM's'' and I'll see if I can find one so that I can see this problem
first hand and propose a solution to it.
The problem with QIC drives is that they only support writing at BOM
On Sat, 20 Nov 1999, J Wunsch wrote:
Matthew Jacob [EMAIL PROTECTED] wrote:
Too many people have objected. I didn't make my case clearly enough,
but because enough people of have raised issues, the default won't
be changed.
Too bad. I think your idea was absoultely right, and i'm
Back when we were closing in on the release date for 3.3, I sent
the following message. As we now close in on the release date
for 3.4, I thought I'd send it again, seeing that both of the
problem reports are still marked "open", and neither of the two
patches have been applied yet. (not even
The diagnostic is relatively harmless, but it suggests that /etc/fstab
is wrong.
Here is fstab line, please point what is wrong?
/dev/da0s4a / ufs rw,userquota 1 1
I have no idea; it'd be handy to know what it's trying to mount that's
failing, but I don't
As Andrey A. Chernov wrote ...
What this means? What actions required?
It was a problem recently which cause my kernel paniced
after boot, but now I got this diagnostic instead of panic:
/kernel: Waiting 2 seconds for SCSI devices to settle
/kernel: Creating DISK da0
/kernel:
Does anybody can explain why kernel with NewATA driver booted on machine
with ISA based IDE adapter trying to mount wd* as root f/s, while
exactly *the same* kernel booted on PCI based mobo mounts ad* as root?
/etc/fstab ?
No, I do not talking about /etc/fstab, I'm talking
On Sat, Nov 20, 1999 at 12:48:21PM -0500, Byung Yang wrote:
I lowered the optimization level from -O6 to -O and now it shows the cpu
Offical GCC Project stance is that levels above -O3 are not offically
supported. Above -O3 are experimental (if they are even paid attention
to). Levels above
Is anyone seeing a problem like the one below? This is happening to me on
quite a few binaries that used to be gdb'able before I installed a new
world on the 13th...
[by-tor@volatile:~/mms-0.90$]: gdb ./mms
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered
In the last episode (Nov 20), Donn Miller said:
Thanks. Here is what I tried:
root@lc186 floppies# dd obs=16k conv=osync if=color.gz
of=/dev/rfd0
2453+1 records in
77+0 records out
1261568 bytes transferred in 50.994527 secs (24739 bytes/sec)
It appears to have worked. I guess the
join
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sorry about the multiple posts. I have @home to thank for this. The mail
server said the connection was timing out. Apparently not.
I am quite well aware of the mailing list etiquette. I read through many of
them frequently.
The question itself should remain in the hackers list. Support for
28 matches
Mail list logo
