Snanning with Brother 3-in-one J140W gets killed by signal 11 and signal 5
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
This means you do not have the editor on the system. Do you have one you know how to use?
If yes, use it. If not, the vi editor is always there. So, 'vi 65-libsane.rules' should open the file. Be warned, vi is not very easy to use as a novice. Any editor you now know how to use is going to be easier.
Ok, something happened when I typed in 'vi 65-libsane.rules'!
There's a blinking curser, then lots of little lines and at the bottom it says "65-libsane.rules [new file]!
What next?
C
Quote:
Originally Posted by camorri
This means you do not have the editor on the system. Do you have one you know how to use?
If yes, use it. If not, the vi editor is always there. So, 'vi 65-libsane.rules' should open the file. Be warned, vi is not very easy to use as a novice. Any editor you now know how to use is going to be easier.
Spend a few minutes and look at the document. You need to be able to Open a file, change modes, enter text and save the file. There are instructions for other, more complex editing tasks, you can by pass them for now. See if you can enter the data, as I posted, and save the file in the directory you changed into. It needs to be there so udev can read it.
This, I think is the best way for you to edit the file. I only use vi when there is no other choice. I'm sure there is some editor on your system that is easier. You can look into that when you are not fighting with some problem.
Ok, thank you for the link Cliff.
I have to go home now, but when I get back to Dad's next week I will implement what you said with the vi editor.
[I wouldn't know if one was easier to use than another - I haven't used any at all]
Smiles!
Carla
Thanks!
Quote:
Originally Posted by camorri
So, what we know, the file did not exist, and now you are creating it.
As I said above, vi is not easy to use. I'm going to post a link to a How To document, to help you with vi.
Spend a few minutes and look at the document. You need to be able to Open a file, change modes, enter text and save the file. There are instructions for other, more complex editing tasks, you can by pass them for now. See if you can enter the data, as I posted, and save the file in the directory you changed into. It needs to be there so udev can read it.
This, I think is the best way for you to edit the file. I only use vi when there is no other choice. I'm sure there is some editor on your system that is easier. You can look into that when you are not fighting with some problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.