From owner-freebsd-small Sun Jun 3 8:17:50 2001 Delivered-To: freebsd-small@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 5F92037B401 for ; Sun, 3 Jun 2001 08:17:35 -0700 (PDT) (envelope-from oppermann@monzoon.net) Received: (qmail 33371 invoked from network); 3 Jun 2001 15:16:29 -0000 Received: from unknown (HELO monzoon.net) ([62.48.0.122]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 3 Jun 2001 15:16:29 -0000 Message-ID: <3B1A54C1.65CB6B2@monzoon.net> Date: Sun, 03 Jun 2001 17:16:17 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: VN device and dd disk images Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello I want to install 128MB SanDisk instead of an IDE HDD in some of my machines. The 128MB are enough to place a reduced but otherwise normal FreeBSD on it. (So no need for PicoBSD). I've got all that done and my prototype SanDisk is running fine. Now for deployment I simply have a machine with a HDD and dd the whole SanDisk into a file and do it vice versa to make a new SanDisk for deployment. All fine and good until I want to update some of the programs in the dd image of the original SanDisk. Now the idea of using the vn device crossed my mind. Unfortunatly for some reason I'm unable to mount the /dev/vn0 device, either because superblock not found or no permission. Might it be that I did the dd image the wrong way? Which device do I have to dd from the SanDisk to use the image for vn? Will I still be able to dd that file back to a virgin SanDisk and boot directly from it without any modification? Any pointers very appreciated. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message