[hackers removed from Cc to prevent excessive crossposting]
On Sun, 14 Feb 1999, Garrett Wollman wrote:
On Sun, 14 Feb 1999 16:44:37 -0800 (PST), Julian Elischer
jul...@whistle.com said:
The trouble is Doug, that until there IS a developer's guide, the only
person capable if moving PCI
When I try to run wine on FreeBSD 4.0-CURRENT, I get the following
message:
Feb 15 05:19:56 myname /kernel: Patch manager interface is currently
broken. Sorry
Feb 15 05:19:56 myname /kernel: Patch manager interface is currently
broken. Sorry
wine: can't exec 'demo1.exe': error=0
wine: no
I'm also using wine(latest from ports) with 4.0-current and it works for
me (elf kernel).
Donn Miller wrote:
When I try to run wine on FreeBSD 4.0-CURRENT, I get the following
message:
Feb 15 05:19:56 myname /kernel: Patch manager interface is currently
broken. Sorry
Feb 15 05:19:56 myname
Alex Zepeda wrote:
Is a delay needed between the final sync's and the actual power off?
Apparently so. There is/was a recently added sysctl for this purpose.
Poke around in the archives.
Was that sysctl added to the -STABLE branch? I am running 3.1-BETA
and I cannot find it.
-- JMA
Matthew Thyer m...@camtech.com.au writes:
On Sun, 14 Feb 1999, Erik Funkenbusch wrote:
During a make world (usually about 10-20 minutes in on my P100) everything
just comes to a grinding halt. No disk activity, but the screen saver will
kick in (despite the shell being in the middle of
When the writer blocks, the reader runs and uses a buggy loop to read
only the first chunk of input.
On an otherwise idle system, the need_resched() condition seems to be
true always. I would have expected the synchronisation provided by the
sleep(1) to bias need_resched() in the opposite
On Mon, 15 Feb 1999, Donn Miller wrote:
I've got the USER_LDT option in my kernel, and I'm running an `aout'
instead of `elf' kernel.
I thought running a.out systems had been deprecated for -current and was no
longer supported. Since you're running a bleeding-edge codebase anyway, why
haven't
On Fri, 12 Feb 1999 16:56:48 PST, Jaye Mathisen wrote:
mergemaster is your friend.
Mergemaster will help you update /etc/defaults/rc.conf, but you'll need
to use something else to merge changes from that file into /etc/rc.conf
.
Ciao,
Sheldon.
To Unsubscribe: send mail to
Kris Kennaway wrote:
On Mon, 15 Feb 1999, Donn Miller wrote:
I've got the USER_LDT option in my kernel, and I'm running an `aout'
instead of `elf' kernel.
I thought running a.out systems had been deprecated for -current and was no
longer supported. Since you're running a bleeding-edge
On Mon, 15 Feb 1999, Donn Miller wrote:
Kris Kennaway wrote:
On Mon, 15 Feb 1999, Donn Miller wrote:
I've got the USER_LDT option in my kernel, and I'm running an `aout'
instead of `elf' kernel.
I thought running a.out systems had been deprecated for -current and was no
Chuck Robey wrote:
If IO is generic, then printing the type of printer it finds is
meaningless, right? It's going to announce generic no matter what,
then it should stay silent, right? Better to say nothing than to get it
wrong every time, especially with the correct info sitting mere
Donn Miller wrote:
Kris Kennaway wrote:
On Mon, 15 Feb 1999, Donn Miller wrote:
I've got the USER_LDT option in my kernel, and I'm running an `aout'
instead of `elf' kernel.
I thought running a.out systems had been deprecated for -current and was no
longer supported. Since
Brian Feldman wrote:
That sounds like a bug, but the boot: prompt is NOT the new boot loader,
it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you actually
yet to BTX, try boot -c.
Terminology errors abound here. I know, because I made many of them
in the past.
boot0 is the
At the prompt:
set boot_userconfig
boot
Tom Veldhouse
ve...@visi.com
-Original Message-
From: Donn Miller dmm...@bellatlantic.net
To: Kris Kennaway kkenn...@physics.adelaide.edu.au
Cc: curr...@freebsd.org curr...@freebsd.org
Date: Monday, February 15, 1999 6:34 AM
Subject: Re:
On Mon, 15 Feb 1999, Daniel C. Sobral wrote:
Brian Feldman wrote:
That sounds like a bug, but the boot: prompt is NOT the new boot loader,
it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you
actually
yet to BTX, try boot -c.
Terminology errors abound here. I
Ok, so perhaps tweeking the rescheduling changes in kern_subr.c to
not try to do it in the first few thousand bytes copied is the solution?
kern_subr.c can't do that, because `struct uio' doesn't give the original
count.
Would you like to do it or should I? This isn't high priority
Kris Kennaway wrote:
On Mon, 15 Feb 1999, Donn Miller wrote:
I've got the USER_LDT option in my kernel, and I'm running an `aout'
instead of `elf' kernel.
I thought running a.out systems had been deprecated for -current and was no
longer supported. Since you're running a
That sounds like a bug, but the boot: prompt is NOT the new boot loader,
it's the semi-new boot0 (which is quite nice, Mr. Nordier).
'boot:' comes from boot2, actually.
When you actually
yet to BTX, try boot -c.
... and you never get to BTX, you end up the loader.
--
\\ Sometimes
Is a delay needed between the final sync's and the actual power off?
Apparently so. There is/was a recently added sysctl for this purpose.
Poke around in the archives.
Was that sysctl added to the -STABLE branch? I am running 3.1-BETA
and I cannot find it.
No, they were added
Sorry for the cross-posting, but I am running -STABLE and I would
like to hear from -CURRENT users about this problem.
The panic is easily reproducible: simply, try to hard-link a file
from a local filesystem to a NFS-mounted one (yes, I _know_ that
this is non-sense):
mount
Previously on Sun, Feb 14, 1999 at 09:37:01PM -0500, tc...@staff.circle.net
wrote:
: I've been trying to track down a regular, but not
: manually reproducible crash in 3.0-BETA (19990205).
:
: I can't get a crashdump due to a DSCHECK negative
: number bug. I think my swap space of 3+GB is
: too
:Sorry for the cross-posting, but I am running -STABLE and I would
:like to hear from -CURRENT users about this problem.
:
:The panic is easily reproducible: simply, try to hard-link a file
:from a local filesystem to a NFS-mounted one (yes, I _know_ that
:this is non-sense):
:..
:
: mount
:kern_subr.c can't do that, because `struct uio' doesn't give the original
:count.
:
:Would you like to do it or should I? This isn't high priority but it
:should definitely not be rescheduling after the first 96 bytes. That's
:just a waste of cpu.
:
:The waste for rescheduling
On Sat, 13 Feb 1999, Steve Price wrote:
Is anyone out there successfully using a 3Com 3C375 network
controller in there laptop? I got a new Dell Inspiron 7000
that came with one of these jewels and I haven't been able
to find the trick to make it work.
CardBus cards aren't supported.
Isn't it easier to reclassify the bug as uipc_send() wakes up the
reader before it's done appending the data from a write() to the socket
buffer and use my patch? I don't think it makes sense for uipc_send()
to depend on sorwakeup() not actually waking up anyone in certain
situations.
Bill
To
On 15 February 1999, Jose M. Alcaide proclaimed:
Sorry for the cross-posting, but I am running -STABLE and I would
like to hear from -CURRENT users about this problem.
The panic is easily reproducible: simply, try to hard-link a file
from a local filesystem to a NFS-mounted one (yes, I
On Mon, 15 Feb 1999, Doug White wrote:
# CardBus cards aren't supported. Period.
Eek, I didn't realize this was a CardBus card. :{ I quess
this begs the question though, is anyone working on CardBus
support for FreeBSD since this is the 32-bit version of
PCMCIA? Yes I understand they are
Hi.
I saw that my 4-CURRENT box from 8 February dropped to ddb
after my last make world. I rebuilt world today, and the
same problem is occuring. These problems started occuring
after Matt Dillon's changes to the VM system.
What is worrying/troubling is that in single user mode,
the machine is
On Mon, 15 Feb 1999, Steve Price wrote:
On Mon, 15 Feb 1999, Doug White wrote:
# CardBus cards aren't supported. Period.
Eek, I didn't realize this was a CardBus card. :{ I quess
this begs the question though, is anyone working on CardBus
support for FreeBSD since this is the 32-bit
Hi.
I saw that my 4-CURRENT box from 8 February dropped to ddb
after my last make world. I rebuilt world today, and the
same problem is occuring. These problems started occuring
after Matt Dillon's changes to the VM system.
What is worrying/troubling is that in single user mode,
the
On Monday, 15 February 1999 at 18:00:16 -0500, Luoqi Chen wrote:
Hi.
I saw that my 4-CURRENT box from 8 February dropped to ddb
after my last make world. I rebuilt world today, and the
same problem is occuring. These problems started occuring
after Matt Dillon's changes to the VM system.
On Thu, Feb 11, 1999 at 12:53:05PM -0500, Chuck Robey wrote:
My boot messages recently have included a warning about the lo0
interface not setting the ifq_maxlen.
Same here. Rebuilt a few hours ago, and now I see:
IP packet filtering initialized, divert disabled, rule-based forwarding
On Tue, 16 Feb 1999, Jamie Clark wrote:
On Thu, Feb 11, 1999 at 12:53:05PM -0500, Chuck Robey wrote:
My boot messages recently have included a warning about the lo0
interface not setting the ifq_maxlen.
Same here. Rebuilt a few hours ago, and now I see:
IP packet filtering initialized,
Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is
the kernel loader, and they're all by Mr. Nordier.
Wrong again. boot0 is in the MBR, boot1 and boot2 are the bootstrap;
all by Robert. The loader, OTOH, uses Robert's BTX code, Ficl, and a
lot of code derived by me
Can anyone give me a hand with this problem? Machines are dropping like
flies from this, one I haven't managed to get back at all (hangs on
syncing disks). Anyway, this web server runs just fine for 1 - 3 days,
then loses one of it's drives (da1). I'm not a kernel hacker, so I was
looking for
I'd move forward, not back..
take the 3.1 release that will be available in a day or so..
3.0 was a bit experimental still.
On Mon, 15 Feb 1999, T.D. Brace wrote:
Can anyone give me a hand with this problem? Machines are dropping like
flies from this, one I haven't managed to get back at
Chris Tubutis ch...@tci.com writes:
whenever I click a mailto: HREF it inadvertly dumps core.
Does it truly dump core, or does it merely go away?
Can't speak for the original poster, but my Netscrap 4.5 shows the same
behaviour:
[16]a...@darkstar:/alex #/usr/local/netscape/netscape
On Mon, 15 Feb 1999, Mike Smith wrote:
Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is
the kernel loader, and they're all by Mr. Nordier.
Wrong again. boot0 is in the MBR, boot1 and boot2 are the bootstrap;
all by Robert. The loader, OTOH, uses Robert's BTX
Hi, if I load the vesa kld module from loader.rc, in order to
use a high-res splash screen, when X starts the screen is very dim.
Usually I start xdm from ttys, but its the same if I use startx.
The cursor looks normal, its really bright against the dim screen.
Its fine if I don't load vesa and
Hi, if I load the vesa kld module from loader.rc, in order to
use a high-res splash screen, when X starts the screen is very dim.
Usually I start xdm from ttys, but its the same if I use startx.
The cursor looks normal, its really bright against the dim screen.
Its fine if I don't load vesa and
I spent sometime just staring at the subject, before reading the
message, trying to remember if I had been to any FreeBSD drinking
problems thread... :-)
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org
Well, as a computer geek, I have to believe in
Please try the attached patch for /sys/i386/isa/vesa.c and
see if it works.
Kazu
Yes, that worked. No more dim screen.
Thanks alot!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
42 matches
Mail list logo
