From owner-freebsd-questions@freebsd.org  Thu Sep 10 11:59:19 2015
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E562BA01C74
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Thu, 10 Sep 2015 11:59:19 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id AA717175C
 for <freebsd-questions@freebsd.org>; Thu, 10 Sep 2015 11:59:19 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from r56.edvax.de (port-92-195-125-111.dynamic.qsc.de
 [92.195.125.111])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx02.qsc.de (Postfix) with ESMTPS id 3A00427892;
 Thu, 10 Sep 2015 13:59:10 +0200 (CEST)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id t8ABxAuY003271;
 Thu, 10 Sep 2015 13:59:10 +0200 (CEST)
 (envelope-from freebsd@edvax.de)
Date: Thu, 10 Sep 2015 13:59:10 +0200
From: Polytropon <freebsd@edvax.de>
To: Mohsen Pahlevanzadeh <mohsen@pahlevanzadeh.org>
Cc: freebsd-questions@freebsd.org
Subject: Re: xenix (sysv) filesystem and FreeBSD
Message-Id: <20150910135910.23daf037.freebsd@edvax.de>
In-Reply-To: <55F166FF.4040803@pahlevanzadeh.org>
References: <55F13B5A.3070408@pahlevanzadeh.org>
 <20150910104034.b3439c2c.freebsd@edvax.de>
 <55F166FF.4040803@pahlevanzadeh.org>
Reply-To: Polytropon <freebsd@edvax.de>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 11:59:20 -0000

On Thu, 10 Sep 2015 15:48:23 +0430, Mohsen Pahlevanzadeh wrote:
> Can I put _native_ filesystem into kernel ? If yes, please address me....

I think there is no (and never has been a) native support
for Xenix file systems. Furthermore, file system support
has been moved out of the kernel for many file system
types (except the OS's most common ones), so there's
now FUSE to be used for everything else. If there is a
way, I think that's the one to use.

Check out the FreeBSD kernel sources for a list of the
currently supported file systems. See the FUSE documentation
for what other formats can be dealt with in user space.

As Matthew wrote: If you can access the disk, first make
a full (!) copy of it with dd. In case this causes read
errors, use dd_rescue instead. Then work with the copy
only (mdconfig, vnconfig) - this mechanism can represent
different file systems, in MBR or "dedicated", and you
can mount them (if there is support for that file system,
be it UFS or SysV-native) at least read-only, that should
be sufficient.

As I said, in worst case, there are the forensic tools
that work independently (!) from the file system in use.




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...