MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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.
Distribution: open SUSE 11.0, Fedora 7 and Mandriva 2007
Posts: 1,662
Rep:
Mandriva's menu.lst problems'.
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.
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>"
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.
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????
Distribution: open SUSE 11.0, Fedora 7 and Mandriva 2007
Posts: 1,662
Original Poster
Rep:
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.
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.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.