In message [EMAIL PROTECTED], Matthew
Jacob writes:
Well, I am truly f*cked now. I read enough of this thread, saw nothing new
in UPDATING, and did the following:
alpha
kernel from today
MAKEDEV from today
(but not a make world install- the binaries/libs are ~week old)
In message [EMAIL PROTECTED], Matthew
Jacob writes:
Well, I am truly f*cked now. I read enough of this thread, saw nothing new
in UPDATING, and did the following:
alpha
kernel from today
MAKEDEV from today
(but not a make world install- the binaries/libs are ~week
In message [EMAIL PROTECTED], Matthew
Jacob writes:
Sorry- maybe more of an edge case. It really has to do with 'ad' support
seemingly vanishing from the alpha. Or, rather, it's hard to say exactly
what has happened:
Mounting root from ufs:/dev/rad0a
no such device 'rad'
Bruce and Mike smith
In message [EMAIL PROTECTED], Matthew
Jacob writes:
Sorry- maybe more of an edge case. It really has to do with 'ad' support
seemingly vanishing from the alpha. Or, rather, it's hard to say exactly
what has happened:
Mounting root from ufs:/dev/rad0a
no such device 'rad'
Bruce
Kazutaka YOKOTA wrote:
I'm using non-standard 100x37 console mode on my notebook, because in 80x25
text mode letters seems too big for my 12' panel, while other modes doesn't
cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600
100x37 mode (instead of default 80x25)
On Fri, 3 Dec 1999, Mike Heffner wrote:
Hi,
I have recently noticed that the irqs for my PCI devices are being screwed up
somehow. It is easily noticeable with dmesg, the correct one's are in paren.:
Is this an SMP box by any chance? Does the kernel work with the irqs which
it chose?
--
Kazutaka YOKOTA wrote (1999/12/03):
This strange behavior was reported several times in the past. It must
be related to screen update logic in syscons. But, I don't think we
have successfully fixed it at that time :-(
It's time to analyze the problem again...
Yes. I know about this problem
Tried to build ssh2 (after installing ssh1) from the ports, and I got the
following error:
SHELL@:No such file or directory
I added USE_GMAKE= yes to the security/ssh2/Makefile, and tried it again
and it completed successfully. Has anyone else came across this?
Davec
--
[EMAIL
thanks for the responses!
"make" and "make install" worked fine with the newest port changes, but when
making the handbook jade dumped core at last. Memory consumption raised
to over 30 MByte before the core dump.
I made a mistake in the former posting as i tried to compile
jade-1.2.2.tar.gz
Yes. I know about this problem too but I have no time to fix and test
it. Is anybody interested in bug reports? ;-)
* Left margin moving to the right is related to the screen width not
divisible by 8 and an use of tabulators at the end of line after the
last valid tab position. So the same
Cejka Rudolf wrote:
Kazutaka YOKOTA wrote (1999/12/03):
This strange behavior was reported several times in the past. It must
be related to screen update logic in syscons. But, I don't think we
have successfully fixed it at that time :-(
It's time to analyze the problem again...
Yes.
Thanks Nick, my USB mouse works perfectly now.
On Thu, 2 Dec 1999, Nick Hibma wrote:
The problem is that the mouse doesn't work (its not a hardware problem),
all I get whenever I move the mouse are lots of the following messages
on the console:
Discarded 7 bytes in queue
This
On 03-Dec-99 Doug Rabson said:
| On Fri, 3 Dec 1999, Mike Heffner wrote:
|
| Hi,
|
| I have recently noticed that the irqs for my PCI devices are being screwed
| up
| somehow. It is easily noticeable with dmesg, the correct one's are in
| paren.:
|
| Is this an SMP box by
I had the same type of problem compiling rpm (so I could install the latest
linux_base to try vmware) My problem turned out to be I had autoconf 2.12
installed and I needed 2.13 the @SHELL@ is supposed to be substituted by
configure, but wasn't because of the autoconf bit.
Check your autoconf.
On Fri, 03 Dec 1999 09:55:43 -0500 (EST), Mike Heffner [EMAIL PROTECTED] said:
Yes, it is a SMP box, and yes, the devices work fine. I just thought it was odd
that the kernel would report incorrect ones.
They are not incorrect. SMP uses a different interrupt system.
-GAWollman
--
Garrett
With todays' build, the previous problems went away. Other problems have
replaced them (sio's wierd again for alpha), but that's a different
story.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I just upgraded a server from 2.2.8 to -current (991201 kernel) and am
seeing some NFS corruption. It looks like byte ranges are getting
zeroed out by the client (or not getting written at all, and the server
at the other end is filling with zeros?). I've seen it while writing
to both a
Mike Heffner wrote:
On 03-Dec-99 Doug Rabson said:
| On Fri, 3 Dec 1999, Mike Heffner wrote:
|
| Hi,
|
| I have recently noticed that the irqs for my PCI devices are being screw
ed
| up
| somehow. It is easily noticeable with dmesg, the correct one's are in
|
=== usr.sbin/pccard/pccardc
cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static -c
/usr/src/usr.sbin/pccard/pccardc/power.c
/usr/src/usr.sbin/pccard/pccardc/power.c: In function `power_main':
/usr/src/usr.sbin/pccard/pccardc/power.c:79: `PIOCSVIR' undeclared (first use
Has the signal structure problem that hangs native Netscape
been corrected? I haven't seen a definitive "its fixed" statement
recently...
Thanks,
Bruce
--
Hi gang,
I noticed that /src/etc/pccard.conf.sample listed the
Netgear FA410TX card as supported.
Does it still use the ed0 driver? I take it I no longer
need to worry about the PAO additions if I use a build of
-current that lists the FA410TX as supported, right?
Hello!
After cvsuped my source, i try rebuild my -current system...
=== usr.bin/truss
cp /usr/src/usr.bin/truss/../../sys/kern/syscalls.master syscalls.master
/bin/sh /usr/src/usr.bin/truss/../../sys/kern/makesyscalls.sh syscalls.master
/usr/src/usr.bin/truss/i386.co
nf
cp
I noticed that /src/etc/pccard.conf.sample listed the
Netgear FA410TX card as supported.
Does it still use the ed0 driver? I take it I no longer
need to worry about the PAO additions if I use a build of
-current that lists the FA410TX as supported, right?
Yes. Note
I've been experiencing more strange crashes. I've been getting them about once or
twice a day lately, but only if I'm running my testing for the FreeBSD-audit project.
I'm basically brute forcing the FreeBSD toolchain, and reporting the results to the
audit mailing list. Unfortunatly, the
Sergey Osokin wrote:
Hello!
After cvsuped my source, i try rebuild my -current system...
Please re-cvsup. There was a longish delay between 2 related commits.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking Databases http://www.scc.nl/
The
In message [EMAIL PROTECTED], Ustimenko S
emen writes:
Hi!
Promised somewhere in spring, i am now
almost ready to put HPFS driver into current.
So i have question:
Where have to go driver sources
src/sys/hpfs or src/sys/i386/hpfs, or something else ?
Where have to go mount_hpfs:
Well, it seems like RPCMNT_UMNTALL call always fails with RPC_SYSTEMERROR on
all systems except FreeBSD. I tested HP/UX, AIX and Solaris boxes - they all
behave identically as follows:
rpc.umntall -h $HOST always fails
rpc.umntall -h $HOST -p $DIR - works just fine since it is using
Actually, I don't think so. I'm not 100% sure, but I think that you end
up in the interrupt handler for the card that's going away, but with tty
interrupts masked so you can't get back into DDB. If it's a modem card,
then you'll have them masked as well.
I'm _fairly_ sure that you'll
Garrett Wollman wrote:
On Fri, 03 Dec 1999 09:55:43 -0500 (EST), Mike Heffner [EMAIL PROTECTED] said:
Yes, it is a SMP box, and yes, the devices work fine. I just thought it was odd
that the kernel would report incorrect ones.
They are not incorrect. SMP uses a different interrupt
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/reader.c
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/skeleton.c
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/symtab.c
cc -O -pipe
What is beast? I was happily able to build -current at about 5 this
morning on a pc164.
On Fri, 3 Dec 1999, Jordan K. Hubbard wrote:
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/reader.c
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c
thanks, committed.
For thise wondering this is a netgraph node that can do arbitrary
filtering using the existing bpf engine.
On Fri, 3 Dec 1999, Steven G. Kargl wrote:
*** Makefile.orig Fri Dec 3 16:46:54 1999
--- Makefile Fri Dec 3 16:46:25 1999
***
*** 6,11
It seems that the bktr driver is still broken. I have looked through the
code for the driver, and have yet to find the problem. here is a dmesg
output with the error that seems to be causeing my problem:
bktr0: BrookTree 878 irq 9 at device 17.0 on pci0
bktr0: Hauppauge Model 61291 D110
Warning
What is beast? I was happily able to build -current at about 5 this
morning on a pc164.
It's an Aspen systems DEC Durango PC164 motherboard based system.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 03-Dec-99 Nick Hibma wrote:
Has anyone ever devised a good way to put a module in a port?
Well the skip port creates a module..
Maybe it is the more general question of how to relate modules to
other parts of the base system, like the kernel, downloadable firmware
files, etc.
Urk!
thanks, committed.
For thise wondering this is a netgraph node that can do arbitrary
filtering using the existing bpf engine.
And just when is ipfw going to become a netgraph node 0.5 * :-)
God I wish I had some free time to go play with this code!!
On Fri, 3 Dec 1999, Steven G. Kargl
Kenneth Culver wrote...
It seems that the bktr driver is still broken. I have looked through the
code for the driver, and have yet to find the problem. here is a dmesg
output with the error that seems to be causeing my problem:
bktr0: BrookTree 878 irq 9 at device 17.0 on pci0
bktr0:
Excerpts from FreeBSD-Current: 2-Dec-99 Re: HEADS-UP: bdevs have be.. by
"David O'Brien"@FreeBSD.
At 2MB the Alpha fixit floppy isn't very useful. Nor is there a live
files system for the Alpha. Nor can you even boot sysinstall and get a
shell if you use a serial console. All-in-all
I would like to get OpenSSL imported into -current. I currently have the
build framework almost ready to go, I'm just running some buildworld tests
to make sure it's working properly.
OpenSSL would give a number of potential benefits. Some of the coolest
ones are:
* Precursor to importing
I think you should look at exactly how OpenBSD 2.6 has integrated it
and then report back with your amended proposal. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I think it's high time we expanded our cryptographic support beyond the
bare minimum of DES - anyone violently disagree?
On the contrary; I violently agree!
We need to make OpenSSH work with K5 as a matter of priority.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To
41 matches
Mail list logo
