Linux - Software This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
09-29-2004, 10:57 PM
|
#1
|
LQ Newbie
Registered: Jul 2003
Location: Santa Barbara CA
Distribution: Slackware and Fedora
Posts: 19
Rep:
|
Using Vi, getting "blkopen's read failed" error
Hi,
I'm trying to edit files using vi, but getting the following error:
Code:
bash-2.05b$ vi .bashrc
blkopen's read failed
if I try editing the same file as root, there is no problem.
Here's an ls -la of .bashrc (this isn't limited to just this file, but any I try to edit with this user.)
Code:
bash-2.05b$ ls -la .bashrc
-rwx--x--x 1 sartre users 195 Aug 30 08:23 .bashrc
Any help is greatly appreciated, as google isn't helping much.
|
|
|
09-29-2004, 11:28 PM
|
#2
|
Senior Member
Registered: Sep 2004
Location: Savannah, GA
Distribution: Ubuntu, Gentoo, Mythbuntu, ClarkConnect
Posts: 1,154
Rep:
|
what's your username?
(not a vi user, the error is slightly cryptic to me)
|
|
|
09-29-2004, 11:41 PM
|
#3
|
LQ Newbie
Registered: Jul 2003
Location: Santa Barbara CA
Distribution: Slackware and Fedora
Posts: 19
Original Poster
Rep:
|
My username is sartre.
Some more troubleshooting on my end turned up a couple of things:
/usr/bin/vi is a link to elvis
I'm able to edit files using joe or vim, just not elvis .
|
|
|
09-30-2004, 02:05 AM
|
#4
|
Member
Registered: Sep 2004
Distribution: OpenSuSe
Posts: 153
Rep:
|
Is elvis an editor... (there are so many of them)...
Anyway, as root, when you issue this command "which vi", is "/usr/bin/vi" returned?
If answer is yes, try checking whether there is any .elvisrc or something like that for root & try copying that...
If the answer is no, then root is using "vi" in a differnt directory which evidently is working. Create a softlink/alias to that & invoke...
HTH.
|
|
|
09-30-2004, 03:39 PM
|
#5
|
LQ Newbie
Registered: Jul 2003
Location: Santa Barbara CA
Distribution: Slackware and Fedora
Posts: 19
Original Poster
Rep:
|
I pointed /usr/bin/vi to /usr/bin/vim and all is right with the world.
I'd like to know what the specific error means...
anyways, thanks for the help.
|
|
|
10-25-2004, 08:50 PM
|
#6
|
LQ Newbie
Registered: Oct 2004
Posts: 1
Rep:
|
I just had the same problem, so I found your post through a google search.
I think the reason why you got that error was b/c you ran out of space in /var (at least that was my problem).
-- Val
|
|
|
10-27-2004, 01:40 AM
|
#7
|
LQ Newbie
Registered: Jul 2003
Location: Santa Barbara CA
Distribution: Slackware and Fedora
Posts: 19
Original Poster
Rep:
|
Thanks vace, that looks like it was it. A little housecleaning fixed it.
|
|
|
All times are GMT -5. The time now is 10:31 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|