Re: Seeking 6.4 make source for ports
On Wed, 20 Jun 2012 06:57:59 +0200, Michael R. Wayne freebs...@wayne47.com wrote: Google is littered with messages from people who have 6.3 systems and can no longer upgrade ports. It appears that a recent change requires the version of make from 6.4. While it would be ideal if freebsd.org would build a 6.4 make on a 6.3 system and pseudo-officially support it, a reasonable alternative would be a simple way to download just the files required to build the 6.4 version of make on 6.3. Any possibility to get this tossed on a site someplace? Do you have a problem yourself or did you just found some messages on google? I presume you are running 6.3 yourself. Why don't you upgrade the OS to 6.4 or 7+, but you do upgrade the ports on an unsupported OS? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Seeking 6.4 make source for ports
Ronald Klop wrote: Do you have a problem yourself or did you just found some messages on google? I presume you are running 6.3 yourself. Why don't you upgrade the OS to 6.4 or 7+, but you do upgrade the ports on an unsupported OS? It is a little mind boggling. Unless required I wouldn't even recompile my ports when moving a system from 6.3 to 6.4. In fact I've got an internal system here that started life as 5.3 BETA and have been upgraded all the way to 7.4 via 6.4 with pretty much no downtime apart from the installworld part of the source upgrade. All the 5.x compiled ports ran fine on the 7.4 system until I got round to recompiling them. Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Seeking 6.4 make source for ports
20.06.2012 16:17, Mike Pumford пишет: Ronald Klop wrote: Do you have a problem yourself or did you just found some messages on google? I presume you are running 6.3 yourself. Why don't you upgrade the OS to 6.4 or 7+, but you do upgrade the ports on an unsupported OS? It is a little mind boggling. Unless required I wouldn't even recompile my ports when moving a system from 6.3 to 6.4. In fact I've got an internal system here that started life as 5.3 BETA and have been upgraded all the way to 7.4 via 6.4 with pretty much no downtime apart from the installworld part of the source upgrade. All the 5.x compiled ports ran fine on the 7.4 system until I got round to recompiling them. You are not required to recompile ports when upgrading within major release, e.g. from 6.x to 6.4. There is no one reason to do that. They all will work just as usual. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
error compiling
Hi, i just cvsup standard 8.2, that pulled me 8.2-p4 into the source tree. when i made: make buildkernel KERNCONF=SAMI i got this: cc -c -x assembler-with-cpp -DLOCORE -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_wakeup.c /usr/src/sys/amd64/acpica/acpi_wakeup.c: In function 'acpi_wakeup_ap': /usr/src/sys/amd64/acpica/acpi_wakeup.c:107: error: 'wakeup_pcb' undeclared (first use in this function) /usr/src/sys/amd64/acpica/acpi_wakeup.c:107: error: (Each undeclared identifier is reported only once /usr/src/sys/amd64/acpica/acpi_wakeup.c:107: error: for each function it appears in.) /usr/src/sys/amd64/acpica/acpi_wakeup.c: In function 'acpi_sleep_machdep': /usr/src/sys/amd64/acpica/acpi_wakeup.c:258: error: 'wakeup_pcb' undeclared (first use in this function) *** Error code 1 Stop in /usr/obj/usr/src/sys/SAMI. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # I Have the conf file with these options: ### #SAMI ADDITIONS ### device lagg options IPFIREWALL options IPFIREWALL_FORWARD options IPFIREWALL_VERBOSE options DUMMYNET options HZ=1000 options TCP_SIGNATURE device crypto # core crypto support device cryptodev # /dev/crypto for access to h/w options IPSEC options DEVICE_POLLING device if_bridge options VIMAGE #options SCTP options IPDIVERT ### any ideas? -- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
geli decrypt only one partition
hi all, i have two partitions: ada0p3.eli and ada1p3.eli on bootprocess i must type a passphrase for ada0p3 and have ada0p3.eli. next i type the passphrase for ada1p3 and i become: wrong key when the bootprocess is finish and i login and type geli attach -k /path to keyfile /dev/ada1p3 and i type the passphrase then i have ada1p3.eli. why can i decrypt only one partition on bootprocess? ada0p1.eli and ada1p3.eli are two parts on zfs miror. the mirroe cant create when i decrypt ada1p3 by hand. thanks for help suri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
I'm resending this email as I got no response the first time. After over 3 years of uptime, I decided to upgrade one of my SUN boxes to 9-stable. However the new kernel didn't boot because of geom integrity check issues. This I understand as I remember I had to use some weird tricks in the past to get the entire disks used in the first place. Anyway, I felt lucky this was a known and documented problem, with a workaround: http://www.freebsd.org/releases/9.0R/relnotes-detailed.html#AEN1277 However, the workaround doesn't seem to work :-( Type '?' for a list of commands, 'help' for more detailed help. OK set kern.geom.part.check_integrity=0 OK boot jumping to kernel entry at 0xc007. Copyright (c) 1992-2012 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 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012 SNIP Timecounters tick every 1.000 msec ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: MAXTOR STM3160215A 3.AAD ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: MAXTOR STM3160215A 3.AAD ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM: ada0: adding VTOC8 information. GEOM_PART: integrity check failed (ada0, VTOC8) this is where it hangs, just like without setting kern.geom.part.check_integrity. Is this a regression? -- cheers, Ruben de Groot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel modules are broken after updating to the latestFreeBSD9-STABLE
On Tue, Jun 19, 2012 at 9:45 PM, Dewayne Geraghty dewayne.gerag...@heuristicsystems.com.au wrote: Hi Olav, It seems that you're doing the same as I would, in that you start from a fresh base. I'd stay with csup, it is reliable and avoids the modula2 installation. Over the last 5 years, I have experienced the same weirdness on 2 occasions, and out of desperation (no time), I've removed the source, /usr/obj, removed ccache (that's been a few problems), removed -j $((`sysctl -n hw.ncpu`+1)) and changed my source origin. Because I'm in Australia, I use: *default host=cvsup3.au.freebsd.org #*default host=cvsup2.jp.freebsd.org #*default host=cvsup2.freebsd.org # Only when updates are 1hour old There's a page in the Handbook for urls that are close to you. I'd suggest that course. Good luck. Regards, Dewayne. PS If successful, please post to the list, so the cause may be shared/reviewed. I got the right kernel to load after doing a make installkernel in single user mode. However I still have a problem starting my jails. I get the following error message for each jail I start. /lib/libc.so.7: version FBSD_1.3 required by /bin/sh not found I use ezjail, are there some other way to update it than just using ezjail-admin update -i? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
On 20.06.2012 19:14, Ruben de Groot wrote: Timecounters tick every 1.000 msec ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: MAXTOR STM3160215A 3.AAD ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: MAXTOR STM3160215A 3.AAD ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM: ada0: adding VTOC8 information. GEOM_PART: integrity check failed (ada0, VTOC8) this is where it hangs, just like without setting kern.geom.part.check_integrity. Is this a regression? Can you enable verbose boot mode and show what you will get? -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
On 20 jun 2012, at 18:34, Andrey V. Elsukov wrote: On 20.06.2012 19:14, Ruben de Groot wrote: Timecounters tick every 1.000 msec ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: MAXTOR STM3160215A 3.AAD ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: MAXTOR STM3160215A 3.AAD ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM: ada0: adding VTOC8 information. GEOM_PART: integrity check failed (ada0, VTOC8) this is where it hangs, just like without setting kern.geom.part.check_integrity. Is this a regression? Can you enable verbose boot mode and show what you will get? It looks like it gets stuck in some loop and I can only break to lom and reset. Type '?' for a list of commands, 'help' for more detailed help. OK unload OK set kern.geom.part.check_integrity=0 OK boot kernel.9 -v /boot/kernel.9/kernel data=0x5af3d8+0xc2fd8 syms=[0x8+0x77fe8+0x8+0x7119d] /boot/kernel.9/geom_mirror.ko text=0x37a10 data=0x5a0+0x18 syms=[0x8+0x1650+0x8+0x1159] jumping to kernel entry at 0xc007. Copyright (c) 1992-2012 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 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012 r...@morninglightmountain.hacktor.net:/usr/obj/usr/src/sys/MORNINGLIGHTMOUNTAIN sparc64 Preloaded elf kernel /boot/kernel.9/kernel at 0xc089a000. Preloaded elf module /boot/kernel.9/geom_mirror.ko at 0xc089a1a0. real memory = 536870912 (512 MB) avail memory = 503963648 (480 MB) machine: SUNW,UltraAX-i2 cpu0: Sun Microsystems UltraSparc-IIe Processor (400.00 MHz CPU) mask=0x14 maxtl=5 maxwin=7 INTR: Adding CPU 0 as a target ULE: setup cpu 0 nfslock: pseudo-device mem: memory null: null device, zero device openfirm: Open Firmware control device random: entropy source, Software, Yarrow ctl: CAM Target Layer loaded nexus0: Open Firmware Nexus device pcib0: U2P UPA-PCI bridge mem 0x1fe-0x1fe,0x1fe0100-0x1fe01ff irq 2032,2030,2031,2021 on nexus0 pcib0: Sabre, impl 0, version 0, IGN 0x1f, bus A, 66MHz pcib0: DVMA map: 0x6000 to 0x63ff 8192 entries pcib0: PROM IOTSB size: 1 (2048 entries) pcib0: bus range 0 to 0; PCI bus 0 initalizing intr_countp pcib0: [GIANT-LOCKED] pci0: OFW PCI bus on pcib0 pci0: domain=0, physical bus=0 found- vendor=0x108e, dev=0xa001, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x10b9, dev=0x1533, revid=0x00 domain=0, bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x000f, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D3 current D0 found- vendor=0x10b9, dev=0x7101, revid=0x00 domain=0, bus=0, slot=3, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x1282, dev=0x9102, revid=0x31 domain=0, bus=0, slot=12, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0147, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x50 (2400 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (1 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x1, size 8, enabled map[14]: type Memory, range 32, base 0, size 8, enabled found- vendor=0x1282, dev=0x9102, revid=0x31 domain=0, bus=0, slot=5, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0147, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x50 (2400 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (1 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x10100, size 8, enabled map[14]: type Memory, range 32, base 0x2000, size 8, enabled found- vendor=0x10b9, dev=0x5237, revid=0x03 domain=0, bus=0, slot=10, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x50 (2 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0x100, size 12, memory disabled found- vendor=0x10b9, dev=0x5229, revid=0xc3 domain=0, bus=0, slot=13, func=0
Re: geli decrypt only one partition
joerg_surmann joerg_surm...@snafu.de wrote: i have two partitions: ada0p3.eli and ada1p3.eli on bootprocess i must type a passphrase for ada0p3 and have ada0p3.eli. next i type the passphrase for ada1p3 and i become: wrong key when the bootprocess is finish and i login and type geli attach -k /path to keyfile /dev/ada1p3 and i type the passphrase then i have ada1p3.eli. why can i decrypt only one partition on bootprocess? This is frequently the effect of an incorrectly specified keyfile in loader.conf. Do you get a boot message like the following for both keyfiles when booting in verbose mode? Jun 20 19:49:34 r500 kernel: Preloaded ada0s1d:geli_keyfile0 /boot/ad4s1d.key at 0x813951d0. Fabian signature.asc Description: PGP signature
Re: Seeking 6.4 make source for ports
On Wed, Jun 20, 2012 at 10:26:02AM +0200, Ronald Klop wrote: On Wed, 20 Jun 2012 06:57:59 +0200, Michael R. Wayne freebs...@wayne47.com wrote: Google is littered with messages from people who have 6.3 systems and can no longer upgrade ports. It appears that a recent change requires the version of make from 6.4. While it would be ideal if freebsd.org would build a 6.4 make on a 6.3 system and pseudo-officially support it, a reasonable alternative would be a simple way to download just the files required to build the 6.4 version of make on 6.3. Any possibility to get this tossed on a site someplace? Do you have a problem yourself or did you just found some messages on google? Have the problem myself. There are ports with security vulnerabilities and the recent change broke make for ports. I went to Google and found lots of other people with the same problem. The suggested fix is to use the make from 6.4. Hence my request. I presume you are running 6.3 yourself. Why don't you upgrade the OS to 6.4 or 7+, but you do upgrade the ports on an unsupported OS? Upgrading a port can be done without rebooting the machine. Upgrading the O/S is a MUCH more major undertaking and is almost never a clean process. Plus the time investment multiplied by many machines is huge (and dreaded). So, any chance of getting a 6.4 make compiled for 6.3? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Seeking 6.4 make source for ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/12 11:56, Michael R. Wayne wrote: On Wed, Jun 20, 2012 at 10:26:02AM +0200, Ronald Klop wrote: On Wed, 20 Jun 2012 06:57:59 +0200, Michael R. Wayne freebs...@wayne47.com wrote: Google is littered with messages from people who have 6.3 systems and can no longer upgrade ports. It appears that a recent change requires the version of make from 6.4. While it would be ideal if freebsd.org would build a 6.4 make on a 6.3 system and pseudo-officially support it, a reasonable alternative would be a simple way to download just the files required to build the 6.4 version of make on 6.3. Any possibility to get this tossed on a site someplace? Do you have a problem yourself or did you just found some messages on google? Have the problem myself. There are ports with security vulnerabilities and the recent change broke make for ports. I went to Google and found lots of other people with the same problem. The suggested fix is to use the make from 6.4. Hence my request. I presume you are running 6.3 yourself. Why don't you upgrade the OS to 6.4 or 7+, but you do upgrade the ports on an unsupported OS? Upgrading a port can be done without rebooting the machine. Upgrading the O/S is a MUCH more major undertaking and is almost never a clean process. Plus the time investment multiplied by many machines is huge (and dreaded). Well, not upgrading the OS means you could leave serious security issues unpatched, which may be Ok for certain trusted environment (e.g. where absolutely no untrusted local user will ever present) but not a wise idea for production system facing the Internet. The good, old time, when everyone wants to be a good neighbor with you, has gone forever. So, any chance of getting a 6.4 make compiled for 6.3? Of course, it would compile (you can grab the source from CVS, CVSup, or SVN and compile it with: cd src/usr.bin/make make cleandir make cleandir # yes, do it twice, this is not a typo make obj make depend make sudo make install # or run this command as root without sudo ) Please note that FreeBSD 6.x was EoL'ed 2 years ago and we (secteam@) no longer support it anymore, which means you don't get security advisories, etc. for the base system. You are advised to upgrade to a more recent and supported FreeBSD release as listed at: http://security.freebsd.org/#sup Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJP4iSBAAoJEG80Jeu8UPuzAM0IAJOMi7zT930RSGUIETOZZQnY 63RKEmwydRV4Tx3urgrEDJM9/ebBECU5aQpejy+ztV1Fpgm8x9TrR4sIt2fGjPj+ JKdkrKUZX2Vc/wrnc7qtnTJOfWjOm2W0JH9NuKQrjFFZQSkptIr7Tj0iOOTG0Cb3 Z/pvVSTeVSDfTbS2kZprIbNHZnERUyJfQgN/o6NjduNOXnb9Nhgtd6PE/SpNrdfe ZIJt4+FkAmDf4QtnUMnqOKCSQg/FUbvBnjHfv645Jpud/cPvQeEZvQMVB2qG76Ex f2dyyb2wSZtbRL4Oe2YkTzB+dKlHbxvJfbl1fagN3KYVszzW6jMmFXbJsQQjyaU= =rukn -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
