Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Daniel O'Connor <[EMAIL PROTECTED]>: On Friday 01 June 2007 23:39, Robin Gruyters wrote: > What happens if you try > tar -b 128 -tf /dev/sa0 Same problem. > What did you upgrade from? Some gnutar using system I guess? (5.x > or 4.x?) I'd upgraded from FreeBSD 6.1-RELEASE-p10 OK. Can you read the archive as a normal file from the tape? eg dd if=/dev/sa0 of=/tmp/foo If so does it work? Are you getting errors reading from the drive, or just the tar file is broken? Nope, it doesn't work. # dd if=/dev/sa0 of=/data3/tmp/bla dd: /dev/sa0: Input/output error 0+0 records in 0+0 records out 0 bytes transferred in 0.005972 secs (0 bytes/sec) # When setting the correct blocksize, it does work: # dd if=/dev/sa0 of=/data3/tmp/bla bs=65536 count=32 32+0 records in 32+0 records out 2097152 bytes transferred in 9.698233 secs (216241 bytes/sec) # This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. Maybe tar doesn't use the -b option when listing the content? (-t) Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpFRkTZCvB8k.pgp Description: PGP Digital Signature
Re: Sysinstall replacement
Craig Boston wrote: I also don't think that ext2 should be offered in the installer, as there have been periodic stability problems with it, and new users accustomed to Linux may pick it out of habit and get bitten. I advocate the opposite view: if it doesn't get exposition, it won't be fixed. P.S. I pretty much never use sysinstall anymore, preferring to set up things as gjournal and geli using Fixit mode, then just extract the tarballs into the new filesystems. Having a good standalone partitioning tool would be nice though, as doing all the math by hand can be tedious. Any chance that the module that handles that could be set up so it's possible to use it independently? I'll write the backend, if anyone wants to do the frontend, he's welcome to it. signature.asc Description: OpenPGP digital signature
Re: Sysinstall replacement
Craig Boston wrote: > Ivan Voras wrote: > > See http://wiki.freebsd.org/finstall . > > Somewhat tangental, the only thing that really jumps out at me is this: > > > I propose the UFS+gjournal be the default FS type (even for > > root+boot?) > > I think this is not such a good idea. While I like gjournal, and use it > quite a bit, I don't think it's suitable as a default. > > For one thing, with default settings, it carves out a full GB of usable > space from each filesystem that it's used on. This would prove highly > surprising to new users, especially on smaller filesystems such as /var, > and may well cause them to think FreeBSD uses a highly inefficient > filesystem. > > Also, gjournal journals *everything*, not just metadata. When the data > and journal are on the same physical device, as they would be in most > setups that take the defaults, all write operations are effectively done > twice (modulo any write-combining). Again, this probably wouldn't be > expected for a default and would lead to perceived slowness. > > Both of these are quite acceptable tradeoffs for what gjournal does, but > the user should be aware of them before choosing to employ it. I think > it would be wonderful to have in the installer, just not as the default. I agree completely. Having it as a non-default option would be best. > I also don't think that ext2 should be offered in the installer, as > there have been periodic stability problems with it, and new users > accustomed to Linux may pick it out of habit and get bitten. Actually I think having it as an option would be good, but I agree that it could cause problems so a warning should be printed, indicating that UFS (or UFS2) is the native BSD file system, and that ext2fs only exists for Linux compatibility and might cause problems. > P.S. I pretty much never use sysinstall anymore, preferring to set up > things as gjournal and geli using Fixit mode, then just extract the > tarballs into the new filesystems. I use sysinstall to install FreeBSD on "virgin" machines or when there's a major jump (like from 4.x to 6.x). Of course, in all other cases I use source-level updates via "make world". > Having a good standalone partitioning tool would be nice though, > as doing all the math by hand can be tedious. Not sure if you already know this ... In the bsdlabel tool you can use "m" and "g" suffixes for sizes to specify megabytes and gigabytes, respectively, so you don't have to calculate block numbers. The size of the last partition can be given as "*" so it will receive all the remaining free space of the device. Furthermore you can use the "*" wildcard for the offsets, so the bsdlabel tool will calculate the offsets by adding the sizes of the preceding partitions. So, in fact, you don't have to do any math at all. If you want a curses GUI, you can run sysinstall with the apropriate functions (»sysinstall diskLabelEditor«). Personally I prefer bsdlabel(8), though, which throws me into my favourite editor (neither v* nor e*) and lets me edit the label directly. That's _much_ faster than navigating through sysinstall. YMMV, of course. Best regards Oliver -- 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 "The ITU has offered the IETF formal alignment with its corresponding technology, Penguins, but that won't fly." -- RFC 2549 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vnode_pager_putpages errors on 6.2
On Thu, May 31, 2007 at 06:15:14PM +0200, Christoph Schug wrote: > On Tue, May 29, 2007, steve wrote: > > > Howdy! > > > > I had this issue on 4.x, which is basically, I have > > machines that do cgi stuff for customers, and there is a local > > md device that is used as a tmp. When it fills the machine > > logs errors > > > > vnode_pager_putpages I/O error 28.. > [...] > > Just for the record: there's still an open discussion on the same issue > in PR kern/67919 [1]. Is this issue resolved completely with this patch? Not sure yet. I'm running some machines with the patch and some without, hoping that the unpatched machines will fail and the patched ones won't. Havn't been able to reproduce the problem to conclude. But I'll let you know ... -steve > > [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/67919 > > Thanks > -cs > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
On 02/06/07, Fabian Keil <[EMAIL PROTECTED]> wrote: Chris <[EMAIL PROTECTED]> wrote: > On 29/05/07, Mark Linimon <[EMAIL PROTECTED]> wrote: > > On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote: > > > Agreed. 6.3-RELEASE would nominally be due around July but the lack > > > of any schedule on http://www.freebsd.org/releng/ suggests that it will > > > be later than that. The plans to start the 7.0-RELEASE cycle will also > > > impact this. > > > > At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and > > released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping > > so as to reuse the same ports freeze). > > > > The ports tree is not even close to stable enough to release right now. > Given that Kris repeatedly tells me and others that the ports system > is only supported on the latest freebsd release (meaning one has to be > upgrading freebsd on their servers every few months to get this > support) if 7.0 and 6.3 are released around the same time will the > ports tree be supported on both? I believe you misunderstood something. Where do you think Kris said that? Fabian He said using the ports is only supported in the latest FreeBSD release, so eg. its not supported in 5.5 and 6.0 and 6.1. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
On 02/06/07, Brandon S. Allbery KF8NH <[EMAIL PROTECTED]> wrote: On Jun 2, 2007, at 3:45 , Chris wrote: > Given that Kris repeatedly tells me and others that the ports system > is only supported on the latest freebsd release (meaning one has to be > upgrading freebsd on their servers every few months to get this > support) if 7.0 and 6.3 are released around the same time will the > ports tree be supported on both? I think you're confused by terminology. As I understand it, the ports tree is supported on -CURRENT and the latest -STABLE series: that is, currently on 6.x and 7.x (and possibly 5.x still since RELENG_5 and RELENG_6 were both being released for a while), but not RELENG_4 or earlier. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED] electrical and computer engineering, carnegie mellon universityKF8NH So my question remains when we have 7.0 and 6.3 both STABLE releases will the ports tree not be supported in 6.3 a just released version of FreeBSD? Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
On 02/06/07, Kris Kennaway <[EMAIL PROTECTED]> wrote: On Sat, Jun 02, 2007 at 02:02:44PM +0200, Fabian Keil wrote: > Chris <[EMAIL PROTECTED]> wrote: > > > On 29/05/07, Mark Linimon <[EMAIL PROTECTED]> wrote: > > > On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote: > > > > Agreed. 6.3-RELEASE would nominally be due around July but the lack > > > > of any schedule on http://www.freebsd.org/releng/ suggests that it will > > > > be later than that. The plans to start the 7.0-RELEASE cycle will also > > > > impact this. > > > > > > At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in July and > > > released in Aug/Sep, with 6.3 quickly following (perhaps even overlapping > > > so as to reuse the same ports freeze). > > > > > > The ports tree is not even close to stable enough to release right now. > > > Given that Kris repeatedly tells me and others that the ports system > > is only supported on the latest freebsd release (meaning one has to be > > upgrading freebsd on their servers every few months to get this > > support) if 7.0 and 6.3 are released around the same time will the > > ports tree be supported on both? > > I believe you misunderstood something. Where do you think Kris said that? Yep, looks like he's confused again. I hope it's not a terminal condition. Kris Please repeat what you told me when I asked why a variable I had to set on 6.1 machines wasnt put in UPDATING. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
Chris wrote: > So my question remains when we have 7.0 and 6.3 both STABLE releases > will the ports tree not be supported in 6.3 a just released version of > FreeBSD? I can't help but get the impression that you're spoiling for a fight here, so let me ask you to take step 1, which is relax a little. You are focusing on released version numbers when you ask about ports support, and we generally focus on release branches. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html for more information about that. We will be supporting ports for RELENG_5 and _6, and RELENG_7 after it's created from what is now HEAD. Where I think the confusion is coming in is in regards to support for a specific version number that is older than the latest version in that branch. For example, support for 6.1 which is an older release on the RELENG_6 branch. We do our best to provide ports support for older versions on currently supported branches, but it's not always possible to do so. You can search the archives of the ports list for information on why just supporting 3 active branches (which will be 4 after RELENG_7 is branched) for over 16,000 ports is a pretty massive undertaking. I hope this makes the situation more clear. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
On Mon, Jun 04, 2007 at 09:17:17PM +0100, Chris wrote: > On 02/06/07, Kris Kennaway <[EMAIL PROTECTED]> wrote: > >On Sat, Jun 02, 2007 at 02:02:44PM +0200, Fabian Keil wrote: > >> Chris <[EMAIL PROTECTED]> wrote: > >> > >> > On 29/05/07, Mark Linimon <[EMAIL PROTECTED]> wrote: > >> > > On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote: > >> > > > Agreed. 6.3-RELEASE would nominally be due around July but the > >lack > >> > > > of any schedule on http://www.freebsd.org/releng/ suggests that it > >will > >> > > > be later than that. The plans to start the 7.0-RELEASE cycle will > >also > >> > > > impact this. > >> > > > >> > > At BSDCan, Ken Smith mentioned that 7.0 is due to be branched in > >July and > >> > > released in Aug/Sep, with 6.3 quickly following (perhaps even > >overlapping > >> > > so as to reuse the same ports freeze). > >> > > > >> > > The ports tree is not even close to stable enough to release right > >now. > >> > >> > Given that Kris repeatedly tells me and others that the ports system > >> > is only supported on the latest freebsd release (meaning one has to be > >> > upgrading freebsd on their servers every few months to get this > >> > support) if 7.0 and 6.3 are released around the same time will the > >> > ports tree be supported on both? > >> > >> I believe you misunderstood something. Where do you think Kris said that? > > > >Yep, looks like he's confused again. I hope it's not a terminal > >condition. > > > >Kris > > > > > > > > > > Please repeat what you told me when I asked why a variable I had to > set on 6.1 machines wasnt put in UPDATING. Quoting from http://www.freebsd.org/ports/: -- The Ports Collection supports the latest release on the FreeBSD-CURRENT and FreeBSD-STABLE branches. -- i.e. just because 7.0 is released starting a new -STABLE branch does not mean that the other -STABLE branches lose support. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
>From Doug Barton <[EMAIL PROTECTED]>, Mon, Jun 04, 2007 at 01:55:01PM -0700: > Chris wrote: > > > So my question remains when we have 7.0 and 6.3 both STABLE releases > > will the ports tree not be supported in 6.3 a just released version of > > FreeBSD? > You are focusing on released version numbers when you ask about ports > support, and we generally focus on release branches. See > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html > for more information about that. We will be supporting ports for > RELENG_5 and _6, and RELENG_7 after it's created from what is now HEAD. In particular, if a port breaks on 6.1 but works on 6.2, it is likely that a POLA violation is afoot somewhere. This doesn't mean that the issue will be fixed but instead that something of this sort is unlikely. Unlike in other operating systems, FreeBSD is incredibly consistent between minor version numbers. Usually this means things just work. e.g., throughout the life of 4.x I rarely encountered problems because of mixing PORTS and an older release of 4.x. And by rarely I mean I don't remember any examples of it happening. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
