Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I'm definitely struggling through the setup of Backtrack. I'm also
learning a lot so it can't be all bad right? I'm currently at this instructional step:
Run the bootinst.sh script contained in the boot directory on the first partition (/mnt/sda1/boot/bootinst.sh). This will make the SD card/USB flash drive bootable.
I'm in terminal, at root :/# i type /mnt/sdb1/boot/bootinst.sh and am advised no such file or directory
Well, in the File System I can browse the partition and the bootinst.sh file is located in the boot folder where it should be.
I'm stuck, the sdb1 partition is Fat16 as required, it contains the boot folder with all the files, so i guess i'm not mounting this partition properly, so the computer can't get to the file?
Last edited by gordon__1; 01-14-2008 at 11:42 PM.
Reason: issue resolved
So, there is the actual fix, but how is that going to help anybody else? How about telling us why it worked? If you don't know, then maybe we can help you figure it out.
Are you trying to say that you learned that merely making a script executable isn't enough; you must also either have it in your $PATH, or call it w/ its path included in the name? No, you said you tried
Code:
/mnt/sda1/boot/bootinst.sh
Was it instead that bootinst.sh only worked when it was run from its own directory? If that's so, did you actually run
The problem was caused because I was having difficulty changing over to the USB drive in Terminal. It turns out i was not in the correct directory and once I was, the command worked. I've been working my way through Ubuntu, eeexubuntu, BackTrack3 and my new ASUS eee computer. I'm self taught and have made a lot of progress, there's definitely a learning curve.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.