On Fri, 19 Dec 2014 12:13:59 +0100
Frédéric Marchal <frederic.marc...@wowtechnology.com> wrote:
> A google search reveals it is a common problem that should be fixed with
> sudo hdparm -r0 /dev/sdi
# hdparm -r0 /dev/sdi
/dev/sdi:
setting readonly to 0 (off)
readonly = 0 (off)
after which again:
# dd bs=4M if=debian-live-7.6.0-amd64-rescue.iso of=/dev/sdi && sync
dd: opening `/dev/sdi': Read-only file system
"Karl E. Jorgensen" <k...@jorgensen.org.uk> wrote:
> What does:
> ls -l /dev/sdi
> report? I suspect it will say the file does not exist.
# ls -l /dev/sdi
brw-rw---T 1 root floppy 8, 128 Dec 19 07:59 /dev/sdi
> If /dev/sdi does not exist, dd will attempt to create it. As a normal
> file. Which is probably not what you want...
> Similarly, can /dev actually be written to? The output of a command
> like this would be instructive:
> touch /dev/somefile-which-doesnt-exist
# touch /dev/somefile-which-doesnt-exist
# ls -l /dev/somefile-which-doesnt-exist
-rw-r--r-- 1 root root 0 Dec 19 09:54 /dev/somefile-which-doesnt-exist
My gast remains fiercely flabbered...
Cheers,
Ron.
--
George Orwell was an optimist.
-- Isaac Asimov
-- http://www.olgiati-in-paraguay.org --
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141219150725.1f31a...@ron.cerrocora.org
