Date: Mon, 26 Jan 2009 16:33:26 +0200 From: Alex Karpovic <alekar2009@gmail.com> To: Chuck Robey <chuckr@telenix.org> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: hex editors, disk info Message-ID: <700ff07a0901260633n2b09d056n64cf6b1def013f04@mail.gmail.com> In-Reply-To: <497D1201.6060503@telenix.org> References: <700ff07a0901251351t629b9606g260447b4cbaef00b@mail.gmail.com> <20090126001710.688b53eb@gluon> <497D1201.6060503@telenix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> That in mind, what's wrong with bpatch? I've used it for binary patching, it > works just fine that that (if my first assumption is totally off-base). You > download from the device, change any required data, and (if the device allows > writes) write it back to the device. Of course, not all devices allow writes. It's a bit uncomfortable. Just for example: I need to search some signatures, which could be anywhere in 640Gb disk, and make some changes around them. And I don't have spare 640+ Gb to copy whole disk to. And even if I would have enough space, it is painfully slow to move 640Gb twice just to make ten minutes editing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?700ff07a0901260633n2b09d056n64cf6b1def013f04>