Re: help my bash is gone
Amos Shapira wrote: On 10/31/05, Aaron [EMAIL PROTECTED] wrote: Hi all, I have this strange behaviour that when I open a new term session or even in an existing term sesstion I will execute a common command such as ls or cd and the shell returns command not found. usually I can close cd command not found?? cd is an internal shell command (doesn't make sense to run it in a separate process). Are you sure that's what happened? What's the exact error message? It should be something like -bash: exact commandname: command not found Any other format might mean you are not really running bash, or that bash is not really seeing the command you typed (e.g. bad aliases, bad readline library, problems with keyboard/X/tty driver, etc.) And what's a term session? Do you mean an X terminal, ssh/telnet from other machine, or a VC (text mode)? = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
On Mon, 2005-10-31 at 09:54 +0200, Amit Aronovitch wrote: Amos Shapira wrote: On 10/31/05, Aaron [EMAIL PROTECTED] wrote: Hi all, I have this strange behaviour that when I open a new term session or even in an existing term sesstion I will execute a common command such as ls or cd and the shell returns command not found. usually I can close cd command not found?? cd is an internal shell command (doesn't make sense to run it in a separate process). Are you sure that's what happened? seperate process? What's the exact error message? It should be something like -bash: exact commandname: command not found -bash: ls:command not found was from ctrl alt F2 but the same thing on term windows I us konsole if it matters It happens randomly and often after time when I open a new term. Aaron Any other format might mean you are not really running bash, or that bash is not really seeing the command you typed (e.g. bad aliases, bad readline library, problems with keyboard/X/tty driver, etc.) And what's a term session? Do you mean an X terminal, ssh/telnet from other machine, or a VC (text mode)? = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
RE: help my bash is gone
iirc, something very similar happened to me a few days before my hard disk died. if i were you, i'd backup my hard disk completely now. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Aaron Sent: Mon, October 31, 2005 2:35 AM To: linux-il@linux.org.il Subject: help my bash is gone Hi all, I have this strange behaviour that when I open a new term session or even in an existing term sesstion I will execute a common command such as ls or cd and the shell returns command not found. usually I can close that session and open another and things work again, sometimes I must log out and back in and sometimes (rarely ) that doesn't help. I am using demudi which is debian and this once happened while I was having other problems and I was forced to reinstall since I couldn't use the command line Any thoughts on what might be causing this very strange behaviour would be most appreciated. Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] *** This email message and any attachments thereto are intended only for use by the addressee(s) named above, and may contain legally privileged and/or confidential information. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the [EMAIL PROTECTED] and destroy the original message. *** To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
On 10/31/05, Aaron [EMAIL PROTECTED] wrote: -bash: ls:command not found was from ctrl alt F2 but the same thing on term windows I us konsole if it matters It happens randomly and often after time when I open a new term. 1. what does dmesg show you right after this? Do you see any disk read errors? 2. Take Neta's advise and backup your disk NOW. 3. Maybe I'm jumping into conclusion but try running some SMART disk tests with smartctl(8) (see the section about the -t option). Apparently an offline test on my Maxtor disk helped it heal its bad blocks (but I still switched to a new disk, use the old disk as expandable don't-care-much-if-it-fails area). Aaron --Amos To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
no dmeg gave not errors On Mon, 2005-10-31 at 22:08 +1000, Amos Shapira wrote: On 10/31/05, Aaron [EMAIL PROTECTED] wrote: -bash: ls:command not found was from ctrl alt F2 but the same thing on term windows I us konsole if it matters It happens randomly and often after time when I open a new term. 1. what does dmesg show you right after this? Do you see any disk read errors? 2. Take Neta's advise and backup your disk NOW. 3. Maybe I'm jumping into conclusion but try running some SMART disk tests with smartctl(8) (see the section about the -t option). Apparently an offline test on my Maxtor disk helped it heal its bad blocks (but I still switched to a new disk, use the old disk as expandable don't-care-much-if-it-fails area). Aaron --Amos Unpacking smartmontools (from .../smartmontools_5.33+5.34cvs20050802-3_i386.deb) ... Setting up smartmontools (5.33+5.34cvs20050802-3) ... Not starting S.M.A.R.T. daemon smartd, disabled via /etc/default/smartmontools demudi:/usr/src# hmn Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
The problem with this issue, is that there is a wide range of possible causes to this problem, spanning a large 'diagnosis tree'. This makes it hard to diagnose by iterative mail questions. I'll try to ask enough questions to cover the more reasonable? causes. Aaron wrote: cd command not found?? cd is an internal shell command (doesn't make sense to run it in a separate process). Are you sure that's what happened? seperate process? I think what Amos means is that for cd it's a different matter than e.g. for ls. When you type ls, bash searches for the command on your path, and if found runs it in a subprocess. If your path, or the disk containing the executable (normally /bin/ls) is broken, you get the message you got below. However since cd is an internal command, bash should run it directly (there is no 'cd' executable, it's the bash executable that does the job), so we'd be very surprised if you see similiar message for the 'cd' command too. Were you just giving an example or did you actually see a '-bash: cd: command not found'? I can hardly imagine how this could happen - unless the bash executable itself is broken. What's the exact error message? It should be something like -bash: exact commandname: command not found -bash: ls:command not found OK, so we know it's bash, and we know it knows you typed ls (unless there are some mysterious unprintables hidden over there), rules out a few exotic possibilities. What about if you try explicit path: /bin/ls ? Can you access /bin at all? I would have said try ls'ing it, but since you don't have ls... what happens if you type /bitab? does it complete? if yes, try another tab to see what's there... If there is a working /bin/ls, then it's your PATH. Were the echo $PATH results you mentioned before done from a working terminal? If yes, try from a non-working one (echo, like cd, is an internal command - if it does not work, either you have a bad alias or your bash executable is bad). If you see no /bin or no /bin/ls, indeed the most probable cause would be a bad disk/ bad file-system. When this happens, try switching to another (working) shell, and see if you can access /bin/ls from there. If you can run /bin/df, try /bin/df / and /bin/df /bin. It might also be related to user permissions (maybe these shells are opened under some special user, that does not have read or exec perms to the file) - try running /usr/bin/id ... oops - this would probably not be available too - so try locating this shell by carefully examining the output of ps -ef from another terminal - note the user id. One more general diagnosis tool - if you do locate the shell's process from another terminal, you can use 'strace -p process number', then go back to the bad term and type /bin/ls -ld /bin/ls to see the syscalls bash does when looking for ls. Yet another possibility, is that for some reason the shell or the terminal is run chroot(8)'ed to some other place - I guess this one is too far fetched for now was from ctrl alt F2 but the same thing on term windows I us konsole if it matters This would have helped to further diagnose had you given a different answer to my other question (the exact error message). As it stands it probably does not matter. It happens randomly and often after time when I open a new term. Aaron after time - does that mean that it works ok for a while, then the same shell stops recognizing commands? Or do you simply mean that you open a new shell after some time, and the *new* shell is the one that does not work? Or - is it that they both stop working, but this does not happen unless you open a new terminal. One more useful technique you can try, especially if you suspect PATH is being corruped, is adding debug printings in initialization scripts - e.g. /etc/profile /etc/bash.bashrc, ~/.bash_profile and ~/.bashrc (sometimes it's the initializations scripts that fail, corrupting your PATH on the way). But do make sure you remember to remove them once your'e done experimenting... = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
On Tue, 2005-11-01 at 03:13 +0200, Amit Aronovitch wrote: The problem with this issue, is that there is a wide range of possible causes to this problem, spanning a large 'diagnosis tree'. This makes it hard to diagnose by iterative mail questions. I'll try to ask enough questions to cover the more reasonable? causes. Aaron wrote: cd command not found?? cd is an internal shell command (doesn't make sense to run it in a separate process). Are you sure that's what happened? seperate process? I think what Amos means is that for cd it's a different matter than e.g. for ls. When you type ls, bash searches for the command on your path, and if found runs it in a subprocess. If your path, or the disk containing the executable (normally /bin/ls) is broken, you get the message you got below. However since cd is an internal command, bash should run it directly (there is no 'cd' executable, it's the bash executable that does the job), so we'd be very surprised if you see similiar message for the 'cd' command too. Were you just giving an example or did you actually see a '-bash: cd: command not found'? I can hardly imagine how this could happen - unless the bash executable itself is broken. What's the exact error message? It should be something like -bash: exact commandname: command not found -bash: ls:command not found OK, so we know it's bash, and we know it knows you typed ls (unless there are some mysterious unprintables hidden over there), rules out a few exotic possibilities. What about if you try explicit path: /bin/ls ? Can you access /bin at all? I would have said try ls'ing it, but since you don't have ls... what happens if you type /bitab? does it complete? if yes, try another tab to see what's there... If there is a working /bin/ls, then it's your PATH. Were the echo $PATH results you mentioned before done from a working terminal? If yes, try from a non-working one (echo, like cd, is an internal command - if it does not work, either you have a bad alias or your bash executable is bad). If you see no /bin or no /bin/ls, indeed the most probable cause would be a bad disk/ bad file-system. When this happens, try switching to another (working) shell, and see if you can access /bin/ls from there. If you can run /bin/df, try /bin/df / and /bin/df /bin. It might also be related to user permissions (maybe these shells are opened under some special user, that does not have read or exec perms to the file) - try running /usr/bin/id ... oops - this would probably not be available too - so try locating this shell by carefully examining the output of ps -ef from another terminal - note the user id. One more general diagnosis tool - if you do locate the shell's process from another terminal, you can use 'strace -p process number', then go back to the bad term and type /bin/ls -ld /bin/ls to see the syscalls bash does when looking for ls. Yet another possibility, is that for some reason the shell or the terminal is run chroot(8)'ed to some other place - I guess this one is too far fetched for now was from ctrl alt F2 but the same thing on term windows I us konsole if it matters This would have helped to further diagnose had you given a different answer to my other question (the exact error message). As it stands it probably does not matter. It happens randomly and often after time when I open a new term. Aaron after time - does that mean that it works ok for a while, then the same shell stops recognizing commands? yes it means it was working and pitom all of a sudden it stopped. Or do you simply mean that you open a new shell after some time, and the *new* shell is the one that does not work? Or - is it that they both stop working, but this does not happen unless you open a new terminal. One more useful technique you can try, especially if you suspect PATH is being corruped, is adding debug printings in initialization scripts - e.g. /etc/profile /etc/bash.bashrc, ~/.bash_profile and ~/.bashrc (sometimes it's the initializations scripts that fail, corrupting your PATH on the way). But do make sure you remember to remove them once your'e done experimenting... Thanks for the suggestions I will use all the above the next time it happens Aaron = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
On 10/31/05, Aaron [EMAIL PROTECTED] wrote: Hi all, I have this strange behaviour that when I open a new term session or even in an existing term sesstion I will execute a common command such as ls or cd and the shell returns command not found. usually I can close cd command not found?? cd is an internal shell command (doesn't make sense to run it in a separate process). Are you sure that's what happened? What's your PATH (echo $PATH)? that session and open another and things work again, sometimes I must log out and back in and sometimes (rarely ) that doesn't help. I am using demudi which is debian and this once happened while I was having other problems and I was forced to reinstall since I couldn't use the command line I'd reckon it's a favourite passtime for real linux users to try to get out of any broken situation without having to (in degrading order of preferences) kill-program/exit-shell/logout/kill-xserver (ctrl-backspace)/reboot/reinstall. I think it's a very instructive experience to try to achieve these goals (what is a learned for fun one day can come up as a real session-saver on another, /usr/bin/reset might turn out to be more useful than you would normally expect :). Any thoughts on what might be causing this very strange behaviour would be most appreciated. Messed up environment (variables), trojans, bad disk blocks, broken packages installed come up to my mind right now. Try looking in dmesg(8) and /var/log/messages* for odd kernel messages. Is this a private personal computer or some public/lab/family box used by others? --Amos To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
On Mon, 2005-10-31 at 11:56 +1100, Amos Shapira wrote: On 10/31/05, Aaron [EMAIL PROTECTED] wrote: Hi all, I have this strange behaviour that when I open a new term session or even in an existing term sesstion I will execute a common command such as ls or cd and the shell returns command not found. usually I can close cd command not found?? cd is an internal shell command (doesn't make sense to run it in a separate process). Are you sure that's what happened? What's your PATH (echo $PATH)? demudi linux $ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games demudi linux $ I'd reckon it's a favourite passtime for real linux users to try to get out of any broken situation without having to (in degrading order of preferences) kill-program/exit-shell/logout/kill-xserver (ctrl-backspace)/reboot/reinstall. I think it's a very instructive experience to try to achieve these goals (what is a learned for fun one day can come up as a real session-saver on another, /usr/bin/reset might turn out to be more useful than you would normally expect :). not sure I get your point, I do know that expeinced users don't do what I do, but search for the cause of the problem and a solution. I usually panic and try the above options... Any thoughts on what might be causing this very strange behaviour would be most appreciated. Messed up environment (variables), trojans, bad disk blocks, broken packages installed come up to my mind right now. Try looking in dmesg(8) and /var/log/messages* for odd kernel messages. from dmesg: clip-- sda: assuming drive cache: write through usb 1-1.2: USB disconnect, address 15 scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device sda : READ CAPACITY failed. sda : status=0, message=00, host=1, driver=04 sda : sense not available. scsi7 (0:0): rejecting I/O to dead device sda: Write Protect is off sda: Mode Sense: 00 00 00 00 sda: assuming drive cache: write through /dev/scsi/host7/bus0/target0/lun0:3scsi7 (0:0): rejecting I/O to dead device Buffer I/O error on device sda, logical block 0 scsi7 (0:0): rejecting I/O to dead device Buffer I/O error on device sda, logical block 0 unable to read partition table scsi7 (0:0): rejecting I/O to dead device Buffer I/O error on device sda, logical block 0 Buffer I/O error on device sda, logical block 1 Buffer I/O error on device sda, logical block 2 Buffer I/O error on device sda, logical block 3 Buffer I/O error on device sda, logical block 4 Buffer I/O error on device sda, logical block 5 Buffer I/O error on device sda, logical block 6 Buffer I/O error on device sda, logical block 7 scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7 (0:0): rejecting I/O to dead device scsi7
Re: help my bash is gone
On 10/31/05, Aaron [EMAIL PROTECTED] wrote: On Mon, 2005-10-31 at 11:56 +1100, Amos Shapira wrote: What's your PATH (echo $PATH)? demudi linux $ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games demudi linux $ And you get command not found when doing ls with this path? Is ls aliased to something? I'd reckon it's a favourite passtime for real linux users to try to get out of any broken situation without having to (in degrading order of preferences) kill-program/exit-shell/logout/kill-xserver (ctrl-backspace)/reboot/reinstall. I think it's a very instructive experience to try to achieve these goals (what is a learned for fun one day can come up as a real session-saver on another, /usr/bin/reset might turn out to be more useful than you would normally expect :). not sure I get your point, I do know that expeinced users don't do what I do, but search for the cause of the problem and a solution. I usually panic and try the above options... My point is that if you get to it - it's worth trying to dig and find answers to these problems so next time they come around you are ready to smuck them in the face once and for all, otherwise you'll never become an experienced linux user (or you might become experienced linux installer :). scsi7 (0:0): rejecting I/O to dead device my cdr started doing this after ram upgrade Looks like some device-sensing daemon probing the cd for a media, not too worrying (and you could have clipped the identical lines in the message). ---clip--- Attached scsi removable disk sda at scsi9, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi9, channel 0, id 0, lun 0, type 0 usb-storage: device scan complete EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended Have you crashed your system lately? Have you executed fsck afterward? Try taking the system down to single-user mode (remember - try to avoid a full reboot) unmount and fsck all filesystems except for the root filesystem. Actually - if you are not sure (are you?) then reboot and check whether there are such warnings about your root filesystem too. Consider moving to ext3 (no need to reformat the filesystem, I've never done this myself but I read it's just a matter of running tune2fs -j device file and updating the filesystem type in /etc/fstab) printk: 77 messages suppressed. UDP: short packet: From 213.97.234.10:39074 35764/43 to 192.117.110.160:356 Have you setup a firewall on your computer? Have you taken down all unnecessary services (this is apparently unrelated to your problem but still)? Cheers, --Amos To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
On Mon, 2005-10-31 at 13:58 +1100, Amos Shapira wrote: On 10/31/05, Aaron [EMAIL PROTECTED] wrote: On Mon, 2005-10-31 at 11:56 +1100, Amos Shapira wrote: What's your PATH (echo $PATH)? demudi linux $ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games demudi linux $ And you get command not found when doing ls with this path? Is ls aliased to something? I'd reckon it's a favourite passtime for real linux users to try to get out of any broken situation without having to (in degrading order of preferences) kill-program/exit-shell/logout/kill-xserver (ctrl-backspace)/reboot/reinstall. I think it's a very instructive experience to try to achieve these goals (what is a learned for fun one day can come up as a real session-saver on another, /usr/bin/reset might turn out to be more useful than you would normally expect :). I didn't catch this the first time, but did a man reset and now I see what you mean :) thanks aaron not sure I get your point, I do know that expeinced users don't do what I do, but search for the cause of the problem and a solution. I usually panic and try the above options... My point is that if you get to it - it's worth trying to dig and find answers to these problems so next time they come around you are ready to smuck them in the face once and for all, otherwise you'll never become an experienced linux user (or you might become experienced linux installer :). the latter is still more the case although less and less. scsi7 (0:0): rejecting I/O to dead device my cdr started doing this after ram upgrade Looks like some device-sensing daemon probing the cd for a media, not too worrying (and you could have clipped the identical lines in the message). ---clip--- Attached scsi removable disk sda at scsi9, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi9, channel 0, id 0, lun 0, type 0 usb-storage: device scan complete EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended Have you crashed your system lately? it happens on occasion ie my ups broke and computers at home. Have you executed fsck afterward? no I use ext3 file system and thought the journalling was enough (truth to tell I couldn't figure out how to run it under ext3) Try taking the system down to single-user mode on redhat this was a simple matter I also keep forgetting how to go to single-user mode on debian. (remember - try to avoid a full reboot) unmount and fsck all filesystems except for the root filesystem. Actually - if you are not sure (are you?) then reboot and check whether there are such warnings about your root filesystem too. Consider moving to ext3 (no need to reformat the filesystem, I've never done this myself but I read it's just a matter of running tune2fs -j device file and updating the filesystem type in /etc/fstab) printk: 77 messages suppressed. UDP: short packet: From 213.97.234.10:39074 35764/43 to 192.117.110.160:356 Have you setup a firewall on your computer? Have you taken down all unnecessary services (this is apparently unrelated to your problem but still)? no I haven't set up a firewall and I have unnecessary services embarrassed sigh I will remove the extra junk and setup a firewall toda Aaron Cheers, --Amos = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: help my bash is gone
On 10/31/05, Aaron [EMAIL PROTECTED] wrote: On Mon, 2005-10-31 at 13:58 +1100, Amos Shapira wrote: And you get command not found when doing ls with this path? Is ls aliased to something? You haven't answered this question. I didn't catch this the first time, but did a man reset and now I see what you mean :) I might have bungled again in the way I phrased this - reset was just an small example of something that many people just close a shell where running the right command could let them keep it. experienced linux user (or you might become experienced linux installer :). the latter is still more the case although less and less. Good on you. EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended Have you crashed your system lately? it happens on occasion ie my ups broke and computers at home. You have a UPS? Have you though of connecting its signal to your computer so the system can shut down cleanly before the UPS runs out of juice? Have you executed fsck afterward? no I use ext3 file system and thought the journalling was enough (truth to tell I couldn't figure out how to run it under ext3) e2fsck - from the manual: e2fsck - check a Linux ext2/ext3 file system. The kernel message clearly recommands running fsck. Try taking the system down to single-user mode on redhat this was a simple matter I also keep forgetting how to go to single-user mode on debian. man init will teach you (and between you and me - it's init s). Have you setup a firewall on your computer? Have you taken down all unnecessary services (this is apparently unrelated to your problem but still)? no I haven't set up a firewall and I have unnecessary services embarrassed sigh I will remove the extra junk and setup a firewall Remember - you can install the most secure-*able* system in the world but if you don't configure it properly it's still not secure. --Amos To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
