similar to: disk image creation, step by step

Displaying 20 results from an estimated 1000 matches similar to: "disk image creation, step by step"

2007 Jun 27
5
FreeBSD-6.2 and pxelinx
Hi i want to add the FreeBSD 6.2 release to our installserver according to the manual http://syslinux.zytor.com/archives/2007-April/008420.html But if I type FreeBSD-6.2 at the pxelinux boot prompt the created image load but nothing happens. ?boot: FreeBSD-6.2 Loading memdisk.... Loading
2008 Feb 22
0
mddisk(ramdisk) root system that image size limit ?
OS: FreeBSD 6.2-RELEASE Environment = VMWare (Version 5) and Computer (CPU=Intel P4 2.4G, Memory=Kingston 1G DDR400, Storage=2G CF) create a less-than 100MB of image (image for ramdisk, mfs root) The loader.rc { load kernel // The kernel used 6.2 GENERIC load -t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=95k } above config can boot normal. create
2013 Jul 31
4
Booting FreeBSD
Hi, I am trying to create a hybrid ISO image for FreeBSD 9.2 using syslinux 6.01 and isohybrid.pl I found at http://www.overclockix.com/sources/isohybrid.pl (I know there is a C version in syslinux but I haven't been able to build it yet due to the UUID library being different to the one in FreeBSD). According to the wiki mboot.c32 can boot FreeBSD, however I haven't been able to get it
2006 Mar 02
1
Panics with md/gvinum/ufs
Hi, I've done some strange(?) experiments and I managed to get a panic of type "baddir" and just now another one that only rebooted my system instantly without writing a vmcore. I don't know if this is important. I could not find any information on how gvinum detects failed hard disks. That's why I tried something really simple. Steps to reproduce: 1) dd if=/dev/zero of=a
2013 Dec 16
1
FreeBSD 10.0-RC2 Now Available
The second RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here (or any of the FreeBSD mirror sites):
2013 Aug 07
1
FreeBSD9.2-RC1 bootonly network installation fetch error (snapshots vs releases)
Hello :-) I am installing the 9.2-RC1 bootonly iso which wants to download stuff from snapshots while it is in releases directory: Installer wants to get 9.2-RC1 stuff from here (where it is missing): ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/i386/ While the stuff is at: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RC1/ Please fix :-) Best regards :-) Tomek -- CeDeROM,
2003 Dec 16
2
syslinux bootsector info?
Mr Anvin, is there a specific loading address used with the Syslinux bootsector (to load ldlinux.sys)? like msdos 0x70, freedos 0x60 we're trying to have a SYS program that can create bootsector for other OS's than FreeDOS only. not much luck though :( this way I'm trying to avoid the use of syslinux.exe/com (need the diskspace that it would save by not including this program) I
2008 Dec 02
6
repeatable crash on RELENG7
While trying to speed up nanobsd builds, I mounted /usr/obj on a ramdisk and found my box crashing. Thinking it might be hardware, I tried a separate machine, but with the same results. I have 4G of ram (i386). Am I just running out of some kernel memory ? If so, is there anything I can adjust to prevent this, yet still use mfs in this way ? mdconfig -a -t malloc -s 1800M newfs /dev/md0
2008 Oct 15
3
SATA devices not added/probed from ICH7 sata300 controller, FreeBSD7.0, 7.1beta, 8.0 Daily
On Tue, Oct 14, 2008 at 09:52:09PM -0400, John R. Huston wrote: > Hi, I am not very familiar with using mailing lists so if I have made > a mistake in the format or scope of the message please correct me. I > am pretty desperate for an answer by now so any help at all is really > very appreciated. > > I have a Shuttle SD30G2 computer (Specs: >
2008 Sep 13
0
FreeBSD 7.1-BETA/6.4-BETA Available...
The FreeBSD 7.1-BETA and 6.4-BETA builds are now available on the FreeBSD FTP mirror sites. This is the first step in the release process for FreeBSD-7.1 and FreeBSD-6.4. This set of builds do not include pre-built packages. The ISOs are available from: ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/7.1/ ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/6.4/
2005 Aug 31
1
booting from MS-dos disk.@home.nl
(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk
2012 Feb 11
3
9.0-RELEASE PV from scratch on XCP v1.1.0
Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under
2009 Aug 04
5
FreeBSD starting by HVM
Hi. How I can see what happend in my domU??? dom0 Debian Lenny domU FreeBSD6.4 xen 3.2-1 -------- Xen 3.2-1 :/etc/xen# xm create tttt.cfg Using config file "./tttt.cfg". Started domain freebsd -------- /etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2969 4 r----- 48.0 freebsd
2013 Dec 09
0
FreeBSD 10.0-RC1 now available
The first RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. * Please see the change list for an important note regarding the bsdinstall(8) ZFS on GELI option. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are
2013 Nov 05
1
FreeBSD 10.0-BETA3 now available
The third BETA build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/ (or any of the FreeBSD
2013 Apr 22
0
FreeBSD 8.4-RC2 Now Available
The second RC build of the 8.4-RELEASE release cycle is now available on the FTP servers for the amd64, i386, and pc98 architectures. The SHA256/MD5 sums are tacked on to the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.4/ (or any of the FreeBSD mirror sites).
2010 Mar 23
0
FreeBSD 7.3-RELEASE Available
The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 7.3-RELEASE. This is the fourth release from the 7-STABLE branch which improves on the functionality of FreeBSD 7.2 and introduces a few new features. There will be one more release from this branch to allow future improvements to be made available in the 7-STABLE branch but at this point most developers are
2008 Feb 22
1
FreeBSD 7.0-RC3 (for amd64/i386 only) Available
We're doing a "mini-RC3" to encourage testing of the Highpoint driver (hptrr) backout. Testing of 7.0-RC2 showed there were problems with the driver update done between RC1 and RC2. Because it's a "mini-RC" targetted at testing of one particular thing we have not bothered with setting up FreeBSD Update. You can use the normal cvsup-and-build method of doing an update
2006 Jan 22
3
Encrypted volume - how?
Hi all, I'm looking for a way to recreate the functionality of PGP Disk (under Win32). Basically, create an encrypted file, which contains a filesystem which can then be mounted in any mount point. I know I can use GELI in FreeBSD 6 - as I understand, it performs the encryption at the partition level (the whole partition is encrypted). I'd like to be able to simply unmount my
2007 Apr 18
7
[patch 0/6] Various cleanups
Hi Andi, Here's a little batch of cleanups: - re-enable VDSO when PARAVIRT is enabled - make the parainstructions symbols match the other altinstructions naming convention - add kernel command-line options to disable altinstructions for smp and pv_ops Oh, and I'm mailing your noreplacement patch back at you, for no particularly good reason. J --