On Tue, Jun 08, 1999 at 02:23:56PM -0700, Satoshi - Ports Wraith - Asami wrote:
* From: Nik Clayton n...@nothing-going-on.demon.co.uk
* On Tue, Jun 08, 1999 at 07:41:13AM +1000, Peter Jeremy wrote:
* My question is: How do I create /usr/local/share/sgml/docbook/catalog?
* It doesn't
On 8 Jun 1999, Joel Ray Holveck wrote:
This wouldn't help the poor sod whose connection gets shot down every
eight days while he's not there and doesn't know what hit him.
If the poor sod hasn't touched his xterm for 8 days, he's either dead
or he doesn't care if it goes away.
Again,
Hi folks,
This thread has degenerated into the kind of dick-waving that suggests
to the responsible list member that it's no longer worth participation.
If you have nothing to say, there are many of us who would be in your
debt if you'd be so kind as to say it.
Ciao,
Sheldon.
To Unsubscribe:
John Baldwin jobal...@vt.edu wrote:
So it would seem that patch and cvs don't interact at all, unless it's a
question of patch 2.5 being able to apply diffs generated by cvs diff.
That is the main problem I have with patch 2.5 -- it completely fails
to apply patches from `cvs diff` unless you
I'm sorry, if this is not the best place to ask, but I know several
Whistle people are active FreeBSD contributors. Does the announcement in
Subject, see also (I hate long URLs):
http://dailynews.yahoo.com/headlines/tc/story.html?s=v/nm/19990609/tc/ibm_whistle_1.html
mean, IBM is to offer
Over the past week and a bit, the INN -CURRENT source tree had a major
upheaval of code, in order to fix the major problem where reader speed
sucked. What used to take 1min to load up a newsgruop now generally
takes mere seconds (no exaggeration, try it)...
The problem is that the new code
CC'ng your suggestion to the 'kernel wizards'...right now, the only thing
I have to work with is the fact that the problems started right after I
upgraded INN to the new code...the rest is basically trying to followup
suggestions...
On Wed, 9 Jun 1999, Richard Michael Todd wrote:
In message
I believe I stumbled over this as well. (As a side note, you can run DDB
over a serial console too, just compile with DDB, and DDB_UNATTENDED so your
system will come back if it unexpectedly panics; on the serial console send
a 'break').
Anyway, I have a simple program that mmap()s a 1Gig file
On Wed, 9 Jun 1999, David E. Cross wrote:
I believe I stumbled over this as well. (As a side note, you can run DDB
over a serial console too, just compile with DDB, and DDB_UNATTENDED so your
system will come back if it unexpectedly panics; on the serial console send
a 'break').
And
by break I mean a serial break condition. Take the Tx line out of your
box and bring it negative 3-5 volts for a short time, that will be a break.
Seriously, the break will need to be sent from the piece of equipment that is
connected to the other end of the serial line. It isn't a telnet
On Wed, 9 Jun 1999, David E. Cross wrote:
by break I mean a serial break condition. Take the Tx line out of your
box and bring it negative 3-5 volts for a short time, that will be a break.
Seriously, the break will need to be sent from the piece of equipment that is
connected to the other
You have more than enough space to do it to. Swap memory is not dumped, only
RAM is... typicall it is dumped to the swap partition. In this case you
have well more than enough.
If your /etc/fstab showed /dev/da3s1b as your 1.6 gig swap partition, you
would add dumpon=/dev/da3s1b to your
On Wed, 9 Jun 1999, David E. Cross wrote:
You have more than enough space to do it to. Swap memory is not dumped, only
RAM is... typicall it is dumped to the swap partition. In this case you
have well more than enough.
Ah, okay, then I mis-read the error ;( I have 1.6gig of swap spread
How hard would it be to add a kernel option that would enable an alternate
key to drop to the debugger? Say have it so that if a keystroke of ~b (as
suggested by one user) came through on the console line, it would drop to
the debugger?
I guess the next question is would this even work once the
I'm running 4.0-current using a snapshot(not using PAO) from 5-20-99 on a
dell Latitude. I installed over 3.2 and it works fine. I attempted to
build a new kernel. The kernel config and make went ok however the make
install caused the machine to crash and reboot. I figured it was because
I
It seems John Sconiers wrote:
I'm running 4.0-current using a snapshot(not using PAO) from 5-20-99 on a
dell Latitude. I installed over 3.2 and it works fine. I attempted to
build a new kernel. The kernel config and make went ok however the make
install caused the machine to crash and
Now that file systems options such as CD9660, MFS and NFS can be loaded
dynamically
do lines like
options CD9660_ROOT #CD-ROM usable as root device
still need to occur in our kernel config files if we want them usable as root
devices?
#;^)
--
So ya want ta here da
Hmm, I've run -current on my Latitude since I got it, and it hasn't
failed on me yet... I havn't installed on it lately though, its just
getting make world'ed pretty often...
Thanks...I'll just cvsup and make world tonight.
JOHN
To Unsubscribe: send mail to majord...@freebsd.org
with
On Wed, 9 Jun 1999, The Hermit Hacker wrote:
And today's trick question...how do you send a break? :( I'm telnet'd
into a Livingston Portmaster, with 'telnet -E' to disable the telnet
break...
Any particular reason you're using the -E option? The easiest way to send
a serial break on most
On Wed, 9 Jun 1999, Jasper O'Malley wrote:
On Wed, 9 Jun 1999, The Hermit Hacker wrote:
And today's trick question...how do you send a break? :( I'm telnet'd
into a Livingston Portmaster, with 'telnet -E' to disable the telnet
break...
Any particular reason you're using the -E
And today's trick question...how do you send a break? :( I'm telnet'd
into a Livingston Portmaster, with 'telnet -E' to disable the telnet
break...
Any particular reason you're using the -E option? The easiest way to send
a serial break on most terminal servers is hitting the telnet escape
Hi,
I've been trying to install 19990604-CURRENT on a couple of SC450NX
boxes. It works fine with 2 cpu's, but an SMP kernel with 4 cpu's
falls over very quickly (I think while it's setting up the APIC
stuff, or very shortly after - the messages about APIC bus ids appear
on the screen very
Hi,
I've been trying to install 19990604-CURRENT on a couple of SC450NX
boxes. It works fine with 2 cpu's, but an SMP kernel with 4 cpu's
falls over very quickly (I think while it's setting up the APIC
stuff, or very shortly after - the messages about APIC bus ids appear
on the screen
In reply:
Hi,
I've been trying to install 19990604-CURRENT on a couple of SC450NX
boxes. It works fine with 2 cpu's, but an SMP kernel with 4 cpu's
falls over very quickly (I think while it's setting up the APIC
stuff, or very shortly after - the messages about APIC bus ids appear
Do you mean messages like these?
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000
cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000
io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec0
By the time
subscribe
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
subscribe freebsd-current
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
interesting. then why the delay in bringing up the AP? Note in the
dmesg output below, that the AP only comes up during th SCSI delay. I
have also added other comments to the following output.
The APs need the giant kernel lock when initializing the
local APIC and printing the launched
In article local.mail.freebsd-current/199906092225.saa01...@par28.ma.ikos.com
you write:
Also in trying to figure this out I looked at the DRAM probing
code in /usr/src/sys/i386/i386/machdep.c:getmemsize(), and it looks
as though it's not safe for 2GB (e.g. comparisons of byte addresses
against
In reply:
interesting. then why the delay in bringing up the AP? Note in the
dmesg output below, that the AP only comes up during th SCSI delay. I
have also added other comments to the following output.
The APs need the giant kernel lock when initializing the
local APIC and printing
The Hermit Hacker wrote:
How hard would it be to add a kernel option that would enable an alternate
key to drop to the debugger? Say have it so that if a keystroke of ~b (as
suggested by one user) came through on the console line, it would drop to
the debugger?
Would be most excellent if
31 matches
Mail list logo
