Date: Wed, 24 Aug 2005 10:47:06 -0700 From: garys@opusnet.com (Gary W. Swearingen) To: David Kelly <dkelly@hiwaay.net> Cc: questions@freebsd.org Subject: Re: creating filesystem images Message-ID: <n7mzn7dy79.zn7@mail.opusnet.com> In-Reply-To: <20050824154854.GA63910@Grumpy.DynDNS.org> (David Kelly's message of "Wed, 24 Aug 2005 10:48:54 -0500") References: <430C568B.5060501@azimainc.com> <44d5o3tm57.fsf@be-well.ilk.org> <20050824154854.GA63910@Grumpy.DynDNS.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David Kelly <dkelly@hiwaay.net> writes: > The advantage of dump/restore is that only the necessary data is > written. With dd all the unused blocks on the media are also written, > including the filesystem, which will probably work on the larger card. If you don't mind educating me further for no particular need... I've long known about the UNIX concept of everything being a string of bytes, but came to the conclusion early in my Linux days that disks couldn't be used as a filesystem after a "dd" unless their cylinders were the same size (or maybe it was just tracks). Has this all gone away with FreeBSD's removal of "block devices" and/or with LBA disks? Can I get always (excepting un-related problems) get usable filesystems after "dd if=/dev/ad1 of=/dev/ad1 bs=<almost anything>b"? As a separate issue, some boot stuff can get messed up, right? Or do partition tables use LBA now too? Seems like they'd have to, but I don't remember reading about it anywhere. > Tar or pax are not bad choices in addition to dump/restore. bsdtar yes, but pax and gtar (tar in 4.x?) don't handle file flags, if OP needs those.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?n7mzn7dy79.zn7>