RE: One answer, one question.

1999-01-27 Thread Eric J. Chet
On Wed, 27 Jan 1999, Brian Feldman wrote: > On Wed, 27 Jan 1999, Jeroen Ruigrok/Asmodai wrote: > > > Also, I am also not seeing the relevance of ps. Sure, Matthew commited a > > bunch of VM hacks 'n fixes which appear to work nicely here (mayhaps even > > better than the prior stuff) and ps work

Re: DUMMYNET broken in -current ?

1999-05-01 Thread Eric J. Chet
On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: > > I have two machines, the target being a -current SMP box. > > On the source machine I do > ping target > > On the target machine, SMP kernel with IPFW+DUMMYNET: > > ipfw pipe config 1 delay 200ms > ipfw add pipe 1 icmp from a

Re: Losing the battle with RC1

2002-12-13 Thread Eric J. Chet
Hello I have a Thinkpad T23 and to get current to be stable I had to upgrade the the bios. Might help you also. On Fri, 13 Dec 2002, Kevin Oberman wrote: > For the past few days I have been trying to get RC1 running on my old > laptop (IBM ThinkPad 600E). The installation worked pretty

build broken

2002-10-28 Thread Eric J. Chet
Hello I just tried a -current buildworld which failed: --- "/usr/src/gnu/usr.bin/groff/tmac/Makefile", line 2: warning: duplicate script for target "-s" ignored make: don't know how to make doc-common-s. Stop --- Anybody else seeing this? Thanks, Eric To Unsubscribe: send mail to [EMA

Re: Suspicious warnings in -CURRENT

2000-07-07 Thread Eric J. Chet
On Fri, 7 Jul 2000, Alexander N. Kabaev wrote: > After today's buildworld, I am seeing lots of warning messages from libc like: > > expr in free(): warning: modified (chunk-) pointer > > Does it happen to anyone else on this list? > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "u

VMware X11 and -current

1999-08-03 Thread Eric J. Chet
Hello I have been using FreeBSD under vmware for a few weeks now, running 3.2R. Everything has been running good including X11. I upgraded to -current and the linux XF86_vmware server stopped working. When I try and start the xserver I get an error "xf86OpenConsole: cannot open /dev/tty

Re: VMware X11 and -current

1999-08-03 Thread Eric J. Chet
On Tue, 3 Aug 1999, Matthew Dillon wrote: > > :--0-169768575-933691257=:71237 > :Content-Type: TEXT/PLAIN; charset=US-ASCII > : > :Hello > : I have been using FreeBSD under vmware for a few weeks now, > :running 3.2R. Everything has been running good including X11. I upgraded > :to -curren

Re: VMware X11 and -current

1999-08-03 Thread Eric J. Chet
On Tue, 3 Aug 1999, Matthew Dillon wrote: > :> :to -current and the linux XF86_vmware server stopped working. When I try > :> :and start the xserver I get an error "xf86OpenConsole: cannot open > :> :/dev/tty0. I'm running -current as of 8/1/99 with the latest linux_base > :> :port. > :> > :>

Re: VMware X11 and -current

1999-08-03 Thread Eric J. Chet
On Wed, 4 Aug 1999, Bernd Walter wrote: > It needs ttyp0 as tty0 and so on. > I tried it myself under current and got the X11 window. > but it complained that it can't find /proc/cpuinfo. > I never beleaved that it would work after that. Hello It should work, I used it under fbsd-3.2R f

Re: VMware X11 and -current

1999-08-06 Thread Eric J. Chet
On Fri, 6 Aug 1999, Marcel Moolenaar wrote: > "Eric J. Chet" wrote: > > > > On Wed, 4 Aug 1999, Bernd Walter wrote: > > > > > It needs ttyp0 as tty0 and so on. > > > I tried it myself under current and got the X11 window. > > > but it

Re: VMware X11 and -current

1999-08-06 Thread Eric J. Chet
On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote: > > >At this point we must still be in freebsd xinit, then XF86_VMware(linux > >server) get started. I'm running a linux X server under freebsd. Under > >3.2R all I had to do was change the symlink for X to point to XF86_VMware, > >under -current /dev

Re: VMware X11 and -current

1999-08-06 Thread Eric J. Chet
On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote: > >Hello > > > > I had tried it both ways, when I said having them symlinked to > >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I > >use ttyp0 and ttyp4 respectfully. > > I don't think ttyp* will work. I don't know who sug