Date: Mon, 10 Apr 2017 19:14:14 +0000 (UTC) From: Nikolai Lifanov <lifanov@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r438197 - in head/sysutils/ffs2recov: . files Message-ID: <201704101914.v3AJEEn2097169@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: lifanov Date: Mon Apr 10 19:14:14 2017 New Revision: 438197 URL: https://svnweb.freebsd.org/changeset/ports/438197 Log: unbreak sysutils/ffs2recov o fix MASTER_SITES o add WWW o assign maintainership to submitter o fix on CURRENT PR: 218174 Submitted by: Chris Hutchinson <portmaster@bsdforge.com> Added: head/sysutils/ffs2recov/files/ head/sysutils/ffs2recov/files/patch-inode.c (contents, props changed) Modified: head/sysutils/ffs2recov/Makefile head/sysutils/ffs2recov/pkg-descr Modified: head/sysutils/ffs2recov/Makefile ============================================================================== --- head/sysutils/ffs2recov/Makefile Mon Apr 10 18:52:18 2017 (r438196) +++ head/sysutils/ffs2recov/Makefile Mon Apr 10 19:14:14 2017 (r438197) @@ -3,12 +3,15 @@ PORTNAME= ffs2recov PORTVERSION= 1.0 +PORTREVISION= 1 CATEGORIES= sysutils -MASTER_SITES= http://www.exit.com/Archives/FreeBSD/ +MASTER_SITES= http://BSDforge.com/projects/source/sysutils/ffs2recov/ -MAINTAINER= ports@FreeBSD.org +MAINTAINER= portmaster@bsdforge.com COMMENT= Utility to recover UFS2 filesystems +LICENSE= BSD2CLAUSE + USES= tar:bzip2 uidfix WRKSRC= ${WRKDIR}/${PORTNAME} Added: head/sysutils/ffs2recov/files/patch-inode.c ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sysutils/ffs2recov/files/patch-inode.c Mon Apr 10 19:14:14 2017 (r438197) @@ -0,0 +1,13 @@ +--- inode.c.orig 2017-04-05 19:51:41 UTC ++++ inode.c +@@ -52,6 +52,10 @@ + #define NO_IN_EXTERNS + #include "ffs2recov.h" + ++#ifdef UFS_NDADDR ++#define NDADDR UFS_NDADDR ++#endif ++ + static uint64_t direct_maxblk; /* Max block # for a direct block. */ + static uint64_t single_maxblk; /* Max block # for a single indirect. */ + static uint64_t double_maxblk; /* Max block # for a double indirect. */ Modified: head/sysutils/ffs2recov/pkg-descr ============================================================================== --- head/sysutils/ffs2recov/pkg-descr Mon Apr 10 18:52:18 2017 (r438196) +++ head/sysutils/ffs2recov/pkg-descr Mon Apr 10 19:14:14 2017 (r438197) @@ -1,24 +1,28 @@ -This is the UFS2 version of ffsrecov, heavily (and I do mean _heavily_) based -on John-Mark Gurney's program of the same name. It does basically the same -thing, only it's a little more resistant to crashes caused by bad pointers, -offsets and the like, and it does a little more than his did. Don't contact -him for problems with this program, it's definitely _my_ fault if it breaks. +This is the UFS2 version of ffsrecov, heavily (and I do mean _heavily_) +based on John-Mark Gurney's program of the same name. It does basically +the same thing, only it's a little more resistant to crashes caused by +bad pointers, offsets and the like, and it does a little more than his +did. Don't contact him for problems with this program, it's definitely +_my_ fault if it breaks. -This program is not ready for prime time. It has some shortfalls, it has a -bunch of new options that are mostly undocumented and the manpage could -stand to be rewritten. One _good_ thing is that it now uses the libufs -library and is therefore not as dependent on carrying around low-level code. +This program is not ready for prime time. It has some shortfalls, it +has a bunch of new options that are mostly undocumented and the manpage +could stand to be rewritten. One _good_ thing is that it now uses the +libufs library and is therefore not as dependent on carrying around +low-level code. -On the other hand, it worked for me. Using this tool, I was able to recover -almost all of a several-hundred-gigabyte file system that had been stomped -by a misconfigured RAID controller. (That's why I wrote the thing in the -first place, in fact.) With the right knowledge and a lot of patience, -it is possible to recover most or all of a trashed file system, at least if -it's not _too_ trashed. +On the other hand, it worked for me. Using this tool, I was able to +recover almost all of a several-hundred-gigabyte file system that had +been stomped by a misconfigured RAID controller. (That's why I wrote the +thing in the first place, in fact.) With the right knowledge and a lot +of patience, it is possible to recover most or all of a trashed file +system, at least if it's not _too_ trashed. I'm releasing it under the Berkeley two-clause license in the hope that -someone with more time will pick it up, polish it and make something -a little more useful out of it. +someone with more time will pick it up, polish it and make something a +little more useful out of it. Frank Mayhar frank@exit.com + +WWW: http://BSDforge.com/projects/sysutils/ffs2recov/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201704101914.v3AJEEn2097169>