can't jump to superuser after buildwerld

2007-04-18 Thread KAYVEN RIESE
okay. i am getting a serious stomach ache. i am looking at this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html and my head is spinning. i don't feel good. i am halfway thru doing something or other sorta the wrong way. right now i got a prompt.. i am

Re: can't jump to superuser after buildwerld

2007-04-18 Thread Andrei Kolu
On Wednesday 18 April 2007 09:26, KAYVEN RIESE wrote: okay. i am getting a serious stomach ache. i am looking at this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html and my head is spinning. i don't feel good. i am halfway thru doing something or other

Re: Jail Resource Limits for 6.x ...

2007-04-18 Thread Miroslav Lachman
Marc G. Fournier wrote: Is anyone looking into merging in the patch available at: http://www.ualberta.ca/~cdjones/cdjones_jail_soc2006.patch That provides both memory and cpu limits on a jail? It appears to be against REL_6 from last years SOC ... Is anyone using it in

[releng_6_2 tinderbox] failure on amd64/amd64

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:28:50 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:28:50 - starting RELENG_6_2 tinderbox run for amd64/amd64 TB --- 2007-04-18 09:28:50 - mkdir /home/gnn/RELENG_6_2 TB --- 2007-04-18 09:28:50 - ERROR: /home/gnn/RELENG_6_2/amd64/amd64: File exists TB

[releng_6 tinderbox] failure on i386/pc98

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:54 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:54 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2007-04-18 09:26:54 - mkdir /home/gnn/RELENG_6/i386/pc98 TB --- 2007-04-18 09:26:54 - cleaning the object tree TB --- 2007-04-18 09:26:54 -

[releng_6_1 tinderbox] failure on i386/pc98

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:53 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:53 - starting RELENG_6_1 tinderbox run for i386/pc98 TB --- 2007-04-18 09:26:53 - mkdir /home/gnn/RELENG_6_1/i386/pc98 TB --- 2007-04-18 09:26:53 - cleaning the object tree TB --- 2007-04-18

[releng_6 tinderbox] failure on i386/i386

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:54 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:54 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2007-04-18 09:26:54 - mkdir /home/gnn/RELENG_6/i386 TB --- 2007-04-18 09:26:54 - mkdir /home/gnn/RELENG_6/i386/i386 TB --- 2007-04-18

[releng_6 tinderbox] failure on amd64/amd64

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:54 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:54 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2007-04-18 09:26:54 - mkdir /home/gnn/RELENG_6/amd64 TB --- 2007-04-18 09:26:54 - mkdir /home/gnn/RELENG_6/amd64/amd64 TB --- 2007-04-18

[releng_6_1 tinderbox] failure on i386/i386

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:53 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:53 - starting RELENG_6_1 tinderbox run for i386/i386 TB --- 2007-04-18 09:26:53 - mkdir /home/gnn/RELENG_6_1/i386 TB --- 2007-04-18 09:26:53 - mkdir /home/gnn/RELENG_6_1/i386/i386 TB --- 2007-04-18

[releng_6_1 tinderbox] failure on amd64/amd64

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:52 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:52 - starting RELENG_6_1 tinderbox run for amd64/amd64 TB --- 2007-04-18 09:26:52 - mkdir /home/gnn/RELENG_6_1/amd64 TB --- 2007-04-18 09:26:52 - mkdir /home/gnn/RELENG_6_1/amd64/amd64 TB ---

[releng_6 tinderbox] failure on sparc64/sparc64

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:54 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:54 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2007-04-18 09:26:54 - mkdir /home/gnn/RELENG_6/sparc64 TB --- 2007-04-18 09:26:54 - mkdir /home/gnn/RELENG_6/sparc64/sparc64 TB ---

[releng_6_1 tinderbox] failure on sparc64/sparc64

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:53 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:53 - starting RELENG_6_1 tinderbox run for sparc64/sparc64 TB --- 2007-04-18 09:26:53 - mkdir /home/gnn/RELENG_6_1/sparc64 TB --- 2007-04-18 09:26:53 - mkdir /home/gnn/RELENG_6_1/sparc64/sparc64 TB

[releng_6 tinderbox] failure on alpha/alpha

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:53 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:53 - starting RELENG_6 tinderbox run for alpha/alpha TB --- 2007-04-18 09:26:53 - mkdir /home/gnn/RELENG_6 TB --- 2007-04-18 09:26:53 - mkdir /home/gnn/RELENG_6/alpha TB --- 2007-04-18 09:26:53 -

[releng_6_1 tinderbox] failure on alpha/alpha

2007-04-18 Thread FreeBSD Tinderbox
TB --- 2007-04-18 09:26:52 - tinderbox 2.3 running on sobu.neville-neil.com TB --- 2007-04-18 09:26:52 - starting RELENG_6_1 tinderbox run for alpha/alpha TB --- 2007-04-18 09:26:52 - mkdir /home/gnn/RELENG_6_1 TB --- 2007-04-18 09:26:52 - mkdir /home/gnn/RELENG_6_1/alpha TB --- 2007-04-18

ath(4) interrupt time

2007-04-18 Thread Kostik Belousov
I have Acer laptop with the Atheros card, identified as [EMAIL PROTECTED]:2:0: class=0x02 card=0x04181468 chip=0x001a168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network subclass = ethernet Corresponding dmesg lines are ath0:

bge watchdog timeout -- resetting problem on recent update

2007-04-18 Thread Jason Chang 張傑生
Dear All, After recent cvsup and make world, my server suffered from the bge watchdog timeout -- resetting problem. Manually revert the bge related source to older version and compiled a new kernel may solve the problem. So I guess the recent committed source does not go well with bge nics

Re: Re: tproxy on freebsd

2007-04-18 Thread Volker
On 12/23/-58 20:59, zen wrote: i don't have a problem with this but i am going to be setting up a similar setup and would appreciate the help a working setup would provide. any help will be appreciated, i could use a sample configuration file regarding this problem. zen others, building a

Re: Re: tproxy on freebsd

2007-04-18 Thread Adrian Chadd
On 18/04/07, Volker [EMAIL PROTECTED] wrote: but with that configuration, still the proxy ip address that visible when my client using the proxy. Don't understand that sentence. What address is visible to whom? And which address do you want to 'hide'? If you don't want to leak your internal

Re: tproxy on freebsd

2007-04-18 Thread Volker
On 04/18/07 14:14, Adrian Chadd wrote: On 18/04/07, Volker [EMAIL PROTECTED] wrote: but with that configuration, still the proxy ip address that visible when my client using the proxy. Don't understand that sentence. What address is visible to whom? And which address do you want to

Re: bge watchdog timeout -- resetting problem on recent update

2007-04-18 Thread Tom Evans
On Wed, 2007-04-18 at 17:38 +0800, Jason Chang 張傑生 wrote: Dear All, After recent cvsup and make world, my server suffered from the bge watchdog timeout -- resetting problem. Manually revert the bge related source to older version and compiled a new kernel may solve the problem. So I guess

Re: bge watchdog timeout -- resetting problem on recent update

2007-04-18 Thread Rong-en Fan
On 4/18/07, Tom Evans [EMAIL PROTECTED] wrote: On Wed, 2007-04-18 at 17:38 +0800, Jason Chang 張傑生 wrote: Dear All, After recent cvsup and make world, my server suffered from the bge watchdog timeout -- resetting problem. Manually revert the bge related source to older version and compiled a

Re: tproxy on freebsd

2007-04-18 Thread jonathan michaels
On Wed, Apr 18, 2007 at 02:25:32PM +0200, Volker wrote: On 04/18/07 14:14, Adrian Chadd wrote: On 18/04/07, Volker [EMAIL PROTECTED] wrote: but with that configuration, still the proxy ip address that visible when my client using the proxy. Don't understand that sentence. What

CARP and em0 timeout watchdog

2007-04-18 Thread Sven Willenberger
I currently have a FreeBSD 6.2-RELEASE-p3 SMP with dual intel PRO/1000PM nics configured as follows: em0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.0.18 netmask 0xff00 broadcast 192.168.0.255 ether

FreeBSD 4 EOL ports tree

2007-04-18 Thread Marc Santhoff
Hi, since I need to use some installations of FreeBSD 4 for a while I'd like to know: Is there any special tag available for checking out the last usable ports tree? By accident I discovered the tag RELEASE_4_EOL on some files. Is this vaild for all ports or only some (not shown in the webcvs)?

Re: FreeBSD 4 EOL ports tree

2007-04-18 Thread Gabor Kovesdan
Marc Santhoff schrieb: Hi, since I need to use some installations of FreeBSD 4 for a while I'd like to know: Is there any special tag available for checking out the last usable ports tree? By accident I discovered the tag RELEASE_4_EOL on some files. Is this vaild for all ports or only some

Re: FreeBSD 4 EOL ports tree

2007-04-18 Thread Marc Santhoff
Am Donnerstag, den 19.04.2007, 01:05 +0200 schrieb Gabor Kovesdan: Marc Santhoff schrieb: Hi, since I need to use some installations of FreeBSD 4 for a while I'd like to know: Is there any special tag available for checking out the last usable ports tree? By accident I

port accessibility/atk broken in RELEASE_4_EOL tree

2007-04-18 Thread Marc Santhoff
Hi, after cvsup'ing to RELEASE_4_EOL compiling accessibility/atk does not work: # make clean all === Cleaning for pkg-config-0.21 === Cleaning for glib-2.12.9 === Cleaning for gmake-3.81_1 === Cleaning for libtool-1.5.22_2 === Cleaning for icu-3.6 === Cleaning for gettext-0.14.5_2 ===

Re: FreeBSD 4 EOL ports tree

2007-04-18 Thread Aristedes Maniatis
On 19/04/2007, at 9:05 AM, Gabor Kovesdan wrote: RELEASE_4_EOL is the tag where the 4.X support was not yet removed. We only started to remove the 4.X support after the tag, thus you should still be able to build ports from the tag on 4.X. My installations use portsnap and so

Asus DVD Writer not recognized

2007-04-18 Thread Marius Nuennerich
Hi list, we've got a Asus DRW-1814BLT here which is not recognized by 6.2. I can't find it neither in dmesg nor in atacontrol. The Bios detects it fine and even Linux. This writer is SATA: http://www.asus.com/products4.aspx?modelmenu=2model=1488l1=6l2=35l3=0 The device is connected to: atapci0:

Re: can't jump to superuser after buildwerld

2007-04-18 Thread KAYVEN RIESE
how in the werld did i manage to remove myself from wheel. i just ran mergemaster -p is there any documentation for that command that would explain the complex nonsense .. well.. maybe i just freeked out. still.. i followed instructions.. granted somebody told me a different procedure (that i

Re: tproxy on freebsd

2007-04-18 Thread zen
Volker wrote: On 04/18/07 14:14, Adrian Chadd wrote: On 18/04/07, Volker [EMAIL PROTECTED] wrote: but with that configuration, still the proxy ip address that visible when my client using the proxy. Don't understand that sentence. What address is visible to whom? And which

Re: tproxy on freebsd

2007-04-18 Thread zen
Adrian Chadd wrote: A little birdie has told me that this mode of transparent client-spoofing is possible with FreeBSD with a little kernel hackery (much less than whats needed for TPROXY.) Maybe someone who knows the code better than I could comment on how difficult it'd be to add in

Re: Yet Another Screenshot of a GNOME 2.18 Desktop

2007-04-18 Thread Ivan Voras
John Merryweather Cooper wrote: See attached URL. This is a Screenshot of GNOME 2.18 on my Dell 5100 Laptop. http://www.borgsdemons.com/images/Screenshot.png It looks like the problem with font size / monitor DPI still isn't solved. (the fonts on a bare-bones Linux Gnome desktop are bigger

Re: tproxy on freebsd

2007-04-18 Thread Adrian Chadd
On 19/04/07, zen [EMAIL PROTECTED] wrote: if there is any such thing , i'm willing to be a tester . i will deploy it on my server and enviroment ( live one) I'm talking to someone about it who has some patches against -current. We'll see what can be done. Thankfully! The solution for FreeBSD

Re: tproxy on freebsd

2007-04-18 Thread zen
Adrian Chadd wrote: On 19/04/07, zen [EMAIL PROTECTED] wrote: if there is any such thing , i'm willing to be a tester . i will deploy it on my server and enviroment ( live one) I'm talking to someone about it who has some patches against -current. We'll see what can be done. i'm glad to

make buildworld on Freebsd 6.2 amd64 stops on ifconfig.l

2007-04-18 Thread sobo
Hi the following occurs when trying to make buildworld once cvsup'd to stable, any idea's? Environment: FreeBSD xxx.xxx.xxx.xxx 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #1: Wed Apr 18 10:29:35 WST 2007 [EMAIL PROTECTED] :/usr/src/sys/amd64/compile/PHEONIX amd64 Description: ld -dc -r -o

Re: FreeBSD 4 EOL ports tree

2007-04-18 Thread Kris Kennaway
On Thu, Apr 19, 2007 at 09:35:21AM +1000, Aristedes Maniatis wrote: On 19/04/2007, at 9:05 AM, Gabor Kovesdan wrote: RELEASE_4_EOL is the tag where the 4.X support was not yet removed. We only started to remove the 4.X support after the tag, thus you should still be able to build ports

Re: port accessibility/atk broken in RELEASE_4_EOL tree

2007-04-18 Thread Kris Kennaway
On Thu, Apr 19, 2007 at 02:03:36AM +0200, Marc Santhoff wrote: Hi, after cvsup'ing to RELEASE_4_EOL compiling accessibility/atk does not work: # make clean all === Cleaning for pkg-config-0.21 === Cleaning for glib-2.12.9 === Cleaning for gmake-3.81_1 === Cleaning for