On Thu 17 Dec 2015 at 21:55:48 +0100, Sven Arvidsson wrote:
> On Thu, 2015-12-17 at 18:56 +, Brian wrote:
> > I don't think any of the solutions do help you to write to a raw
> > device, whether it be a floppy or a USB stick. Writing a Debian ISO
> > to USB is not uncommon here and I do not ap
Sven Arvidsson writes:
> dd'ing an image to a raw device does require root.
Why? If it's a removable device and not a system filesystem, it
wouldn't be unreasonable to give such access to anyone logged in
at the console, on the grounds that they could otherwise take
the device away and write it o
Hi,
Sven Arvidsson wrote:
> Writing ISO to USB could also be done through udisks presumably?
A safe method which distinguishes removable media from
the fixely installed disks would be of great interest for
https://www.debian.org/CD/faq/#write-usb
Have a nice day :)
Thomas
isk image to /dev/fd0, and I'm not sure how the solutions
> could help me, but really, it's rare enough that I don't mind
> sudoing.
> I just thought it was an interesting regression.
If sudo becomes a chore you could write a simple udev rule that adds
back the floppy gro
On Thu, 2015-12-17 at 18:56 +, Brian wrote:
> I don't think any of the solutions do help you to write to a raw
> device,
> whether it be a floppy or a USB stick. Writing a Debian ISO to USB is
> not uncommon here and I do not appreciate having to be root to do it.
> A
> mistake in one letter in
ation, and I have to use it occasionally! I just noticed that
> >> my
> >> user was not allowed to write to /dev/fd0 even though it belongs to
> >> the group "floppy". I found that /dev/fd0 belongs to the group
> >> "disk",
> >> and I d
was not allowed to write to /dev/fd0 even though it belongs to
>> the group "floppy". I found that /dev/fd0 belongs to the group
>> "disk",
>> and I don't think it should. Granting a user the ability to write to
>> floppies is not nearly as dangerous
On Wed, 2015-12-16 at 22:09 +0100, Anders Andersson wrote:
> Believe it or not, but I still have a floppy disk drive in my
> workstation, and I have to use it occasionally! I just noticed that
> my
> user was not allowed to write to /dev/fd0 even though it belongs to
> the group &q
On 12/16/2015 10:09 PM, Anders Andersson wrote:
Believe it or not, but I still have a floppy disk drive in my
workstation, and I have to use it occasionally! I just noticed that my
user was not allowed to write to /dev/fd0 even though it belongs to
the group "floppy". I found tha
Believe it or not, but I still have a floppy disk drive in my
workstation, and I have to use it occasionally! I just noticed that my
user was not allowed to write to /dev/fd0 even though it belongs to
the group "floppy". I found that /dev/fd0 belongs to the group "disk",
On Tue, Jan 02, 2007 at 09:47:28AM -0600 or thereabouts, Hugo Vanwoerkom wrote:
> Stephen wrote:
> >Happy New Year !
> >
> >I did something stupid, when tired and working as root.
>
>
> What did you do?
Hi Hugo:
I believe I did 'rm /dev/fd0/*'
Any
Stephen wrote:
Happy New Year !
I did something stupid, when tired and working as root.
What did you do?
I'm now getting
this error when attempting to mount/read a floppy;
"Inappropriate ioctl for device"
running 'hdparm -Tt /dev/fd0' returns the fol
Happy New Year !
I did something stupid, when tired and working as root. I'm now getting
this error when attempting to mount/read a floppy;
"Inappropriate ioctl for device"
running 'hdparm -Tt /dev/fd0' returns the following;
/dev/fd0:
read(20971
On Thu, Nov 16, 2006 at 05:12:27PM -0500, Douglas Tutty wrote:
> On Tue, Nov 14, 2006 at 01:58:58PM -0500, [EMAIL PROTECTED] wrote:
>
> > But when I tried
> > ls /dev/fd0
> > it told me
> >
> > ls: /dev/fd0: No such file or directory
> >
>
On Tue, Nov 14, 2006 at 01:58:58PM -0500, [EMAIL PROTECTED] wrote:
> But when I tried
> ls /dev/fd0
> it told me
>
> ls: /dev/fd0: No such file or directory
>
> Indeed, ls /dev says
>
[ its not there ]
> Where is my floppy drive?
>
Are you running a pla
Is there anything besides hardware failure of the write
circuitry in either the floppy drive or the controller which
would make it able to perfectly read diskettes but not
format or write?
I did try the MAKEFLOPPIES script which ran correctly, but doing
a low-level format of a diskette pro
I tried running lilo on my sarge system today, with the
lilo.conf line
boot=/dev/fd0
instead of the former
boot=/dev/hda
This used to work. But this time I was told:
LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21
On Sun, Feb 26, 2006 at 08:05:08PM -0500, [EMAIL PROTECTED] wrote:
> I have a floppy drive on my srge system. I used to access it as
> /dev/fd0. But there's no /dev/fd0 in my sarge system any more.
> There is a /dev/fd/0, /dev/fd/1, /dev/fd/2, and /dev/fd/3.
>
> Could /dev/
I have a floppy drive on my srge system. I used to access it as
/dev/fd0. But there's no /dev/fd0 in my sarge system any more.
There is a /dev/fd/0, /dev/fd/1, /dev/fd/2, and /dev/fd/3.
Could /dev/fd/0 be the new name for /dev/fd/0? Or do I need to look
elsewhere for the problem?
-- he
On Tue, May 25, 2004 at 10:07:11AM -0400, Derrick 'dman' Hudson wrote:
> /dev/fd refers to the file descriptors for the current process and is
> unrelated to floppy drives. (FYI)
Thanks for the info. So is something like /proc//fd ?
> Just out of curiosity, do you have a /dev/floppy directory
dprobe floppy
Thanks for your reply. After rebooting (a failed effort to get grub
to work on this setup) I could see the /dev/fd0 created by MAKEDEV. I
am not sure why I could not find it. Maybe it was related to a
"floppy" module not loaded.
Regards
Johann
--
Johann Spies Tel
On Tue, May 25, 2004 at 02:32:28PM +0200, Johann Spies wrote:
| I have done two thing that could have changed it:
|
| 1. Installed kernel-image-2.6.6-i686
# modprobe ide-floppy
| 2. Ran the mkdev.sh script from lm-sensors-sources.
|
| Now there are no devices like /dev/fd0-3
|
| zsh % ls
On Tue, May 25, 2004 at 02:32:28PM +0200, Johann Spies wrote:
> I have done two thing that could have changed it:
>
> 1. Installed kernel-image-2.6.6-i686
> 2. Ran the mkdev.sh script from lm-sensors-sources.
>
> Now there are no devices like /dev/fd0-3
May be unrelated, but
I have done two thing that could have changed it:
1. Installed kernel-image-2.6.6-i686
2. Ran the mkdev.sh script from lm-sensors-sources.
Now there are no devices like /dev/fd0-3
zsh % ls -la /dev/fd*
lrwxrwxrwx1 root root 13 2004-05-24 19:07 /dev/fd ->
/proc/self/fd
I recently installed kernel 2.4.8 and the compilation went
fine. To test it before actually changing from my previous
version I did a dd if=bzImage of=/dev/fd0 bs=8192 using
a Imation floppy 2.0MB, High density formatted with
superformat /dev/fd0 hd
On using this diskette to boot up, there is a
On Sat, Feb 03, 2001 at 04:29:36PM +, cls/cs wrote:
:debs,
:
:i floppy boot potato.
:
:if i need to access mount or superformat another floppy, i cannot access
/dev/fd0.
Why can't you access /dev/fd0?
Unless the root file system is also on the floppy, this shouldn't be a
problem
debs,
i floppy boot potato.
if i need to access mount or superformat another floppy, i cannot access
/dev/fd0.
suggustions?
ti,a.
bentley taylor.
att.
//
running: debian gnu/linux ( http://www.debian.org )
kernel: 2.2.17
Script started on Sat Feb 3 16:25:01 2001
cls210:/home/bt
On Thu, Dec 28, 2000 at 11:33:56PM -0800, kmself@ix.netcom.com wrote:
> >
> > /etc/fstab has a line
> > /dev/fd0/floppyauto (plus a couple of numbers which I can't
> > remember off the top of my head).
>
> What I suspect is that you are trying to mount
are automounter
packages which will take care of this for you automatically, but you've
got other problems to deal with first.
> If I do
> mount /dev/fd0 /floppy
> the light on the floppy drive goes on... and stays on... forever. At
> this point my system is completely frozen a
I updated my system to "woody" and custom built a 2.4.0test12 kernel.
With a floppy in the drive
cd /floppy
ls
never returns any files
If I do
mount /dev/fd0 /floppy
the light on the floppy drive goes on... and stays on... forever. At
this point my system is completely frozen and I ha
On Tue, Dec 21, 1999 at 07:53:11PM -0600, Matt Garman wrote:
>
> Hello:
>
> I'm trying to make the "base" disks to do a potato install.
>
> When I do a "dd if=root.bin of=/dev/fd0," I get the following:
>
> dd: /dev/fd0: Input/output error
Subject: /dev/fd0: Input/output error (making base disks)
Date: Tue, Dec 21, 1999 at 07:53:11PM -0600
In reply to:Matt Garman
Quoting Matt Garman([EMAIL PROTECTED]):
>|
>| Hello:
>|
>| I'm trying to make the "base" disks to do a potato install
On 21/12/99 Matt Garman wrote:
I'm trying to make the "base" disks to do a potato install.
When I do a "dd if=root.bin of=/dev/fd0," I get the following:
dd: /dev/fd0: Input/output error
1113+0 records in
1112+0 records out
looks like a disk error prevented the c
Hello:
I'm trying to make the "base" disks to do a potato install.
When I do a "dd if=root.bin of=/dev/fd0," I get the following:
dd: /dev/fd0: Input/output error
1113+0 records in
1112+0 records out
And again with "cmp root.bin /dev/fd0":
cmp: /dev/fd0:
Yifang Dai <[EMAIL PROTECTED]> writes:
> I hit this strange problem today, on my potato machine:
>
> /boot# dd if=bzImage-2.2.12 of=/dev/fd0
> dd: /dev/fd0: Read-only file system
do you have it mounted? try umount /dev/fd0 and see if
that lets it work.
On Tue, Oct 05, 1999 at 04:11:00PM -0700, Eric G . Miller wrote:
> On Tue, Oct 05, 1999 at 12:59:06PM -0400, Yifang Dai wrote:
> > I hit this strange problem today, on my potato machine:
> >
> > /boot# dd if=bzImage-2.2.12 of=/dev/fd0
> > dd: /dev/fd0: Read-only file
On Tue, Oct 05, 1999 at 12:59:06PM -0400, Yifang Dai wrote:
> I hit this strange problem today, on my potato machine:
>
> /boot# dd if=bzImage-2.2.12 of=/dev/fd0
> dd: /dev/fd0: Read-only file system
>
> Here is the permission for /dev/fd0
>
> /boot# ls -l /dev/f
I hit this strange problem today, on my potato machine:
/boot# dd if=bzImage-2.2.12 of=/dev/fd0
dd: /dev/fd0: Read-only file system
Here is the permission for /dev/fd0
/boot# ls -l /dev/fd0
brw-rw-r-- 1 root floppy 2, 0 Oct 4 17:41 /dev/fd0
The floppy is not write-protected
On Sun, 29 Aug 1999, Paul wrote:
> I`ve tried looking for "makedev" which dselect tells me is installed but
> all I seem to have are the doc files and the /var/lib/dpkg/info/ files.
Makedev the binary (actually it's a script) is in /dev.
As a quick fix, you can do (as root
> From: Paul <[EMAIL PROTECTED]>
>
> ... I managed to "rm /dev/fd0". Now although
> "locate" still shows it as existing ...
Remember that locate displays only cached information.
Daniel
On Sun, Aug 29, 1999 at 09:06:15PM +0100, Paul wrote:
> all I seem to have are the doc files and the /var/lib/dpkg/info/ files.
> How do I restore my floppy drive?
Ooops!
I meant:
./MAKEDEV fd0
Sorry
On Sun, Aug 29, 1999 at 09:06:15PM +0100, Paul wrote:
> I`ve tried looking for "makedev" which dselect tells me is installed but
> all I seem to have are the doc files and the /var/lib/dpkg/info/ files.
> How do I restore my floppy drive?
cd /dev
./MAKEDEV fd
This should create the symlinks.
In a moment of stupidity whilst attempting to learn how to copy from
hard drive to floppy disc I managed to "rm /dev/fd0". Now although
"locate" still shows it as existing attempting to "mount /floppy" gives
me the message "mount: special device /dev/fd0 does not
On 29-Dec-98 Brent Hueth wrote:
>
> I can't seem to get my floppy drive to work under Debian. For example,
> when trying to format a disk with:
>
> superformat /dev/fd0 hd sect=18
>
Try something like mkfs.
I can't seem to get my floppy drive to work under Debian. For example,
when trying to format a disk with:
superformat /dev/fd0 hd sect=18
I get:
old capacity=12500
Measuring drive 0's raw capacity
Fatal error while measuring raw capacity
0: 40
1: 01
2: 00
3: 00
4: 00
5: 01
6: 08
W
an error
message box, and lower on the screen there is a message "/dev/fd0:
Device not configured".
Any help would be much appreciated!!! Thanks in advance!!!
More details follow:
The Rescue disk that says it's ver 2.0. I tried the regular and
tecra flavors with the same results.
I
My fstab had the following entry to enable easy mounting of fd0. The "2"
in field 6 was meant to enable a fsck when a floppy was mounted.
/dev/fd0/floppy ext2 noauto 0 2
This used to work, but now on system boot it complains that it cannot
chec
Mario Olimpio de Menezes <[EMAIL PROTECTED]> writes:
> floppy0: Unable to allocate DMA memory
>
> With little knowledge about this problem, I did an rmmod in some
> modules not being used at the moment and got the floppy accessible again.
> Today the problem was back, and there isn't
Hi,
Yesterday I was surprised with a new problem. When trying to
access the floppy (I always did it), with mdir as well as with mount, I
got the following message from dmesg:
floppy0: Unable to allocate DMA memory
With little knowledge about this problem, I did an rmmod in some
Hello
yesterday the upgrade to version 1.2.9 was done at my home box resulting
in user access problems to /dev/fd0 which are 660 as default using
mtools.
I remember with debian version 1.2.2 I fixed this problem setting the
binary of mtools to ownership of root.floppy and
Hi there,
I have Debian1.2 running kernel 2.0.27. The tar package version is
1.11.8-5.
I can create multipy floppy archive using 'tar cvMf /dev/fd0' but
NOT retrieving it using 'tar xvMf /dev/fd0'.
I always get 'Segmentation faults and then core dumped' when I t
51 matches
Mail list logo
