Mandriva's menu.lst problems'.

Gins · 01-09-2009, 01:34 PM

The following was written by CJS to my previous question.

Code:

This is just an idea, because I don't want to intrude on your excellent troubleshooting efforts, yancek; but it might help to see the output of meierfra's boot_info_script.txt in order to help pinpoint Gin's booting problem. If you are interested in running the script, Gins, how about downloading the "boot_info_script.txt" to your desktop, and then do the following as root user, but replace <username> with your username:
Code:
bash /home/<username>/Desktop/boot_info_script.txt
That will create a "RESULTS.txt" file in the same directory from where the script is run, namely your desktop; please copy/paste the contents of that file to your next post. That will help clarify your setup and hopefully what your booting problem might be.

http://www.linuxquestions.org/questi...428/page4.html

I do not how this works. It just went deep into the system and elicited all the details.

I believe it downloaded a script from some other source and elicited all the details.
These things are magic.

Could you tell me how it worked?

pixellany · 01-09-2009, 01:50 PM

Gins;

When I recommended starting a new thread, I did not mean that you should start one that requires us to go back and re-read the other one!!! When you start a new thread, it needs to stand on its own.

Please tell us exactly what your question is: In this case, this might mean that you should summarize the information you are referring to.

Example:
Suppose I'm struggling with SED (I do that a lot....

). I might logically start a new thread like this:

Quote:

In this thread <link>, they describe how SED addressing works. The discussion includes a new feature in which addressing can be used to access--eg--every third line. Can this be used in conjunction with the incremental addressing? eg sed '1,+~3<command>"

Gins · 01-09-2009, 02:18 PM

Thanks pixellany

The following is my question.

Our friend CJS asked me to click on 'boot info script.txt'

It downloaded a thread and penetrate into my system and elicited a .txt file.

I just clicked; it elicited a .txt file.

I don't know how that works.

pixellany · 01-09-2009, 02:32 PM

Quote:

Originally Posted by Gins

Thanks pixellany

The following is my question.

Our friend CJS asked me to click on 'boot info script.txt'

It downloaded a thread and penetrate into my system and elicited a .txt file.

I just clicked; it elicited a .txt file.

I don't know how that works.

OK--you are getting closer... Where do I get this script you are referring to?

Are you asking HOW the script creates a .txt file??? Or where it gets the data??

Gins · 01-09-2009, 02:39 PM

Pixellany wrote the following:

Are you asking HOW the script creates a .txt file??? Or where it gets the data??

1. How do I download it without doing any work? I mean it penetrated into the system and elicited a .txt file

2. How did it penetrated into the system?

Usually I have to write a script and execute it.

I have some knowledge of writing scripts.

To execute a script you should use the 'chmod' command to change the status.

This particular file did not ask any permission; just penetrated into the system.
__________________

pixellany · 01-09-2009, 02:48 PM

One more time---where did you get the script that is doing **whatever**. If someone cannot repeat what you are doing, then how are we supposed to help you????

What you need to do is post:

Where to get the script
Details of how you ran it---ie what exactly you did.

From your previous post:

Quote:

Our friend CJS asked me to click on 'boot info script.txt'
It downloaded a thread and penetrate into my system and elicited a .txt file.

Where do I find 'boot info script.txt'??????

Gins · 01-09-2009, 03:49 PM

Yes, I want to know the following:

1. Where to get the script
2. Details of how you ran it---ie what exactly you did.

pixellany · 01-09-2009, 06:13 PM

Gins;

I am afraid we may have a language barrier--or something.

You said that YOU did something with a script called "boot info script", and you described some things that happened. Now you are asking US where to get the script????

Maybe we should start over:

What is the original problem?
What have you tried?
What happened?
What is your current question?

Gins · 01-10-2009, 12:43 PM

pixellany

English is the lingua franca for the forum. You are a native English speaker. English is my second language. So it is impossible to draw a parallel between your English and my English. I speak some Russian and French too.

It is needless to say there are language barriers between us.

Let me start from scratch.

1] Could you tell me how to download the file in question?

If I could download it, I would ask the the rest later on.

ernie · 01-10-2009, 01:42 PM

Pixellany, I went back in Gins previous thread and found the link CJS provided to the script. You can get it ans see what it does if that is of any help.

pixellany · 01-10-2009, 02:46 PM

Well, there it is!!!

Click on the link and it opens in a browser window--at least on my machine. Save the file, set the executable permissions, and run it. (You probably have to run it as root.)

Note that the script includes some instructions at the beginning.

I will try it myself when I have time.

Gins · 01-10-2009, 03:23 PM

pixellany

1] Could you tell me how to download the file in question?

CJS · 01-10-2009, 03:25 PM

Just in case anyone is wondering, the "Boot Info Script" now has an official home at sourceforge.net:

https://sourceforge.net/projects/bootinfoscript/

We appreciate and welcome any and all constructive criticism or suggestions, because the author (meierfra) would like the make the script as useful as possible when it comes to booting issues. Gins, in case you are wondering, you can execute a script without first setting its executable bit by doing:

Code:

sudo bash boot_info_script.sh

That also runs the script as root, and that's basically how you previously ran the script.

Gins · 01-10-2009, 03:48 PM

I downloaded it for Mandriva 2009.

[ni@localhost Desktop]$ su root
Password:
[root@localhost Desktop]# ./boot_info_script.sh
bash: ./boot_info_script.sh: Permission denied
[root@localhost Desktop]#

Why didn't it work?

---------------------------------------------------------------

It is on the Desktop. As you see I have 3 files on the Desktop

[ni@localhost Desktop]$ ls
boot_info_script.sh

register.desktop

Buddahs_first_journey_to_SriLanka.jpg
[ni@localhost Desktop]$

------------------------------------------------------------------------------------------
[root@localhost Desktop]# file boot_info_script.sh
boot_info_script.sh: Bourne-Again shell script text executable
[root@localhost Desktop]#

I can't figure out the mistake I made. Probably I have a mental aberration as it is getting late here.

-----------------------------------------------------------------------------------
Yes, it worked.

[root@localhost Desktop]# sudo bash boot_info_script.sh
Finished. The results are in the file RESULTS.txt located in /home/ni/Desktop
[root@localhost Desktop]#

I have a question. It may be a silly question.
Why do I have to use the words 'sudo bash'?

In order to execute a script, we write './ name_of_the_script'

What is 'sudo bash'?
I must confess that there are many things which I have never learnt.

pixellany · 01-10-2009, 04:49 PM

You have to run that script as root.

You can switch to root using "su", or you can run individual commands using "sudo".

For details:
man su
man sudo

When you enter a command in Bash, it looks for a pathname in $PATH. To run the command in the current directory, you use "./command".

"." means "current directory"