[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] dd - access to block device

To: mint@lists.fishpool.fi
Subject: Re: [MiNT] dd - access to block device
From: Petr Stehlik <joy@sophics.cz>
Date: Fri, 30 Jul 2004 09:50:53 +0200
Delivered-to: mint@lists.fishpool.fi
In-reply-to: <Pine.NEB.4.60.0407300943270.4429@wh58-508.st.uni-magdeburg.de>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <Pine.LNX.4.40.0407300857350.29063-100000@laura.studionet> <1091173025.5178.0.camel@joy.sophics> <Pine.NEB.4.60.0407300943270.4429@wh58-508.st.uni-magdeburg.de>
Sender: mint-bounce@lists.fishpool.fi

V Pá, 30. 07. 2004 v 09:44, Frank Naumann píše:
> >> You have to write to the device itself, so indeed drive letters won't
> >> work.
> >
> > Sometimes drive letters do work (mkfs, chkfs, fdisk?)
> 
> Yes, because these tools are linked against the libIO that overwrite 
> open/write/seek and such things that catch these drive letters and go over 
> XHDI for raw access.

didn't know about libIO. Is it able to passthrough things that don't
look like a drive letter? Would it be possible to create kind of a
'rawdd' that way?

Petr

Follow-Ups:
- Re: [MiNT] dd - access to block device
  - From: Frank Naumann <fnaumann@mail.cs.uni-magdeburg.de>

References:
- Re: [MiNT] dd - access to block device
  - From: Maurits van de Kamp <maurits@bassment.nu>
- Re: [MiNT] dd - access to block device
  - From: Petr Stehlik <joy@sophics.cz>
- Re: [MiNT] dd - access to block device
  - From: Frank Naumann <fnaumann@mail.cs.uni-magdeburg.de>

Prev by Date: Re: [MiNT] dd - access to block device
Next by Date: Re: [MiNT] dd - access to block device
Previous by thread: Re: [MiNT] dd - access to block device
Next by thread: Re: [MiNT] dd - access to block device
Index(es):
- Date
- Thread