|
|
|
last edited 4 years ago by test1 |
Edit detail for #266 Axiom binary for Fedora Core 4 does not start properly revision 4 of 4
| 1 2 3 4 | ||
|
Editor: test1
Time: 2020/03/08 16:45:53 GMT+0 |
||
| Note: | ||
changed: -exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/AXIOMsys exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/FRICASsys changed: --rwxr-xr-x 1 root root 13650944 Sep 5 23:20 AXIOMsys -rwxr-xr-x 1 root root 13650944 Sep 5 23:20 FRICASsys changed: -exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/AXIOMsys exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/FRICASsys
I have installed axiom-Sept2005-FC4-bin.tgz on Fedora Core 4 (in /usr/local), following the instructions in the download page, but execution of axiom does not produce any proper output. Ie it produces a pair of blank lines and closes again, returning the prompt to the console. On the other hand, axiom -h works.
Some variations occur, eg with option noclef it closes without blank lines, and with iw it opens an X term for a second and then it closes. And here some other ones:
=========
[root@localhost bin]?# axiom -nogo
Would now start the processes.
exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/FRICASsys
[root@localhost bin]?# ps aux | axiom
clef trying to get the initial terminal settings: Invalid argument
root@localhost bin]# axiom -list
AXIOM workspaces in $AXIOM/bin = /usr/local/axiom/mnt/linux/bin:
-rwxr-xr-x 1 root root 13650944 Sep 5 23:20 FRICASsys
Would now start the processes.
exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/FRICASsys
==========
What is the problem?
Regards, Alejandro Jakubi
echo 0 >/proc/sys/kernel/randomize_va_space
and see if that fixes the problem
Tim
Yes, SELinux? was enabled and enforced. This command did not solved the problem. Then I have disabled SELinux?, booted, axiom did not work yet, executed the command and axiom began working. Then I have set SELinux? to enabled again, booted with relabelling, and after execution of the command axiom does work, even with enforcing.Apparently I should call axiom from a script including this command.
Alejandro
Yes, SELinux? was enabled and enforced. This command did not solved the problem. Then I have disabled SELinux?, booted, axiom did not work yet, executed the command and axiom began working. Then I have set SELinux? to enabled again, booted with relabelling, and after execution of the command axiom does work, even with enforcing.
Apparently I should call axiom from a script including this command. i've asked someone who knows the SELinux? people to suggest that they use Lisp as a test case. the people who implemented the SELinux? routines don't seem to understand the way lisp systems work. every time they release a "new" SELinux? update they've broken yet another thing in Lisp.
at least it solved your problem.
t
In fact it is enough to execute the magic command once in the shell. Afterwards, axiom opens fine every time. So, I think, I should add this command to /etc/rc.d/rc.local.Alejandro
Category: Axiom on Linux => building Axiom from source Severity: serious => minor Status: open => duplicate Category: building Axiom from source => Axiom on Linux Severity: minor => serious Status: duplicate => open http://axiom-developer.org/axiom-website/download.html Status: open => closed