From owner-freebsd-questions@FreeBSD.ORG Fri Aug 27 07:24:16 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFF0810656A3 for ; Fri, 27 Aug 2010 07:24:16 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 419578FC19 for ; Fri, 27 Aug 2010 07:24:16 +0000 (UTC) Received: from [193.31.11.193] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1OotIM-0006ou-1w for freebsd-questions@freebsd.org; Fri, 27 Aug 2010 09:24:14 +0200 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id o7R7OG5A002607 for ; Fri, 27 Aug 2010 09:24:16 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id o7R7OGgw002606 for freebsd-questions@freebsd.org; Fri, 27 Aug 2010 09:24:16 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Fri, 27 Aug 2010 09:24:16 +0200 From: Matthias Apitz To: freebsd-questions@freebsd.org Message-ID: <20100827072416.GA2516@current.Sisis.de> Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org References: <20100823070819.GB2539@current.Sisis.de> <4C7241C2.2000305@otenet.gr> <20100823112621.GA4367@current.Sisis.de> <4C725BFC.90006@otenet.gr> <20100824084225.GA2160@current.Sisis.de> <4C739A78.4070303@otenet.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4C739A78.4070303@otenet.gr> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) X-Con-Id: 51246 X-Originating-IP: 193.31.11.193 Subject: installing FreeBSD in VMWare-player (was: running FreeBSD on Windows host) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Aug 2010 07:24:16 -0000 El día Tuesday, August 24, 2010 a las 01:10:00PM +0300, Manolis Kiagias escribió: > > I have produced three dumps: from the /, /var and /usr file system. The > > man page of restore(8) reads about creating pristine file system, made > > by newfs(8). Later, in the VM environment, I'd like to have only one big > > file system... Is it possible to restore the tree dumps into one big > > file system or do I have to rebuild the same slicing as I now have? > > > > You won't have to rebuild the slicing. Just create the relevant > directories in your big file system, cd into them and use restore. Will it be a problem having the kernel /boot/* in this case far away from the beginning of the partition? I did some 1st tests with installing FreeBSD into a VM. I grabed some other laptop which runs already Win7 and installed a VMWare-player in it to do some tests. Of course the VMWare-player was not able to boot from a prepared USB key. A workaround was a boot from some ISO image of a "boot manger" (I used plpbt-5.0.10.zip from http://www.plop.at/) which allows you to choose the USB storage as boot device after 1st stage boot. The system comes up fine from the USB key and I created a 160 GByte slice with the standard procedure like: # fdisk -I /dev/ad0 # fdisk -B /dev/ad0 # bsdlabel -w ad0s1 auto # bsdlabel -B ad0s1 edit the disk label and change partition "a" from "unused" to "4.2BSD" as partition type: # setenv EDITOR /usr/bin/vi # bsdlabel -e ad0s1 create the future root-filesystem on it and mount it to /mnt for the installation: # newfs -m 0 -o space /dev/ad0s1a # mount /dev/ad0s1a /mnt install freebsd into /mnt; this assumes that you have the kernel and userland in /usr/src and /usr/obj ready to be installed; # cd /usr/src # make installworld DESTDIR=/mnt The 'make installworld' failed with errors in the Makefiles (...); for example the file /usr/src/lib/libc/uuid/Makefile.inc had a line like this: SRCS+? uuid_compare.c uuid_create.c uuid_create_nil.c uuid_equal.c \ uuid_from_string>c uuid_hash.c uuid_is_nil.c uuid_stream.# \ uuid_to_string.c where it should have: SRCS+= uuid_compare.c uuid_create.c uuid_create_nil.c uuid_equal.c \ uuid_from_string.c uuid_hash.c uuid_is_nil.c uuid_stream.c \ uuid_to_string.c (note the ? singn and the # sign), i.e. the content was broken and some other files were missing in the /usr/src tree of the USB key. I used the same key last year to install from it the system to my netbook EeePC and it worked like it should. Since then the USB key was unused and carried around in the bag of my laptop. Is it possible that the data gets corrupt on an USB key after some time? I'm wondering why the system even is intact to be booted from... Will prepare the key again or just fill in the dumps I have... matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre!