Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Re: Disk geometry
- To: tlug@example.com
- Subject: Re: [tlug] Re: Disk geometry
- From: Frank Bennett <bennett@example.com>
- Date: Thu, 4 Apr 2002 20:25:46 +0900
- Content-disposition: inline
- Content-type: text/plain; charset=iso-2022-jp
- In-reply-to: <20020403113431.GC5613@example.com>
- References: <20020402094134.GA31262@example.com> <3CAA8E68.CC5FF784@example.com> <20020403113431.GC5613@example.com>
- User-agent: Mutt/1.3.25i
On Wed, Apr 03, 2002 at 01:34:31PM +0200, Tobias Diedrich wrote: > For a sector by sector image you could use dd with conv=noerror,sync to > make sure it continues even after read errors. Many thanks. What is the reason for the "sync" (or "block" or "unblock") directive in the example? I'm not sure I understand the "blocks" concept. Is dd sensitive to blocking info forwarded by the device in some way? Or does "sync" just pad out an incomplete final block with nulls? Frank
- Follow-Ups:
- [tlug] Re: Disk geometry
- From: Tobias Diedrich
- References:
- [tlug] Disk geometry
- From: Frank Bennett
- Re: [tlug] Disk geometry
- From: B0Ti
- [tlug] Re: Disk geometry
- From: Tobias Diedrich
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] disk configuration: drive mounting
- Next by Date: Re: [tlug] disk configuration: drive mounting
- Previous by thread: [tlug] Re: Disk geometry
- Next by thread: [tlug] Re: Disk geometry
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links