| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
cannot launch "bash"
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 cannot launch "bash" - Oct. 3, '06, 5:34:57 PM
|
|
|
dnob700
Posts: 3
Joined: Dec. 3, '05,
Status: offline
|
hello,
I've just installed SFU on a new computer under windows XP Pro.
But I'm unable to install bash properly : following the method given on the website and nowhere but to a "core dump" message when I try to launch the newly installed bash (the rest of SFU seems to behave corectly).
Is this a known bug with a known solution ? I've found nothing related on the forum.
sincerely,
M.K.
|
|
|
|
|
RE: cannot launch "bash" - Oct. 3, '06, 7:13:17 PM
|
|
|
Rodney
Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Refer to the FAQ entry on DEP (entry 2.07) is the most likely answer.
|
|
|
|
|
RE: cannot launch "bash" - Oct. 4, '06, 3:58:32 AM
|
|
|
dnob700
Posts: 3
Joined: Dec. 3, '05,
Status: offline
|
thank you, that was part of the problem.
Now I can start bash, but I cannot launch any other programs from bash : all command like ls, vi, etc. end with the same error message "segmentation fault (core dumped)", while they are functionning correctly from another shell (ksh).
|
|
|
|
|
RE: cannot launch "bash" - Oct. 4, '06, 1:14:33 PM
|
|
|
Rodney
Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
This sounds like the same problem still (DEP) because those utilities (ls et al) are
all built with c89 rather than gcc and are thus not going to get nailed by DEP.
Neither are they going to SEGV (core dump).
It happened at least once before for one Forum member that they applied the change to the
boot.ini file, but left the previous directive behind. Thus there were two entries for noexecute.
What does your boot.ini file look like now? Can you quote the whole thing?
|
|
|
|
|
RE: cannot launch "bash" - Oct. 5, '06, 12:42:16 PM
|
|
|
dnob700
Posts: 3
Joined: Dec. 3, '05,
Status: offline
|
here is my bootloader file.
Should I clear the NoExecute option ?
I've also found in my BIOS setup an option to disable the "execute disable function". But I'm not sur that this hardware layer option has the same effect than the software one.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /fastdetect /NoExecute=OptIn
|
|
|
|
|
RE: cannot launch "bash" - Oct. 5, '06, 12:59:37 PM
|
|
|
Rodney
Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
You didn't follow the instructions in the FAQ. That's why it's not working.
You need to have "/Noexecute=AlwaysOff". That's what FAQ 2.07 has.
No other value to the noexecute option will work.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
