login  home  contents  what's new  discussion  bug reports     help  links  subscribe  changes  refresh  edit

Edit detail for #266 Axiom binary for Fedora Core 4 does not start properly revision 1 of 4

1 2 3 4
Editor:
Time: 2007/11/17 22:18:09 GMT-8
Note: property change

changed:
-
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/AXIOMsys

[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 AXIOMsys

Would now start the processes.

exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/AXIOMsys

==========

What is the problem?

Regards, Alejandro Jakubi

From AlejandroJakubi Wed Feb 8 14:21:48 -0600 2006
From: Alejandro Jakubi
Date: Wed, 08 Feb 2006 14:21:48 -0600
Subject: 
Message-ID: <20060208142148-0600@wiki.axiom-developer.org>



From root Wed Feb 8 19:08:43 -0600 2006
From: root
Date: Wed, 08 Feb 2006 19:08:43 -0600
Subject: [#266 Axiom binary for Fedora Core 4 does not	start properly] (new)
Message-ID: <200602090156.k191uvZ15289@localhost.localdomain>
In-Reply-To: <20060208140835-0600@wiki.axiom-developer.org>
	(mathaction@axiom-developer.org)

My best guess is that you have SELinux enabled. As root try:

echo 0 >/proc/sys/kernel/randomize_va_space

and see if that fixes the problem

Tim


From AlejandroJakubi Wed Feb 8 23:24:30 -0600 2006
From: Alejandro Jakubi
Date: Wed, 08 Feb 2006 23:24:30 -0600
Subject: 
Message-ID: <20060208232430-0600@wiki.axiom-developer.org>

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

From root Wed Feb 8 23:45:16 -0600 2006
From: root
Date: Wed, 08 Feb 2006 23:45:16 -0600
Subject: [#266 Axiom binary for Fedora Core 4 does not	start properly]
Message-ID: <200602090633.k196XQl15359@localhost.localdomain>
In-Reply-To: <20060208232430-0600@wiki.axiom-developer.org>
	(mathaction@axiom-developer.org)

> 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


From AlejandroJakubi Thu Feb 9 09:48:47 -0600 2006
From: Alejandro Jakubi
Date: Thu, 09 Feb 2006 09:48:47 -0600
Subject: 
Message-ID: <20060209094847-0600@wiki.axiom-developer.org>

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

From unknown Sun May 14 14:01:09 -0500 2006
From: unknown
Date: Sun, 14 May 2006 14:01:09 -0500
Subject: $#
Message-ID: <20060514140109-0500@wiki.axiom-developer.org>

Category: Axiom on Linux => building Axiom from source 
Severity: serious => minor 
Status: open => duplicate 


From greg Sun May 14 14:31:17 -0500 2006
From: greg
Date: Sun, 14 May 2006 14:31:17 -0500
Subject: property change
Message-ID: <20060514143117-0500@wiki.axiom-developer.org>

Category: building Axiom from source => Axiom on Linux 
Severity: minor => serious 
Status: duplicate => open 


Submitted by : (unknown) at: 2007-11-17T22:18:09-08:00 (17 years ago)
Name :
Axiom Version :
Category : Severity : Status :
Optional subject :  
Optional comment :

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/AXIOMsys?

[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 AXIOMsys?

Would now start the processes.

exec /usr/local/axiom/mnt/linux/bin/sman -ws /usr/local/axiom/mnt/linux/bin/AXIOMsys?

==========

What is the problem?

Regards, Alejandro Jakubi

... --Alejandro Jakubi, Wed, 08 Feb 2006 14:21:48 -0600 reply

[#266 Axiom binary for Fedora Core 4 does not start properly]? (new) --root, Wed, 08 Feb 2006 19:08:43 -0600 reply
My best guess is that you have SELinux? enabled. As root try:

echo 0 >/proc/sys/kernel/randomize_va_space

and see if that fixes the problem

Tim

... --Alejandro Jakubi, Wed, 08 Feb 2006 23:24:30 -0600 reply
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

[#266 Axiom binary for Fedora Core 4 does not start properly]? --root, Wed, 08 Feb 2006 23:45:16 -0600 reply
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

... --Alejandro Jakubi, Thu, 09 Feb 2006 09:48:47 -0600 reply
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

property change --greg, Sun, 14 May 2006 14:31:17 -0500 reply
Category: building Axiom from source => Axiom on Linux Severity: minor => serious Status: duplicate => open