[ANN] 8-CURRENT, RELENG_7 and RELENG_6 have gotten latest unionfs improvements
Hi unionfs folks It is my pleasure and honor to announce the commitment of latest unionfs improvements for 8-current, RELENG_7 and RELENG_6. Now you can get more stable operation using unionfs on latest 8/7/6. This latest improvements give finstall and FreeSBIE works more well as well as other unionfs works good. If you have interesting in it, would you try it please. However, follow two issues we still have: - It gets a hang-up in a certain case using with NFS. - We cannot see devfs on unionfs. I am going to try those issue fix in near future. Thanks all folks who have helped us! The documents of those unionfs: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) -- Daichi GOTO, http://people.freebsd.org/~daichi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 Available, 6.3-BETA1 coming soon...
- Original Message > From: Ken Smith <[EMAIL PROTECTED]> > To: freebsd-stable@freebsd.org; [EMAIL PROTECTED] > Sent: Tuesday, October 23, 2007 5:21:00 AM > Subject: 7.0-BETA1 Available, 6.3-BETA1 coming soon... > > > We have entered the final phases of the FreeBSD-7.0 Release cycle which > also means the beginning of the FreeBSD-6.3 Release cycle. Because the > people who support the ports for FreeBSD also need to go through a > freeze cycle as part of releases we had decided to combine the two > releases to try and minimize the impact on the ports maintainers. > > The current plan is to interleave the BETAs/RCs of the 7.0 and 6.3 > releases, trying to follow this for the dates when the builds will get > started (with them becoming available on the FTP mirrors a day or two > after the builds start): > > 7.0 6.3 > BETA1 10/17 10/24 > BETA2 10/31 11/7 > RC1 11/14 11/21 > RC2 11/28 12/5 > REL 12/12 12/19 > > Tomorrow (10/23) the RELENG_6 branch will be marked "6.3-PRERELEASE" to > note that we have entered the 6.3 release cycle. > > The schedule dates are, as usual, tentative. At this point RELENG_6 is > pretty mature so that schedule should be fairly accurate. Being a new > branch it is at least somewhat likely the dates for 7.0 will wind up > slipping. > > The 7.0-BETA1 builds have completed and are on many of the FreeBSD > mirror sites. If you want to update an existing machine using > cvsup > use > RELENG_7 as the branch tag. Instructions on using FreeBSD Update to > perform a binary upgrade from FreeBSD 6.x to 7.0-BETA1 will be provided > via the freebsd-stable list when available. > > Ken Smith > - From there to here, from here to | > [EMAIL PROTECTED] > there, funny things are everywhere. | > - Theodore Geisel | Thank you Ken! Could you please have someone to put these interesting news in the main page of FreeBSD? I wish FreeBSD main page is more attractive for new users, with links to PC-BSD, and DesktopBSD ..etc ;) --- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
awk gives trouble
Hello,
Running make for makeworld or in ports gives problems since my upgrade
yesterday.
Running 6.2-STABLE of yesterday on i386.
--
stage 1.1: legacy release compatibility shims
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp INSTALL="sh
/usr/src/tools/install.sh"
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk -j 3
-m /usr/src/share/mk" /usr/obj/usr/src/make.i386/make -f Makefile.inc1
DESTDIR= BOOTSTRAPPING= -DNO_HTML -DNO_INFO -DNO_LINT -DNO_MAN -DNO_NLS
-DNO_PIC -DNO_PROFILE -DNO_SHARED -DNO_CPU_CFLAGS -DNO_WARNS legacy
awk: illegal statement
input record number 1, file /usr/include/osreldate.h
source line number 1
"Makefile.inc1", line 101: warning: "awk
'/^#define[[:space:]]*__FreeBSD_version/ { print $3 }'
/usr/include/osreldate.h" returned non-zero status
Any thoughts how I can solve this?
Ronald.
--
Ronald Klop
Amsterdam, The Netherlands
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [EMAIL PROTECTED]: cvs commit: src/crypto/openssl/ssl d1_both.c ?dtls1.h ssl.h ssl_err.c]
Simon L. Nielsen wrote: > RELENG_7 isn't -STABLE yet Uhm, are you sure? In the past, whenever a new RELENG branch was created, it was implicitly the next -stable branch, because -current moved on to the next version number. Did that policy change? If it did change, I'm curious to know what the version 7 branch is called right now (6 being -stable and 8 being -current)? I assume we do not have two -current branches at the same time, do we? Best regards Oliver PS: I do agree that the DTLS security fix doesn't need a FreeBSD Security Advisory, for the reason that it doesn't seem to affect any _released_ FreeBSD version. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." -- RFC 1925 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [EMAIL PROTECTED]: cvs commit: src/crypto/openssl/ssl d1_both.c ?dtls1.h ssl.h ssl_err.c]
On Tue, 2007-10-23 at 18:22 +0200, Oliver Fromme wrote: > Simon L. Nielsen wrote: > > RELENG_7 isn't -STABLE yet > > Uhm, are you sure? In the past, whenever a new RELENG > branch was created, it was implicitly the next -stable > branch, because -current moved on to the next version > number. Did that policy change? It is implicitly the *next* -stable but it's not there yet. That's what Simon was saying. FreeBSD's development (specifically the CVS repository) is public. But the bottom line is that the RELENG_X branches are *development* branches. If we were a corporation those would be private to the Developers. As such the RELENG_X branches at times have nebulous states, gray zones, etc. We're in one such gray zone now. If I needed to come up with a name for RELENG_7 right now it would be what I set its name to when I first branched it: 7.0-PRERELEASE. It doesn't officially become -stable until there has been a release done from it. I've said this many times before. There are lots of people out there who use RELENG_X. But strictly speaking that's a *development* branch. There can be glitches while using it, mistakes do get made on it, etc. We don't want to act like a private company, we don't want to hide the development work. BUT we *do* need to have RELENG_X as a development tool and people using it need to realize that's exactly what it is. The RELENG_X_Y branches are what is meant for "general public consumption". > If it did change, I'm curious to know what the version > 7 branch is called right now (6 being -stable and 8 > being -current)? I assume we do not have two -current > branches at the same time, do we? No change in any policies or anything like that. What I'm describing has been the status quo for a long time but people tend to forget or never quite "get it" or ... so I'm sure you're not the only one thinking this way. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
ACPI warning msgs during boot - significance?
Hi, This unit is supposedly going to be my new home ws, are the below acpi errors something that I need to worry about? Thanks, --per 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 7.0-BETA1 #0: Tue Oct 23 18:23:25 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WEIR Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d AMD Features=0x2000 real memory = 1073676288 (1023 MB) avail memory = 1037070336 (989 MB) ACPI APIC Table: ACPI Warning (tbfadt-0324): FADT (revision 3) is longer than ACPI 2.0 version, truncating length 0x10C to 0xF4 [20070320] ACPI Error (tbfadt-0516): 32/64X address mismatch in "Gpe0Block": [ F828] [ 0 1F030], using 64X [20070320] ACPI Error (tbutils-0314): Null physical address for ACPI table [(null)] [20070320] ACPI Error (tbutils-0314): Null physical address for ACPI table [(null)] [20070320] ACPI Error (tbutils-0314): Null physical address for ACPI table [(null)] [20070320] ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xf808-0xf80b on acpi0 cpu0: on acpi0 p4tcc0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci32: on pcib1 pcib2: at device 3.0 on pci0 pci1: on pcib2 pci0:1:0:0: bad VPD cksum, remain 14 bge0: mem 0xf820-0xf820 irq 16 at device 0.0 on pci1 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:12:79:de:50:6f bge0: [ITHREAD] pcib3: at device 4.0 on pci0 pci64: on pcib3 vgapci0: port 0x3000-0x30ff mem 0xf000-0xf7ff,0xf810-0xf810 irq 16 at device 0.0 on pci64 vgapci1: mem 0xf811-0xf811 at device 0.1 on pci64 uhci0: port 0x5440-0x545f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x5460-0x547f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x5480-0x549f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x54a0-0x54bf irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xf830-0xf83003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered pcib4: at device 30.0 on pci0 pci2: on pcib4 mpt0: port 0x4000-0x40ff mem 0xf800-0xf801,0xf802-0xf803 irq 18 at device 9.0 on pci2 mpt0: [ITHREAD] mpt0: MPI Version=1.2.12.0 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x54e0-0x54ef irq 18 at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0x5810-0x5817,0x5828-0x582b,0x5818-0x581f,0x582c-0x582f,0x54f0-0x54ff irq 18 at device 31.2 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] pci0: at device 31.5 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] pmtimer0 on isa0 orm0: at iomem 0xc-0xccfff pnpid ORM on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/13 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, fla
Re: awk gives trouble (solved)
On Tue, 23 Oct 2007 13:18:11 +0200, Ronald Klop
<[EMAIL PROTECTED]> wrote:
Hello,
Running make for makeworld or in ports gives problems since my upgrade
yesterday.
Running 6.2-STABLE of yesterday on i386.
--
stage 1.1: legacy release compatibility shims
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp INSTALL="sh
/usr/src/tools/install.sh"
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk -j
3 -m /usr/src/share/mk" /usr/obj/usr/src/make.i386/make -f
Makefile.inc1 DESTDIR= BOOTSTRAPPING= -DNO_HTML -DNO_INFO -DNO_LINT
-DNO_MAN -DNO_NLS -DNO_PIC -DNO_PROFILE -DNO_SHARED -DNO_CPU_CFLAGS
-DNO_WARNS legacy
awk: illegal statement
input record number 1, file /usr/include/osreldate.h
source line number 1
"Makefile.inc1", line 101: warning: "awk
'/^#define[[:space:]]*__FreeBSD_version/ { print $3 }'
/usr/include/osreldate.h" returned non-zero status
Any thoughts how I can solve this?
Ronald.
I think I solved it myself. Cvsup didn't remove the old *.diff files from
/usr/src/usr.bin/awk, so the build was producing a very corrupt file.
Removing the awk source and re-cvsup-ing gave me a better working version.
Ronald.
--
Ronald Klop
Amsterdam, The Netherlands
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-BETA1
How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. BTW, where can I find 7-STABLE release notes? It's not here: http://www.freebsd.org/relnotes.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1
On Tue, 23 Oct 2007 19:57:52 +0200, rihad <[EMAIL PROTECTED]> wrote: How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. BTW, where can I find 7-STABLE release notes? It's not here: http://www.freebsd.org/relnotes.html Here are snapshots of the release notes. http://people.freebsd.org/~bmah/relnotes/ -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1
rihad wrote: How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. We've used 7-CURRENT since January on a couple of production boxes and had very few disasters, well, none, but a couple of issues. "Risky" is a relative term really, but if you ask me I'd say the "risk" is rather low. But: TEST FIRST! --per ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I do 6.1-RELEASE to 6.2 via cvsup
> > Also, the list of things to do is a bit mis-ordered and truncated. The > official list is in /usr/src/UPDATING and reads: > > > make buildworld > make kernel KERNCONF=YOUR_KERNEL_HERE > [1] > [3] > mergemaster -p [5] > make installworld > make delete-old > ^ Where in /usr/src/UPDATING is that command. I can't see it. > > mergemaster [4] > Thanks, Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_7 problem with playing DVDs
Using mplayer to try play a DVD my errorconsole is spammed with: ata1: FAILURE - non aligned DMA transfer attempted acd0: setting up DMA failed The mplayer just hangs around in physrd status and cannot be killed (even by kill -9). The error message gets posted until the system is shutdown. The mplayer process also stays alive for the whole time. The only way to open the DVD-drive after attempting to play the DVD is to reboot the system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I do 6.1-RELEASE to 6.2 via cvsup
> > > > Also, the list of things to do is a bit mis-ordered and truncated. The > > official list is in /usr/src/UPDATING and reads: > > > > > > make buildworld > > make kernel KERNCONF=YOUR_KERNEL_HERE > > [1] > > [3] > > mergemaster -p [5] > > make installworld > > make delete-old > > > ^ Where in /usr/src/UPDATING is that command. I > can't see it. > > > > mergemaster [4] > > > > > Thanks, Tuc > Sorry. It is there on my 6-Stable system, but it looks like it is not in 6.2-Release.It's been in HEAD for over 2 years. I am a bit confused,though. I see my 6.2-Stable has src/UPDATING,v 1.416.2.35, but I can't find that version in CVS. I see only one commit, 1.416, in RELENG_6 and I know that it has had more commits since then. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgps4l0GxzD1V.pgp Description: PGP signature
Re: can I do 6.1-RELEASE to 6.2 via cvsup
> > --==_Exmh_1193178365_55823P > Content-Type: text/plain; charset=us-ascii > > > > > > > Also, the list of things to do is a bit mis-ordered and truncated. The > > > official list is in /usr/src/UPDATING and reads: > > > > > > > > > make buildworld > > > make kernel KERNCONF=YOUR_KERNEL_HERE > > > [1] > > > [3] > > > mergemaster -p [5] > > > make installworld > > > make delete-old > > > > > ^ Where in /usr/src/UPDATING is that command. I > > can't see it. > > > > > > mergemaster [4] > > > > > > > > > Thanks, Tuc > > > > Sorry. It is there on my 6-Stable system, but it looks like it is not in > 6.2-Release.It's been in HEAD for over 2 years. > > I am a bit confused,though. I see my 6.2-Stable has src/UPDATING,v > 1.416.2.35, but I can't find that version in CVS. I see only one commit, > 1.416, in RELENG_6 and I know that it has had more commits since then. > AH, no wonder why I don't see it... I'm on 5.5 still, and only have version 1.342.2.36 from 5/26/2006. Thanks, Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: RELENG_7 problem with playing DVDs
> -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > [EMAIL PROTECTED] On Behalf Of [LoN]Kamikaze > Sent: mercredi 24 octobre 2007 00:06 > To: freebsd-stable@freebsd.org > Subject: RELENG_7 problem with playing DVDs > > Using mplayer to try play a DVD my errorconsole is spammed with: > > ata1: FAILURE - non aligned DMA transfer attempted > acd0: setting up DMA failed > > The mplayer just hangs around in physrd status and cannot be killed > (even by > kill -9). The error message gets posted until the system is shutdown. > The > mplayer process also stays alive for the whole time. The only way to > open the > DVD-drive after attempting to play the DVD is to reboot the system. It seems that you have a hardware problem. Could you please try with an other drive? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [ANN] 8-CURRENT, RELENG_7 and RELENG_6 have gotten latest unionfs improvements
* Daichi GOTO ([EMAIL PROTECTED]) wrote: > It is my pleasure and honor to announce the commitment of > latest unionfs improvements for 8-current, RELENG_7 and > RELENG_6. Now you can get more stable operation using > unionfs on latest 8/7/6. > > This latest improvements give finstall and FreeSBIE works > more well as well as other unionfs works good. If you have > interesting in it, would you try it please. Thanks a lot all your guys for your work! Btw, I was wondering: is unionfs related in any way with -ounion option of mount_*? I was told long time ago that -ounion is even more broken than unionfs. Though, those two features seem to do very similar thing and I think that -ounion option is pretty useful. -- Dmitry A. Marakasov| jabber: [EMAIL PROTECTED] [EMAIL PROTECTED] | http://www.amdmi3.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Likely release dates for 6.3, 7.0?
What are the likely release dates (I'm looking for estimates here) of FreeBSD 6.3 and 7.0? We need 6.3, including all of the MFCed code that's likely to be included in it, for new servers and would like to begin experimenting with 7.0. The current release engineering page hasn't been updated in awhile and doesn't show the usual "to do" lists or schedules Can someone give us an estimated timeframe? --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_7 problem with playing DVDs
Olivier Brisson wrote: >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:owner-freebsd- >> [EMAIL PROTECTED] On Behalf Of [LoN]Kamikaze >> Sent: mercredi 24 octobre 2007 00:06 >> To: freebsd-stable@freebsd.org >> Subject: RELENG_7 problem with playing DVDs >> >> Using mplayer to try play a DVD my errorconsole is spammed with: >> >> ata1: FAILURE - non aligned DMA transfer attempted >> acd0: setting up DMA failed >> >> The mplayer just hangs around in physrd status and cannot be killed >> (even by >> kill -9). The error message gets posted until the system is shutdown. >> The >> mplayer process also stays alive for the whole time. The only way to >> open the >> DVD-drive after attempting to play the DVD is to reboot the system. > > It seems that you have a hardware problem. Could you please try with an other > drive? I actually tried with 2 different drives. I can get more detailed, now. The drive lockup and dmesg spamming till the system has shut down as I reported it only occurs if I try to use the drives through the cam interface /dev/cd0 or /dev/cd1. The error message being the same. Here is the dmesg boot output concerning the drives: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x37...skipping... acd0: DVDROM at ata1-master UDMA33 acd1: DVDR at ata1-slave UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [3799193 x 2048 byte records] cd1 at ata1 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: cd present [3793882 x 2048 byte records] If I use the acd0 device mplayer just fails because of failed CSS-key cracking. The dmesg gets a couple of lines with: ata1: FAILURE - non aligned DMA transfer attempted acd0: setting up DMA failed acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x6f ascq=0x04 If I use the acd1 device there are no dmesg reports and the dvd plays, but very poorly, as if the drive was in PIO mode. I checked my BIOS settings and all the usual suspects like block-reading, DMA and so on are turned on. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_7 problem with playing DVDs
[LoN]Kamikaze wrote: > Olivier Brisson wrote: > I actually tried with 2 different drives. I can get more detailed, now. > > The drive lockup and dmesg spamming till the system has shut down as I > reported it only occurs if I try to use the drives through the cam interface > /dev/cd0 or /dev/cd1. The error message being the same. > > Here is the dmesg boot output concerning the drives: > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x37...skipping... > acd0: DVDROM at ata1-master UDMA33 > acd1: DVDR at ata1-slave UDMA33 > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > cd0 at ata1 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 33.000MB/s transfers > cd0: cd present [3799193 x 2048 byte records] > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 33.000MB/s transfers > cd1: cd present [3793882 x 2048 byte records] > > If I use the acd0 device mplayer just fails because of failed CSS-key > cracking. The dmesg gets a couple of lines with: > ata1: FAILURE - non aligned DMA transfer attempted > acd0: setting up DMA failed > acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x6f ascq=0x04 > > If I use the acd1 device there are no dmesg reports and the dvd plays, but > very poorly, as if the drive was in PIO mode. I checked my BIOS settings and > all the usual suspects like block-reading, DMA and so on are turned on. I now turned of the AUTO detection and hand-configured the devices. Now acd1 also reports the same DMA failure. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
1.3G of my /var missing
df -h reports that on /var 1.5G of 1.9G are used and only 237M of free space remain. However doing a du -hd 1 /var and summing up the results I only get to less than 200M of used space, so there are 1.3G unaccounted for. fsck in single user mode does not recognize a problem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 1.3G of my /var missing
> df -h reports that on /var 1.5G of 1.9G are used and only 237M of free space > remain. > > However doing a > du -hd 1 /var > > and summing up the results I only get to less than 200M of used space, so > there are 1.3G unaccounted for. fsck in single user mode does not recognize a > problem. The usual answer is that a process has a unlinked file open however as you went to single user this would have eliminated this. Are you swapping to a file on /var? Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [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: Likely release dates for 6.3, 7.0?
On Tue, Oct 23, 2007 at 11:00:29PM -0600, Brett Glass wrote: > What are the likely release dates (I'm looking for estimates here) of > FreeBSD 6.3 and 7.0? We need 6.3, including all of the MFCed code that's > likely to be included in it, for new servers and would like to begin > experimenting with 7.0. The current release engineering page hasn't been > updated in awhile and doesn't show the usual "to do" lists or schedules > Can someone give us an estimated timeframe? Ken Smith gave the following dates: 7.0 6.3 BETA1 10/17 10/24 BETA2 10/31 11/7 RC1 11/14 11/21 RC2 11/28 12/5 REL 12/12 12/19 -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 1.3G of my /var missing
Mark Andrews wrote: >> df -h reports that on /var 1.5G of 1.9G are used and only 237M of free space >> remain. >> >> However doing a >> du -hd 1 /var >> >> and summing up the results I only get to less than 200M of used space, so >> there are 1.3G unaccounted for. fsck in single user mode does not recognize a >> problem. > > The usual answer is that a process has a unlinked file open > however as you went to single user this would have eliminated > this. Are you swapping to a file on /var? > > Mark No, I have a separate partition for swapping. I even tried to turn off soft-updates, but to no avail. I'd like to find out what causes this, but If I cannot, I will simply backup /var, run newfs and restore it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 1.3G of my /var missing
On Wed, Oct 24, 2007 at 08:27:10AM +0200, [LoN]Kamikaze wrote: > df -h reports that on /var 1.5G of 1.9G are used and only 237M of free space > remain. > > However doing a > du -hd 1 /var > > and summing up the results I only get to less than 200M of used space, so > there are 1.3G unaccounted for. fsck in single user mode does not recognize a > problem. Try looking at tunefs(8), particularly the -m flag. That amount of space is kept for root (the user). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
