can't jump to superuser after buildwerld
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 running xfce4, but i can't jump to superuser. i push the button and the laptop shuts down when i want it to. the thing is when i did mergemaster -p i got into big problems i don't understand why. this guy told me how to do vipw like this: TeRReF: In single user mode: mount -a /usr/sbin/vipw then use this inside vipw: :wq That should do it... that helped a lot.. umm.. i felt stupid i guess. i have been using vi for 20 years.. but still.. i really needed this. i feel i need something like this for mergemaster - p or whatever step i should start from. i am sorry for being so stupid. On Thu, 5 Apr 2007, [EMAIL PROTECTED] wrote: i am still trying to follow the below instructions. haven't done so yet, going away for the weekend. // change to root $ su - // remove /usr/obj to speed up the build # cd /usr/obj chflags -R noschg * rm -rf * didn't do this.. but i guess that shouldn't matter. // Build a new world # cd /usr/src # make -j4 buildworld // build a new kernel (do not put any job options for this build) didn't use -j4 but otherwise i believe we did this. # make buildkernel // install the new kernel gheist seemed to be aware of this and had an opinion about not needing it. # make installkernel // reboot to single user mode (boot -s from the loader prompt) # shutdown -r now did this. // After reboot // check + mount all filesystems # fsck -p did this # mount -u / # mount -a -t ufs did merely mount -a # swapon -a // prepare /etc for the world install didn't do this. # mergemaster -p // install the new world this step is where all hell broke loose. i got this strange question that i didn't know how to respond to. my prompt changed. it felt like things went seriously wrong here. # cd /usr/src ; make installworld // run mergemaster again # mergemaster // reboot to an updated system # shutdown -r now All these instructions are in the handbook. Cheers Tom [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html [2] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't jump to superuser after buildwerld
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 sorta the wrong way. right now i got a prompt.. i am running xfce4, but i can't jump to superuser. i push the button and the laptop shuts down when i want it to. the thing is when i did mergemaster -p i got into big problems i don't understand why. this guy told me how to do vipw like this: TeRReF: In single user mode: mount -a /usr/sbin/vipw then use this inside vipw: :wq That should do it... that helped a lot.. umm.. i felt stupid i guess. i have been using vi for 20 years.. but still.. i really needed this. i feel i need something like this for mergemaster - p or whatever step i should start from. i am sorry for being so stupid. Looks like you overwrote your /etc/group file and removed yourself from wheel group. --- wheel:*:0:root,yourname operator:*:5:root,yourname --- So be more careful next time you update your base system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jail Resource Limits for 6.x ...
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 production anywhere? - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) I got same question + one more. Why there are SoC projects, which never come in to src tree or wider publicity? Sometimes it is like wasting of human resources... ;( Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6_2 tinderbox] failure on amd64/amd64
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 --- 2007-04-18 09:28:50 - tinderbox aborted TB --- 0.02 user 0.05 system 0.02 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_2-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on i386/pc98
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 - checking out the source tree TB --- 2007-04-18 09:26:54 - cd /home/gnn/RELENG_6/i386/pc98 TB --- 2007-04-18 09:26:54 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6 src TB --- 2007-04-18 09:26:54 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:54 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:54 - tinderbox aborted TB --- 0.01 user 0.05 system 0.04 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6_1 tinderbox] failure on i386/pc98
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 09:26:53 - checking out the source tree TB --- 2007-04-18 09:26:53 - cd /home/gnn/RELENG_6_1/i386/pc98 TB --- 2007-04-18 09:26:53 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6_1 src TB --- 2007-04-18 09:26:53 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:53 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:53 - tinderbox aborted TB --- 0.02 user 0.03 system 0.04 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_1-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on i386/i386
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 09:26:54 - cleaning the object tree TB --- 2007-04-18 09:26:54 - checking out the source tree TB --- 2007-04-18 09:26:54 - cd /home/gnn/RELENG_6/i386/i386 TB --- 2007-04-18 09:26:54 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6 src TB --- 2007-04-18 09:26:54 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:54 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:54 - tinderbox aborted TB --- 0.05 user 0.02 system 0.04 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on amd64/amd64
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 09:26:54 - cleaning the object tree TB --- 2007-04-18 09:26:54 - checking out the source tree TB --- 2007-04-18 09:26:54 - cd /home/gnn/RELENG_6/amd64/amd64 TB --- 2007-04-18 09:26:54 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6 src TB --- 2007-04-18 09:26:54 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:54 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:54 - tinderbox aborted TB --- 0.02 user 0.04 system 0.04 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6_1 tinderbox] failure on i386/i386
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 09:26:53 - cleaning the object tree TB --- 2007-04-18 09:26:53 - checking out the source tree TB --- 2007-04-18 09:26:53 - cd /home/gnn/RELENG_6_1/i386/i386 TB --- 2007-04-18 09:26:53 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6_1 src TB --- 2007-04-18 09:26:53 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:53 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:53 - tinderbox aborted TB --- 0.03 user 0.03 system 0.03 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_1-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6_1 tinderbox] failure on amd64/amd64
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 --- 2007-04-18 09:26:52 - cleaning the object tree TB --- 2007-04-18 09:26:52 - checking out the source tree TB --- 2007-04-18 09:26:52 - cd /home/gnn/RELENG_6_1/amd64/amd64 TB --- 2007-04-18 09:26:52 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6_1 src TB --- 2007-04-18 09:26:52 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:52 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:52 - tinderbox aborted TB --- 0.03 user 0.04 system 0.05 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_1-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on sparc64/sparc64
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 --- 2007-04-18 09:26:54 - cleaning the object tree TB --- 2007-04-18 09:26:54 - checking out the source tree TB --- 2007-04-18 09:26:54 - cd /home/gnn/RELENG_6/sparc64/sparc64 TB --- 2007-04-18 09:26:54 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6 src TB --- 2007-04-18 09:26:54 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:54 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:54 - tinderbox aborted TB --- 0.03 user 0.03 system 0.03 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6_1 tinderbox] failure on sparc64/sparc64
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 --- 2007-04-18 09:26:53 - cleaning the object tree TB --- 2007-04-18 09:26:53 - checking out the source tree TB --- 2007-04-18 09:26:53 - cd /home/gnn/RELENG_6_1/sparc64/sparc64 TB --- 2007-04-18 09:26:53 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6_1 src TB --- 2007-04-18 09:26:53 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:53 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:53 - tinderbox aborted TB --- 0.03 user 0.03 system 0.03 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_1-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on alpha/alpha
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 - mkdir /home/gnn/RELENG_6/alpha/alpha TB --- 2007-04-18 09:26:53 - cleaning the object tree TB --- 2007-04-18 09:26:53 - checking out the source tree TB --- 2007-04-18 09:26:53 - cd /home/gnn/RELENG_6/alpha/alpha TB --- 2007-04-18 09:26:53 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6 src TB --- 2007-04-18 09:26:53 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:53 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:53 - tinderbox aborted TB --- 0.02 user 0.04 system 0.04 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-alpha-alpha.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6_1 tinderbox] failure on alpha/alpha
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 09:26:52 - mkdir /home/gnn/RELENG_6_1/alpha/alpha TB --- 2007-04-18 09:26:52 - cleaning the object tree TB --- 2007-04-18 09:26:52 - checking out the source tree TB --- 2007-04-18 09:26:52 - cd /home/gnn/RELENG_6_1/alpha/alpha TB --- 2007-04-18 09:26:52 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -rRELENG_6_1 src TB --- 2007-04-18 09:26:52 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2007-04-18 09:26:52 - ERROR: unable to check out the source tree TB --- 2007-04-18 09:26:52 - tinderbox aborted TB --- 0.03 user 0.03 system 0.06 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_1-alpha-alpha.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ath(4) interrupt time
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: Atheros 5212 mem 0xd000-0xd000 irq 22 at device 2.0 on pci6 ath0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xd000 ath0: [GIANT-LOCKED] Driver successfully attaches to the card and wifi connection works nice. There is some problem. At home, where I have no access point, I did ifconfig ath0 up ifconfig ath0 list scan Shortly after then, interrupt time goes to ~95%, top -S accounted the time to the ath0 interrupt thread. After ifconfig ath0 down machine returned to working condition. Some time later I did the same (in different location), while laptop was powered from battery and powerd ran. After short time, machine locked (presumably, due to interrupts being steadily delivered and lowered frequency of the CPU, that cannot cope with the interrupts stream). Other than that, machine is stable, buildworld/port build for several hours did not cause the problems. Any advise how can I help to debug the issue ? pgpNEFLj0v3HI.pgp Description: PGP signature
bge watchdog timeout -- resetting problem on recent update
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 onboard of IBM e326m servers. 1. server model IBM e326m server with dual AMD opteron cpus http://www-304.ibm.com/jct01004c/systems/support/supportsite.wss/docdisplay?brandind=508lndocid=MIGR-61692 bge chipset is Broadcom BCM5714 B3, ASIC rev. 0x8003 2. senario large network i/o results in error: bge0: watchdog timeout -- resetting bge0: link DOWN bge0: link state changed to DOWN bge0: link UP bge0: link state changed to UP 3. how to reproduce just ftp a file larger then 20mb, and the bge will have trouble in 30sec. 4. source version verified to work abnormally. if_bge.c 1.91.2.22 if_bgereg.h 1.36.2.10 brgphy.c 1.34.2.13 5. source version verified to work normally. if_bge.c 1.91.2.19 if_bgereg.h 1.36.2.9 brgphy.c 1.34.2.12 6. system dmesg: Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #13: Sat Apr 14 10:57:10 CST 2007 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/CCSUN52 Preloaded elf kernel /boot/kernel/kernel at 0x8061a000. INTR: Adding local APIC 0 as a target ACPI APIC Table: AMDBLAST Calibrating clock(s) ... i8254 clock: 1193293 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2793019707 Hz CPU: AMD Opteron(tm) Processor 254 (2793.02-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f51 Stepping = 1 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x1LAHF L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 2146828288 (2047 MB) Physical memory chunk(s): 0x1000 - 0x00096fff, 614400 bytes (150 pages) 0x00717000 - 0x7c2fcfff, 2076073984 bytes (506854 pages) avail memory = 2066284544 (1970 MB) INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec0 ioapic0: Routing external 8259A's - intpin 0 MADT: Found IO APIC ID 5, Interrupt 16 at 0xfec01000 MADT: Found IO APIC ID 6, Interrupt 32 at 0xfec02000 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 - intpin 2 lapic0: Routing NMI - LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high lapic1: Routing NMI - LINT1 lapic1: LINT1 trigger: edge lapic1: LINT1 polarity: high MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 9 polarity: low ioapic0: intpin 9 trigger: level ioapic0 Version 1.1 irqs 0-15 on motherboard ioapic1 Version 1.1 irqs 16-31 on motherboard ioapic2 Version 1.1 irqs 32-47 on motherboard cpu0 BSP: ID: 0x VER: 0x00040010 LDR: 0x DFR: 0x lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff timer: 0x000100ef therm: 0x err: 0x0001 pcm: 0x0001 null: null device, zero device random: entropy source, Software, Yarrow mem: memory ichwd module loaded io: I/O acpi0: AMD XSDT on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] acpi0: Power Button (fixed) pci_open(1):mode 1 addr port (0x0cf8) is 0x80016844 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 1 [class=060400] [hdr=01] is there (id=00361166) AcpiOsDerivePciId: bus 0 dev 24 func 1 unknown: I/O range not supported ACPI timer: 0/4 0/5 0/4 0/4 0/4 0/4 0/3 0/4 0/4 0/4 - 0 Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x508-0x50b on acpi0 pci_link0:Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 10 11 Validation 0 10 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link1:Index IRQ Rtd
Re: Re: tproxy on freebsd
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 transparent proxy using pf + squid is an easy topic and well documented on the net. In detail, it's going that way: pf (assuming nve0 is your local IF): rdr on nve0 from any to any port 80 - 127.0.0.1 port 3128 pass in on nve0 from any to any port 80 keep state pass in on nve0 from any to 127.0.0.1 port 3128 keep state Now, compile squid with transparent support and use: 'http_port 3128 transparent' in your squid.conf (assuming you're running squid = 2.6). I'm running several hosts with a setup like that. Also you may want to check out www/havp and use it as a transparent proxy + squid as upstream proxy. That way you also have virus protection for your internal users while surfing the web (I'm also doing things like that as I found it a better solution that squidclam or the like - YMMV). FYI i already running transparent proxy with ipf+ipnat,: rdr nve0 0.0.0.0/0 port 80 - 122.x.x.x port 3128 tcp 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 addresses to any outside webserver, this is a squid issue and there should (?) be configuration options for squid. is it me or just i cant achieve that with FreeBSD? because i hate to switch to other OS only because of this. No need to switch! :) You may find tons of infos using google or in the ML archives [EMAIL PROTECTED] Also pf@ or isp@ would be the appropriate list for questions like that. HTH, Volker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: tproxy on freebsd
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 addresses to any outside webserver, this is a squid issue and there should (?) be configuration options for squid. He means fully transparent - ie, client thinks its talking to the server; server thinks its talking to the client; proxy server IP isn't visible to either. Adrian -- Adrian Chadd - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tproxy on freebsd
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 'hide'? If you don't want to leak your internal addresses to any outside webserver, this is a squid issue and there should (?) be configuration options for squid. He means fully transparent - ie, client thinks its talking to the server; server thinks its talking to the client; proxy server IP isn't visible to either. Adrian Adrian, thanks, I got it. Talking about real transparent proxy not just a transparent one... ;) Unfortunately I don't have a solution for that as I'm using mostly NATed environments and it doesn't make sense to hand out private address space to a web server. Volker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bge watchdog timeout -- resetting problem on recent update
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 the recent committed source does not go well with bge nics onboard of IBM e326m servers. Hi Jason Can you add hw.pci.enable_msi=0 hw.pci.enable_msix=0 to /boot/loader.conf and reboot and see if that solves the problem. I saw this problem a while ago on my -CURRENT with a misbehaving MSI on my motherboard. (I may have this completely wrong; I'm not even 100% sure the MSI stuff has been MFC'ed to -STABLE). Cheers Tom signature.asc Description: This is a digitally signed message part
Re: bge watchdog timeout -- resetting problem on recent update
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 new kernel
may solve the problem. So I guess the recent committed source
does not go well with bge nics onboard of IBM e326m servers.
Hi Jason
Can you add
hw.pci.enable_msi=0
hw.pci.enable_msix=0
to /boot/loader.conf and reboot and see if that solves the problem.
I saw this problem a while ago on my -CURRENT with a misbehaving MSI on
my motherboard. (I may have this completely wrong; I'm not even 100%
sure the MSI stuff has been MFC'ed to -STABLE).
MSI stuffs are MFC'ed to 6.x since April 1 by jhb@, but I
thought to use MSI, one MUST set hw.pci.enable_{msi,msix} to
1 in loader.conf as the commit log said.
But from the revision changes that Jason posted, the most
suspicious part is MSI...
Regards,
Rong-En Fan
Cheers
Tom
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tproxy on freebsd
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 address is visible to whom? And which address do you want to 'hide'? If you don't want to leak your internal addresses to any outside webserver, this is a squid issue and there should (?) be configuration options for squid. He means fully transparent - ie, client thinks its talking to the server; server thinks its talking to the client; proxy server IP isn't visible to either. Adrian Adrian, thanks, I got it. Talking about real transparent proxy not just a transparent one... ;) not sure i understand this one, a real transparent not just a tra.. Unfortunately I don't have a solution for that as I'm using mostly NATed environments and it doesn't make sense to hand out private address space to a web server. i was assigned a class c some 15 years ago and its getting used for all sorts of admin stuff/disabled user client stuff and other stuff that i cannot sort out 'netting/natting for' most kind regards and appreciations jonathan thanks all ... adrian volker and zen if i forgot somebody sorry. -- powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system === appropriate solution in an inappropriate world === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
CARP and em0 timeout watchdog
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 00:30:48:8d:5c:0a media: Ethernet autoselect (1000baseTX full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 4096 options=bRXCSUM,TXCSUM,VLAN_MTU inet 10.10.0.18 netmask 0xfff8 broadcast 10.10.0.23 ether 00:30:48:8d:5c:0b media: Ethernet autoselect (1000baseTX full-duplex) status: active the em0 interface connects to the LAN while the em1 interface is connected to an identical box via CAT6 crossover cable (for ggate/gmirror). Now, I have also configured a carp interface: carp0: flags=49UP,LOOPBACK,RUNNING mtu 1500 inet 192.168.0.20 netmask 0x carp: MASTER vhid 1 advbase 1 advskew 0 There are twin boxes here and I am running Samba. The problem is that with transfers across the carp IP (192.168.0.20) I end up with em0 resetting after a watchdog timeout error. This occurs whether I transfer files from a windows box using a share (samba) or via ftp. This problem does *not* occur if I ftp to the 192.168.0.19 interface (non-virtual). I suspected cabling at first so had all the cabling in question replaced with fresh CAT6 to no avail. Several gigs of data can be transferred to the real interface (em0) without any issue at all; a max of maybe 1 - 2 Gig can be transferred connected to the carp'ed IP before the em0 reset. Any ideas here? Sven ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 4 EOL ports tree
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)? Thanks, Marc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4 EOL ports tree
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 (not shown in the webcvs)? Thanks, Marc Hello Marc, 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. Regards, Gabor ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4 EOL ports tree
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 discovered the tag RELEASE_4_EOL on some files. Is this vaild for all ports or only some (not shown in the webcvs)? Thanks, Marc Hello Marc, 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. Regards, Gabor Thank you very much, Marc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
port accessibility/atk broken in RELEASE_4_EOL tree
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 === Cleaning for ldconfig_compat-1.0_8 === Cleaning for expat-2.0.0_1 === Cleaning for libiconv-1.9.2_2 === Cleaning for rc_subr-1.31_1 === Cleaning for atk-1.9.1 === Vulnerability check disabled, database not found === Extracting for atk-1.9.1 = MD5 Checksum OK for gnome2/atk-1.9.1.tar.bz2. === Patching for atk-1.9.1 === Applying FreeBSD patches for atk-1.9.1 === atk-1.9.1 depends on executable in : pkg-config - found === atk-1.9.1 depends on shared library: glib-2.0.0 - found === Configuring for atk-1.9.1 === Building for atk-1.9.1 make: cannot open Makefile. *** Error code 2 Stop in /usr/p4/ports.akt/accessibility/atk. Since mostly any gnome2 application uses atk I'd like to ask: Is there a chance to get this error fixed 'officialy'? If I'd know what's the cause I could at least frob it to work here ... TIA, Marc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4 EOL ports tree
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 automatically went past the correct tag. Is there a way to get portsnap to downgrade the ports tree now to 4_EOL or is the best way to install cvsup and do it? Ari Maniatis -- ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Asus DVD Writer not recognized
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: JMicron JMB363 SATA300 controller port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f mem 0xfbefe000-0xfbef irq 40 at device 0.0 on pci2 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc400 atapci0: [MPSAFE] atapci0: Reserved 0x2000 bytes for rid 0x24 type 3 at 0xfbefe000 atapci0: AHCI Version 01.00 controller with 2 ports detected Or: atapci1: VIA 8237A SATA150 controller port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f,0xb000-0xb0ff irq 21 at device 15.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xb400 atapci1: [MPSAFE] atapci1: Reserved 0x100 bytes for rid 0x24 type 4 at atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xbc00 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xb880 Neither works. Any ideas what to try? Thanks in advance Marius ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't jump to superuser after buildwerld
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 posted and was editited out from below) and it made mergemaster -p act in a way that i didn't feel prepared for. right now.. as i explained in the other posting, i didn't really follow all the instructions on the makewerld page given below.. but i am a bit afraid to just jump in the middle somewhere.. hrm.. i guess starting from the beginning might be right but.. ooo.. i am getting that stomache ache agin. btw.. i dropped to single user mode, vi'ed /etc/group according to the instruction and i am now able to jump to root again. thx a bunch for that! On Wed, 18 Apr 2007, Andrei Kolu wrote: 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 sorta the wrong way. right now i got a prompt.. i am running xfce4, but i can't jump to superuser. i push the button and the laptop shuts down when i want it to. the thing is when i did mergemaster -p i got into big problems i don't understand why. this guy told me how to do vipw like this: TeRReF: In single user mode: mount -a /usr/sbin/vipw then use this inside vipw: :wq That should do it... that helped a lot.. umm.. i felt stupid i guess. i have been using vi for 20 years.. but still.. i really needed this. i feel i need something like this for mergemaster - p or whatever step i should start from. i am sorry for being so stupid. Looks like you overwrote your /etc/group file and removed yourself from wheel group. --- wheel:*:0:root,yourname operator:*:5:root,yourname --- So be more careful next time you update your base system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tproxy on freebsd
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 address do you want to 'hide'? If you don't want to leak your internal addresses to any outside webserver, this is a squid issue and there should (?) be configuration options for squid. He means fully transparent - ie, client thinks its talking to the server; server thinks its talking to the client; proxy server IP isn't visible to either. Adrian Adrian, thanks, I got it. Talking about real transparent proxy not just a transparent one... ;) Unfortunately I don't have a solution for that as I'm using mostly NATed environments and it doesn't make sense to hand out private address space to a web server. well actualy is not private address, i work for small ISP and the proxy supose to be caching all our clients requests. and it supose to be that our clients ip is visible to the server, not our proxy. i wish FreeBSD have solutions for this, just hate to discovered the weakness of FreeBSD. and most of all i hate to switch to other OS. Volker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] TIA Zen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tproxy on freebsd
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 functionality to FreeBSD to spoof the local IP of a connected socket for outbound connections. This of course assumes symmetric traffic flows but thats already a given in a setup like this. if there is any such thing , i'm willing to be a tester . i will deploy it on my server and enviroment ( live one) Adrian TIA Zen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Yet Another Screenshot of a GNOME 2.18 Desktop
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 than on a similar FreeBSD desktop. Linux auto-detects it and does the right thing.). signature.asc Description: OpenPGP digital signature
Re: tproxy on freebsd
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 looks doable without having to keep NAT state like TPROXY does.. Adrian -- Adrian Chadd - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tproxy on freebsd
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 hear that. can't wait to see and test it Thankfully! The solution for FreeBSD looks doable without having to keep NAT state like TPROXY does.. this is GREAT!! Adrian Regards Zen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make buildworld on Freebsd 6.2 amd64 stops on ifconfig.l
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 fdisk.lo fdisk_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/fdisk/fdisk.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/fdisk/geom_mbr_enc.o
crunchide -k _crunched_fdisk_stub fdisk.lo
echo int _crunched_dhclient_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} dhclient_stub.c
cc -O2 -fno-strict-aliasing -pipe -c dhclient_stub.c
ld -dc -r -o dhclient.lo dhclient_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/dhclient.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/clparse.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/alloc.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/dispatch.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/hash.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/bpf.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/options.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/tree.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/conflex.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/errwarn.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/inet.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/packet.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/convert.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/tables.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/parse.o /usr/o
bj/usr/src/rescue/rescue//usr/src/sbin/dhclient/privsep.o
crunchide -k _crunched_dhclient_stub dhclient.lo
echo int _crunched_gzip_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} gzip_stub.c
cc -O2 -fno-strict-aliasing -pipe -c gzip_stub.c
ld -dc -r -o gzip.lo gzip_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/gzip/gzip.o
crunchide -k _crunched_gzip_stub gzip.lo
echo int _crunched_bzip2_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} bzip2_stub.c
cc -O2 -fno-strict-aliasing -pipe -c bzip2_stub.c
ld -dc -r -o bzip2.lo bzip2_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/bzip2/bzip2.o
crunchide -k _crunched_bzip2_stub bzip2.lo
echo int _crunched_tar_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} tar_stub.c
cc -O2 -fno-strict-aliasing -pipe -c tar_stub.c
ld -dc -r -o tar.lo tar_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/bsdtar.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/getdate.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/matching.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/read.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/tree.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/util.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/write.o
crunchide -k _crunched_tar_stub tar.lo
echo int _crunched_vi_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} vi_stub.c
cc -O2 -fno-strict-aliasing -pipe -c vi_stub.c
ld -dc -r -o vi.lo vi_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_bsd.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_funcs.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_main.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_read.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_screen.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_term.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cut.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/delete.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/exf.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/key.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/line.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/log.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/main.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/mark.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/msg.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/options.o /usr/obj/usr/
src/rescue/rescue//usr/src/usr.bin/vi/options_f.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/put.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/screen.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/search.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/seq.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/recover.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/util.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_abbrev.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_append.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_args.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_argv.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_at.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_bang.o
Re: FreeBSD 4 EOL ports tree
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 from the tag on 4.X. My installations use portsnap and so automatically went past the correct tag. Is there a way to get portsnap to downgrade the ports tree now to 4_EOL or is the best way to install cvsup and do it? See the cvsup faq for how to adopt an existing ports tree. Or just delete and check out from scratch if you can't get this to work for you :) Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port accessibility/atk broken in RELEASE_4_EOL tree
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 libtool-1.5.22_2 === Cleaning for icu-3.6 === Cleaning for gettext-0.14.5_2 === Cleaning for ldconfig_compat-1.0_8 === Cleaning for expat-2.0.0_1 === Cleaning for libiconv-1.9.2_2 === Cleaning for rc_subr-1.31_1 === Cleaning for atk-1.9.1 === Vulnerability check disabled, database not found === Extracting for atk-1.9.1 = MD5 Checksum OK for gnome2/atk-1.9.1.tar.bz2. === Patching for atk-1.9.1 === Applying FreeBSD patches for atk-1.9.1 === atk-1.9.1 depends on executable in : pkg-config - found === atk-1.9.1 depends on shared library: glib-2.0.0 - found === Configuring for atk-1.9.1 === Building for atk-1.9.1 make: cannot open Makefile. *** Error code 2 Stop in /usr/p4/ports.akt/accessibility/atk. Since mostly any gnome2 application uses atk I'd like to ask: Is there a chance to get this error fixed 'officialy'? No. That's what EOL means. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
