Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
brw-rw---- these are the permissions for fd0 in dev directory.
I want to copy fd0 and intall in my other system, if I go to cp it, all that happens is it trys to copy what ever is in the floppy drive. I want to copy the driver.
Need to know how do take away the executable permissions and then to put them back on. How does this work?
Thanks ahead of time.
brw-rw---- these are the permissions for fd0 in dev directory.
I want to copy fd0 and intall in my other system, if I go to cp it, all that happens is it trys to copy what ever is in the floppy drive. I want to copy the driver.
Need to know how do take away the executable permissions and then to put them back on. How does this work?
Thanks ahead of time.
'b' stands for "block device node". Those are not normal files, they represent devices. You usually shouldn't be interacting with the files inside /dev unless you know what you are doing (tm).
What takes me to my next question: what are you exactly trying to do with the contents of the floppy disk?
The b indicates it is a block "device" file. Copying it would not copy the "driver". The way to make a device file is with use of the mknod command.
Say you have the following:
brw-rw---- 1 jlightne floppy 2, 0 Apr 12 22:12 /dev/fd0
Notice that the fields after floppy (2,0) are NOT size as they would be in a normal file. These are the major,minor number that describe the device.
To create a device with same major/minor on another system you would type:
mknod /dev/fd0 b 2 0
Note that you can create a device file with mknod but this has no meaning if the underlying driver is not already installed on the system on which you create it. You'll get messages like "device not found".
You use the chmod command to set permissions on files but for device files the permissions may be overridden by the driver or the utility that accesses the device. Also the mknod command has a flag to set permissions (mode) at creation.
Type "man mknod" and "man chmod" for more information on the two commands.
I goofed up and did a copy like this. Since its been along time since fooling with linux and not studying first. I wanted to copy mouse to the floppy drive. Yeah I now know how to do it. But I issued this command. Cp mouse fd0 so I figured I messed fd0 up and just deleted it, now I want to get an fd0 back in it. So is it not a driver just a link to the driver? How to get it back?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.