Re: NFSD hang
On Tue, Sep 27, 2011 at 08:06:50PM -0400, Rick Macklem wrote: > > I suspect something is making those threads loop, but I don't know how > to figure out where? (In the bad old days, I would have exscaped to a > debugger and looked where the program counter was, then repeated after > a "cont" a few times, to see where they were executing. However, I > have no idea how to do that on a multicore system, even if you still > had the system sitting there? If someone does know how to do this, > please feel free to chime in;-) Absolutely the same. Break into the debugger, use ps to find the pid/tid of the looping threads, then do "bt id" to get a backtrace for them. Repeat several time to get some idea where the loop is located. pgpCeDaV6lEDG.pgp Description: PGP signature
Re: FreeBSD 9-Beta3 on X300 2 problems
2011/9/27 crsnet.pl : >> Hi, > > Hello, thanks for reply. >> >> Please try to do this without wlan loaded at all (not just down, but >> build your wifi support as a module.) >> Then try without X, see whether it's related to that or not. >> > First i make kldunload if_iwn. > When i try to suspend from X, Xorg close, i see console and laptop suspend. > When i resume it, i get console (any key dosent work), when i try to ALT+F9 > i get black screen and beep;/ > > But when i try to suspen from console. I get : > pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP0: AE_BAD_PARAMETER > pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP1: AE_BAD_PARAMETER > pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP2: AE_BAD_PARAMETER > And laptop suspend, when i resume it. He hangs when i press any buttons it > does nothing. And than i see on console that info : > ugen0.2: ... disconnected > ugen4.2: ... disconnected > ubt0: at uhub0 ... disconnected > then i see this presed lethers > and > acpi0: suspend request ignored (not ready yet) and laptops langs and beep ;/ > >> (And you haven't told us what your hardware is.) > > #dmesg (+WITNESS) > Copyright (c) 1992-2011 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-BETA3 #3: Tue Sep 27 10:47:57 CEST 2011 > cr4sh@x300:/sys/amd64/compile/GENERIC amd64 > WARNING: WITNESS option enabled, expect reduced performance. > CPU: Intel(R) Core(TM)2 Duo CPU L7100 @ 1.20GHz (1197.03-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x6fb Family = 6 Model = f Stepping = 11 > Features=0xbfebfbff > BE> > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > TSC: P-state invariant, performance statistics > real memory = 2147483648 (2048 MB) > avail memory = 2019139584 (1925 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 > (20110527/tbfadt-556) > ACPI Warning: Optional field Gpe1Block has zero address or length: > 0x102C/0x0 (20110527/tbfadt-586) > ioapic0: Changing APIC ID to 1 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > CPU0: local APIC error 0x40 > acpi_ec0: port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a (3) failed > acpi0: reservation of 10, 7ef0 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > vgapci0: port 0x1800-0x1807 mem > 0xfa00-0xfa0f,0xe000-0xefff irq 16 at device 2.0 on pci0 > agp0: on vgapci0 > agp0: aperture size is 256M, detected 7676k stolen memory > vgapci1: mem 0xfa10-0xfa1f at device 2.1 on > pci0 > pci0: at device 3.0 (no driver attached) > atapci0: port > 0x1828-0x182f,0x180c-0x180f,0x1820-0x1827,0x1808-0x180b,0x1810-0x181f irq 18 > at device 3.2 on pci0 > ata2: on atapci0 > ata3: on atapci0 > pci0: at device 3.3 (no driver attached) > em0: port 0x1840-0x185f mem > 0xfa20-0xfa21,0xfa225000-0xfa225fff irq 20 at device 25.0 o > > n pci0 > em0: Using an MSI interrupt > acquiring duplicate lock of same type: "network driver" > 1st &dev_spec->swflag_mutex @ dev/e1000/e1000_ich8lan.c:785 > 2nd &dev_spec->nvm_mutex @ dev/e1000/e1000_ich8lan.c:751 I think that MTX_NETWORK_LOCK is not suitable for this case as you will have 2 different locks with the same name in softc. I think that this patch should be good to go (and fixes the WITNESS warning): http://www.freebsd.org/~attilio/e1000_mutex_init.patch Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein ___ 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: support for Oxford Semiconductor OXPCIe952 UARTs
22.09.2011 09:10, Konstantin V. Krotov пишет:
21.09.2011 23:48, Andriy Gapon пишет:
on 21/09/2011 15:04 Konstantin V. Krotov said the following:
hello.
i'm have on fbsd RELENG_8 pci-e card with 1 rs-232 port.
and this card don't support.
(after patch)
pciconf -lv
puc0@pci0:5:0:0: class=0x070002 card=0xc1381415 chip=0xc1381415 rev=0x00
hdr=0x00
vendor = 'Oxford Semiconductor Ltd - now part of PLX Technology'
class = simple comms
subclass = UART
i wrote fast-hack patch:
Does the device work correctly with this patch?
yes, work.
If yes, could you please submit the patch in a PR and also send a
message about
the PR to either current@ or stable@ mailing list depending on what
version of
FreeBSD you used?
Thank you!
--- pucdata.c 2011-08-22 22:46:02.0 +0400
+++ pucdata.c_ 2011-09-06 13:27:23.0 +0400
@@ -739,6 +739,13 @@
PUC_PORT_NONSTANDARD, 0x10, 0, -1,
.config_function = puc_config_oxford_pcie
},
+
+ { 0x1415, 0xc138, 0x, 0,
+ "Oxford Semiconductor OXPCIe952 UARTs",
+ DEFAULT_RCLK * 0x22,
+ PUC_PORT_NONSTANDARD, 0x10, 0, -1,
+ .config_function = puc_config_oxford_pcie
+ },
{ 0x1415, 0xc15d, 0x, 0,
"Oxford Semiconductor OXPCIe952 UARTs (function 1)",
PR 160895
--
WBR, Konstantin V. Krotov
CJSs "Information Systems"
mailto: k...@insysnet.ru
phone: +7 (8332) 51-35-95
___
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: luit -encoding gbk causes Segmentation fault (core dumped) in 9-stable
Hm, it's not all that useful. But it first calls dlopen(). Does it have shared modules? Do you have old copies of those somewhere lying around? Adrian ___ 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: luit -encoding gbk causes Segmentation fault (core dumped) in 9-stable
On Wed, Sep 28, 2011 at 09:09:30PM +0800, Adrian Chadd wrote: > Hm, it's not all that useful. But it first calls dlopen(). Does it > have shared modules? Do you have old copies of those somewhere lying > around? You need to build everything, i.e. base and the port, build with debug symbols. Otherwise, the backtrace give no useful information. pgpeghVB2ZyTk.pgp Description: PGP signature
linux-f10-flashplugin
Hi list, I upgraded today kernel and world from fresh sources on my 8-stable amd64 system. I upgraded ports as well. After that both firefox and chromium do not see linux-f10-flashplugin. I reinstalled manually emulators/linux_base-f10, www/nspluginwrapper and www/linux-f10-flashplugin10 and did other actions as described in the chapter 6.2.3 of the FreeBSD Handbook. The following conditions are met: linprocfs is mounted on /usr/compat/linux/proc, there is a softlink from /usr/local/lib/browser_plugins/ pointing to /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so, ~/.mozilla/plugins/npwrapper.libflashplayer.so is created by the nspluginwrapper -v -a -i command. All browsers still treat the flash plugin as missing. What may be wrong? Thanks, Serguey. ___ 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: linux-f10-flashplugin
On 28.09.2011 16:25, S.N.Grigoriev wrote: > Hi list, > > I upgraded today kernel and world from fresh sources on my 8-stable amd64 > system. > I upgraded ports as well. After that both firefox and chromium do not see > linux-f10-flashplugin. > I reinstalled manually emulators/linux_base-f10, www/nspluginwrapper and > www/linux-f10-flashplugin10 and did other actions as described in the chapter > 6.2.3 of the > FreeBSD Handbook. The following conditions are met: > linprocfs is mounted on /usr/compat/linux/proc, > there is a softlink from /usr/local/lib/browser_plugins/ pointing to > /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so, > ~/.mozilla/plugins/npwrapper.libflashplayer.so is created by the > nspluginwrapper -v -a -i > command. > > All browsers still treat the flash plugin as missing. > What may be wrong? > Hello, Please see http://lists.freebsd.org/pipermail/freebsd-gecko/2011-September/001840.html Best regards, Thomas ___ 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: linux-f10-flashplugin
On Wed, Sep 28, 2011 at 10:25 AM, S.N.Grigoriev wrote: > All browsers still treat the flash plugin as missing. > What may be wrong? try nspluginwrapper -v -a -u -- Eitan Adler ___ 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: linux-f10-flashplugin
On Wed, 28 Sep 2011 18:25:17 +0400 "S.N.Grigoriev" wrote: > Hi list, > > I upgraded today kernel and world from fresh sources on my 8-stable > amd64 system. I upgraded ports as well. After that both firefox and > chromium do not see linux-f10-flashplugin. I reinstalled manually > emulators/linux_base-f10, www/nspluginwrapper and > www/linux-f10-flashplugin10 and did other actions as described in the > chapter 6.2.3 of the FreeBSD Handbook. The following conditions are > met: linprocfs is mounted on /usr/compat/linux/proc, there is a > softlink from /usr/local/lib/browser_plugins/ pointing > to /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so, > ~/.mozilla/plugins/npwrapper.libflashplayer.so is created by the > nspluginwrapper -v -a -i command. > > All browsers still treat the flash plugin as missing. > What may be wrong? Hmmm. What's the output of: /usr/local/lib/nspluginwrapper/x86_64/freebsd/npconfig -l ^^ substitute appropriate architecture as needed Have you tried manually reinstalling the plugin with (ignore the linewrap below): /usr/local/lib/nspluginwrapper/x86_64/freebsd/npconfig -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so (again, substitute appropriate architecture in the path to npconfig as needed) -- Conrad J. Sabatier conr...@cox.net ___ 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: linux-f10-flashplugin
28.09.2011, 19:42, "Conrad J. Sabatier" : > On Wed, 28 Sep 2011 18:25:17 +0400 > "S.N.Grigoriev" wrote: > >> Hi list, >> >> I upgraded today kernel and world from fresh sources on my 8-stable >> amd64 system. I upgraded ports as well. After that both firefox and >> chromium do not see linux-f10-flashplugin. I reinstalled manually >> emulators/linux_base-f10, www/nspluginwrapper and >> www/linux-f10-flashplugin10 and did other actions as described in the >> chapter 6.2.3 of the FreeBSD Handbook. The following conditions are >> met: linprocfs is mounted on /usr/compat/linux/proc, there is a >> softlink from /usr/local/lib/browser_plugins/ pointing >> to /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so, >> ~/.mozilla/plugins/npwrapper.libflashplayer.so is created by the >> nspluginwrapper -v -a -i command. >> >> All browsers still treat the flash plugin as missing. >> What may be wrong? > > Hmmm. What's the output of: > > /usr/local/lib/nspluginwrapper/x86_64/freebsd/npconfig -l > ^^ > substitute appropriate architecture > as needed > > Have you tried manually reinstalling the plugin with (ignore the > linewrap below): > > /usr/local/lib/nspluginwrapper/x86_64/freebsd/npconfig > -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so > > (again, substitute appropriate architecture in the path to npconfig as > needed) > > -- > Conrad J. Sabatier > conr...@cox.net Hi Conrad, after manual reinstalling as described above 'npconfig -l' output is: /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so Original plugin: /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so Plugin viewer: /usr/local/lib/nspluginwrapper/i386/linux/npviewer Wrapper version string: 1.4.4-1 Still no results. Regards, Serguey. ___ 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: linux-f10-flashplugin
28.09.2011, 18:59, "Thomas Steen Rasmussen" : > On 28.09.2011 16:25, S.N.Grigoriev wrote: > >> Hi list, >> >> I upgraded today kernel and world from fresh sources on my 8-stable amd64 >> system. >> I upgraded ports as well. After that both firefox and chromium do not see >> linux-f10-flashplugin. >> I reinstalled manually emulators/linux_base-f10, www/nspluginwrapper and >> www/linux-f10-flashplugin10 and did other actions as described in the >> chapter 6.2.3 of the >> FreeBSD Handbook. The following conditions are met: >> linprocfs is mounted on /usr/compat/linux/proc, >> there is a softlink from /usr/local/lib/browser_plugins/ pointing to >> /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so, >> ~/.mozilla/plugins/npwrapper.libflashplayer.so is created by the >> nspluginwrapper -v -a -i >> command. >> >> All browsers still treat the flash plugin as missing. >> What may be wrong? > > Hello, > > Please see > http://lists.freebsd.org/pipermail/freebsd-gecko/2011-September/001840.html > > Best regards, > > Thomas Thomas, thanks for your response. I saw the link above. What exactly should I change? -- Regards, S.Grigoriev. ___ 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: linux-f10-flashplugin
On Wed, 28 Sep 2011 19:59:43 +0400 "S.N.Grigoriev" wrote: > > Hi Conrad, > > after manual reinstalling as described above 'npconfig -l' output is: > > /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so > Original > plugin: /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so > Plugin viewer: /usr/local/lib/nspluginwrapper/i386/linux/npviewer > Wrapper version string: 1.4.4-1 > > Still no results. > > Regards, > Serguey. OK, your output differs from mine in only one respect. Mine shows the following: /home/conrads/.mozilla/plugins/npwrapper.libflashplayer.so Original plugin: /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so Plugin viewer: /usr/local/lib/nspluginwrapper/i386/linux/npviewer Wrapper version string: 1.4.4-1 It was a while ago that I did the actual wrapper install, but if I remember right, I simply copied npwrapper.libflashplayer.so from /usr/local/lib/browser_plugins to /home/conrads/.mozilla/plugins. You may want to try doing that and see if firefox/chromium will then recognize it. In theory, the system-wide install under /usr/local/lib/browser_plugins *should* work, but I seem to recall having problems with it, which was why I tried putting it under ~/.mozilla/plugins. Maybe it has something to do with the fact that it's not a native plugin(?). I don't know, really. But this has worked fine for me ever since, even across upgrades. Hope this helps. Let us know how it turns out. -- Conrad J. Sabatier conr...@cox.net ___ 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: linux-f10-flashplugin
On Wed, 28 Sep 2011 11:50:08 -0500 "Conrad J. Sabatier" wrote: > > It was a while ago that I did the actual wrapper install, but if I > remember right, I simply copied npwrapper.libflashplayer.so > from /usr/local/lib/browser_plugins to /home/conrads/.mozilla/plugins. > You may want to try doing that and see if firefox/chromium will then > recognize it. > > In theory, the system-wide install > under /usr/local/lib/browser_plugins *should* work, but I seem to > recall having problems with it, which was why I tried putting it > under ~/.mozilla/plugins. Maybe it has something to do with the fact > that it's not a native plugin(?). I don't know, really. But this > has worked fine for me ever since, even across upgrades. > > Hope this helps. Let us know how it turns out. Actually, now that I think of it, I think the way I did it was this: cd /home/conrads/.mozilla/plugins /usr/local/lib/nspluginwrapper/x86_64/freebsd/npconfig -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so And npwrapper.libflashplayer.so was created under /home/conrads/.mozilla/plugins. Hope this helps. -- Conrad J. Sabatier conr...@cox.net ___ 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: linux-f10-flashplugin
At Wed, 28 Sep 2011 16:59:39 +0200, Thomas Steen Rasmussen wrote: > Please see > http://lists.freebsd.org/pipermail/freebsd-gecko/2011-September/001840.html That post is not the case for the OP: - peculiar to firefox-7 implementation. He runs chromium. - wrapped linux-f10-flashplugin in $HOME/.mozilla/plugins works flawlessly in firefox-7. -- kuro ___ 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: linux-f10-flashplugin
28.09.2011, 21:10, "Conrad J. Sabatier" : > On Wed, 28 Sep 2011 11:50:08 -0500 > "Conrad J. Sabatier" wrote: > >> It was a while ago that I did the actual wrapper install, but if I >> remember right, I simply copied npwrapper.libflashplayer.so >> from /usr/local/lib/browser_plugins to /home/conrads/.mozilla/plugins. >> You may want to try doing that and see if firefox/chromium will then >> recognize it. >> >> In theory, the system-wide install >> under /usr/local/lib/browser_plugins *should* work, but I seem to >> recall having problems with it, which was why I tried putting it >> under ~/.mozilla/plugins. Maybe it has something to do with the fact >> that it's not a native plugin(?). I don't know, really. But this >> has worked fine for me ever since, even across upgrades. >> >> Hope this helps. Let us know how it turns out. > > Actually, now that I think of it, I think the way I did it was this: > > cd /home/conrads/.mozilla/plugins > > /usr/local/lib/nspluginwrapper/x86_64/freebsd/npconfig > -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so > > And npwrapper.libflashplayer.so was created > under /home/conrads/.mozilla/plugins. > > Hope this helps. I've done it. No results. -- Regards, Serguey. ___ 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"
9.0-BETA3 and ports db
Hi everyone, Today I upgraded one of my servers from 8.2-STABLE to 9.0-BETA3. I noticed that after the upgrade portsnap does not fetch Index-9 and I had to manually issue the "make fetchindex" command. I remember that this was something I had to do when I was running 9-CURRENT a few months ago in my desktop PC but I thought that it would be solved by now. Am I doing something wrong or is this an expected behavior ? Thanks -- George Kontostanos aisecure.net ___ 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: 9.0-BETA3 and ports db
On Wed, 28 Sep 2011 23:36:13 +0200, George Kontostanos wrote: Hi everyone, Today I upgraded one of my servers from 8.2-STABLE to 9.0-BETA3. I noticed that after the upgrade portsnap does not fetch Index-9 and I had to manually issue the "make fetchindex" command. I remember that this was something I had to do when I was running 9-CURRENT a few months ago in my desktop PC but I thought that it would be solved by now. Am I doing something wrong or is this an expected behavior ? Thanks It is known. But I don't know when it will be fixed. http://www.freebsd.org/cgi/query-pr.cgi?pr=149232 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: 9.0-BETA3 and ports db
On Thu, Sep 29, 2011 at 1:08 AM, Ronald Klop wrote: > On Wed, 28 Sep 2011 23:36:13 +0200, George Kontostanos > wrote: > >> Hi everyone, >> >> Today I upgraded one of my servers from 8.2-STABLE to 9.0-BETA3. I >> noticed that after the upgrade portsnap does not fetch Index-9 and I >> had to manually issue the "make fetchindex" command. I remember that >> this was something I had to do when I was running 9-CURRENT a few >> months ago in my desktop PC but I thought that it would be solved by >> now. >> Am I doing something wrong or is this an expected behavior ? >> >> Thanks >> > > It is known. But I don't know when it will be fixed. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=149232 > > Ronald. > Ok thanks ! -- George Kontostanos aisecure.net ___ 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 9.0-BETA3 Available...
The third BETA build of the 9.0-RELEASE release cycle is now available. Since this is the first release of a brand new branch I cross-post the announcements on both -current and -stable. But just so you know most of the developers active in head pay more attention to the -current mailing list. If you notice problems you can report them through the normal Gnats PR system or on the -current mailing list. The 9.0-RELEASE cycle will be tracked here: http://wiki.freebsd.org/Releng/9.0TODO though the schedule listed there is still way off. We'll re-work the schedule some time soon. NOTE: The location of the FTP install tree and ISOs is the same as it had been for BETA2, though we are still deciding if this will be the layout we switch to for the release. ISO images for the following architectures are available, with pathnames given relative to the top-level of the FTP site: amd64: .../releases/amd64/amd64/ISO-IMAGES/9.0/ i386: .../releases/i386/i386/ISO-IMAGES/9.0/ ia64: .../releases/ia64/ia64/ISO-IMAGES/9.0/ powerpc: .../releases/powerpc/powerpc/ISO-IMAGES/9.0/ powerpc64: .../releases/powerpc/powerpc64/ISO-IMAGES/9.0/ sparc64: .../releases/sparc64/sparc64/ISO-IMAGES/9.0/ MD5/SHA256 checksums are tacked on below. If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now "RELENG_8", if you use "." (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is "svn://svn.freebsd.org/base/stable/9/". We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so "mergemaster -F" is your friend if you are using csup/cvsup. At this point FreeBSD-Update is still not available, in part to help encourage testing the installer. We hope to start the Release Candidate phase of the release cycle with the next test build. Checksums: MD5 (FreeBSD-9.0-BETA3-amd64-bootonly.iso) = 2ce7b93d28fd7ff37965893f1af3f7fc MD5 (FreeBSD-9.0-BETA3-amd64-dvd1.iso) = 4affc701f2052edc548274f090e49235 MD5 (FreeBSD-9.0-BETA3-amd64-memstick.img) = e260f2f2122326cb9a93ac83eb006c1c MD5 (FreeBSD-9.0-BETA3-i386-bootonly.iso) = ef43977dbf1c8c0f40710985660ed55e MD5 (FreeBSD-9.0-BETA3-i386-dvd1.iso) = 95bc3b0c312b83a79752dce616075cdb MD5 (FreeBSD-9.0-BETA3-i386-memstick.img) = d86475510e34698e8077edac717ae73c MD5 (FreeBSD-9.0-BETA3-ia64-bootonly.iso) = 463ee0447dd96ab7fc6e61a6b4623128 MD5 (FreeBSD-9.0-BETA3-ia64-memstick) = 0d6ed910294fbf0afc1c34e9a55227b8 MD5 (FreeBSD-9.0-BETA3-ia64-release.iso) = 716ace96755ddc2965c76590253fb756 MD5 (FreeBSD-9.0-BETA3-powerpc-bootonly.iso) = 6110fe69b92e40e4eab03167795459d0 MD5 (FreeBSD-9.0-BETA3-powerpc-memstick) = 9a365252f3c347c0b465096aed383679 MD5 (FreeBSD-9.0-BETA3-powerpc-release.iso) = 8c18ca00a9a8013a615c86c2a5df46be MD5 (FreeBSD-9.0-BETA3-powerpc64-bootonly.iso) = 2d9e2458116de2b89085fe416e3ce2d5 MD5 (FreeBSD-9.0-BETA3-powerpc64-memstick) = 0b547b0375bfb2a53efc2185b61bfc63 MD5 (FreeBSD-9.0-BETA3-powerpc64-release.iso) = cbc4ad7477bae80f0055e116038d06c2 MD5 (FreeBSD-9.0-BETA3-sparc64-bootonly.iso) = cc1d53cbae4a00672bc0cce3e11ba956 MD5 (FreeBSD-9.0-BETA3-sparc64-dvd1.iso) = 988b07e44a4cfeb39e0aca0a1239c2d2 SHA256 (FreeBSD-9.0-BETA3-amd64-bootonly.iso) = bd12e94d69c189efa15f4ccc5c98d552d54ed204d6d811e9ac8a965dc8780c42 SHA256 (FreeBSD-9.0-BETA3-amd64-dvd1.iso) = fd026f1d0bdddaff533a58b8c731ecbc2b2b14d9d975e8771bebe07eba7a579c SHA256 (FreeBSD-9.0-BETA3-amd64-memstick.img) = 963326cc20ce81cfde062651d757fca1da2ae313fcb2aafcd92054970fdff3a6 SHA256 (FreeBSD-9.0-BETA3-i386-bootonly.iso) = 8a083b9859ca09eca944afc9b20e93b167861b5d876a6ff2c791ad7ffe18f2ac SHA256 (FreeBSD-9.0-BETA3-i386-dvd1.iso) = 811e66efc14ba1a6184b787b09eb497df3c72f38688f73e6b44ffce9e8b81b42 SHA256 (FreeBSD-9.0-BETA3-i386-memstick.img) = 8aca989b1c2837a21240a6c58124f19576cb322c183242e222999f59d99e6293 SHA256 (FreeBSD-9.0-BETA3-ia64-bootonly.iso) = 96c91419fd9a80ff5c3322ef3ee99a4608bda3b39a630dca07869a2aa9c82f13 SHA256 (FreeBSD-9.0-BETA3-ia64-memstick) = 3d253650fdd0bcbecd4f0fb45844f65f4e5a89120b66d16c2d3828370488d5fa SHA256 (FreeBSD-9.0-BETA3-ia64-release.iso) = ab8d322bedc28329298b520b1550940dc5ae75a04636f326baf0f9f5d7e933e2 SHA256 (FreeBSD-9.0-BETA3-powerpc-bootonly.iso) = 0fa3930add2b054ccc828ef9fbbec90efcd9781ad3c82a5ad8bae2d533f27cc5 SHA256 (FreeBSD-9.0-BETA3-powerpc-memstick) = d2c6e43d47021716ac3d0956acc5b9ecf0cf26bc452c1cdf7033d32dc2a66289 SHA256 (FreeBSD-9.0-BETA3-powerpc-release.iso) = 9791766756ecaaa536c2f4e12f86fa99d8fc248d1457f36adafaf2a8865c95b2 SHA256 (FreeBSD-9.0-BETA3-powerpc64-bootonly.iso) = 2d05648ed1be716fd6422ce81f5118424cd6fad7829144e58d64f88315c674e6 SHA256 (FreeBSD-9.0-BETA3-powerpc64-memstick) = f12447fba16b17a93483a22c8dc270c3790707e01ad7b8b0bae9f9bcfeac SHA256 (FreeBSD-9.0-BETA3-powerpc64-release.iso) = 5ccb8b500b1c233077baf38867f595ef753108886e092ba1efd88dfb24ebdbfc SHA256 (F
Re: FreeBSD 9.0-BETA3 Available...
On Wed, 2011-09-28 at 21:42 -0400, Ken Smith wrote: > If you would like to use csup/cvsup mechanisms to access the source > tree the branch tag to use is now "RELENG_8", if you use "." (head) > you will get 10-CURRENT. Sigh. Sorry. It's late... RELENG_9... -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
