Moved, not a BT bug.
This is probably one of the weirdest bugs I've seen, but I think I'm going to try and post it to see what people have to say.
I've been making a usb boot stick with my most commonly used tools. It uses grub4dos to boot and then presents me with a list of the tools on the drive.
Both windows 7 setup and backtrack exist on this drive.
One of the things that windows uses to boot is a folder called "sources". When this folder exists Backtrack refuses to mount the Root fs. It ends up just sitting there clueless. (Actually, I get a message that says "[sda] Assuming Drive Cache: write through". Thats not really an error though...).
When I rename the folder to "Sources_" backtrack decides to work again.
WTF? Is there some sort of code asking the kernel to look in the sources folder for something?
Here is the code I'm using for my grub4dos boot menu.
title Start BackTrack 4\nSecurity Tools
configfile /boot/grub/menu.lst
title Windows 7 Setup x86 + x64
find --set-root /bootmgr
chainloader /bootmgr
Any Suggestions?
Moved, not a BT bug.
Oh, so *THIS* is where the initial thread went. Awesome, Thanks for letting me know in that entirely unnecessary and nasty PM.
Also, Yes, this is a back track bug. It's a bug in the initial ramdisk and if you think its not I would absolutely *LOVE* some additional information on this.
Last edited by Coniferous; 06-13-2010 at 09:17 PM.
Again this is not a BT bug this potential bug in Grub4dos or windows but not in BT.
Further it is not my responsibility to tell you where your posts are.
If you wanted to know that bad then you would have used the search feature and locate posts with your name.
Even easier would have been to go to your user page and selecting either "find all posts" or "find all started threads", under your name.
Last edited by Archangel-Amael; 06-14-2010 at 05:59 PM.