Hint, don't make a guess or comment if you do not know. there are plenty
of examples of this already on the internet.
There are also plenty of examples of questions where the poster fails to
provide the distro name and/or release version, or doesn't ask a full
question in the body of the message.
With that in mind, you could try:
vi
vim
joe
nano
ed
It all depends on what you had installed prior to borking your system.
--
John
No Microsoft, Apple, AT&T, Novell, Trend Micro, nor Ford products were used in the preparation or transmission of this message.
The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.
> In witness thereof, terryc stated:
>> Is there any and what is it?
>
> www.debian.org/doc/manuals/en/reference.pdf - read chapter 11.
>
>> Hint, don't make a guess or comment if you do not know. there are
>> plenty of examples of this already on the internet.
>
> Hint: it's a bad idea to be a beggar and chooser.
Hint 1, if you don't know wtf you are talking about, then don't.
Hint 2, being able to enter google in a browser doesn't count as knowing
wtf you are talking about.
What have you tried so far?
--
Jimmy Johnson
Registered Linux User #380263
vi or nano
> terryc wrote:
>> Is there any and what is it?
>>
>> Hint, don't make a guess or comment if you do not know. there are
>> plenty of examples of this already on the internet.
>
>
> What have you tried so far?
Tried all the ones that were loaded on my system. The "gotcha" devil in
this question is the situation; "rescue mode".
> Obviously you didn't read TFM.
It isn't in TFM. Have you ever read TFM? Noticed how old it is?
> I don't use a kill file, but you are a
> whiner of top level.
I've paid my dues.
> Plus, I've never seen anyone as inept as you are
> using a very simple OS.
That is where you are deluded. Linux is definitely not a simple OS
anymore.
> Yet, as regarding a kill file, I will choose to
> ignore you.
Starting tomorrow no doubt? {:-)
> I've never seen a singular post by you complimenting Linux
> or Debian ... you trolling boob.
I take it you don't know the answer either.
I used the rescue mode once to setup grub, so I don't know what tools
are available, just a guess, you will probably have to chroot into your
existing system.
He asked which ones you had tried - just a little clue, he does have your
computer in front of him so how would he know which ones you have tried.
--
Neil
reverse ra and delete l
Linux user 335851
Surely the obvious ones are vi and nano? Try those and see.
>> Tried all the ones that were loaded on my system. The "gotcha" devil in
>> this question is the situation; "rescue mode".
>
>
> I used the rescue mode once to setup grub, so I don't know what tools
> are available, just a guess, you will probably have to chroot into your
> existing system.
That isn't the issue. It is when you need to change a file such as /boot/
grub/menu.lst or /etc/fstab, or similar, none of the common editors will
run because of "environmental" constraints.
In the past, I've sometimes been able to grep files, but that requires
the lines you need to be already working in the file.
> In witness thereof, mechanic stated:
>>
>> Surely the obvious ones are vi and nano? Try those and see.
>
> ed and nano are default on my minimal Lenny install (/bin).
If you want politeness and respect, why don't you try them and see for
yourself, then report back. BTDT, you learn.
> In the past, I've sometimes been able to grep files, but that requires
> the lines you need to be already working in the file.
If the lines need changing, then use /bin/sed to make the corrections,
directing the output to a temporary file file.TMP.
Then move the original to a file.SAV and finally move your file.TMP to file.