I agree totally. We shouldn't do anything to scare away people new to Pharo.
It's a hard enough sell as it is. This kind of thing only undermines my
advocacy.
Ben Coman wrote
> On Tue, 4 Dec 2018 at 02:07, Sven Van Caekenberghe <
> sven@
> > wrote:
>
>> Yes, I can confirm that it looks like /
On Tue, 4 Dec 2018 at 02:07, Sven Van Caekenberghe wrote:
> Yes, I can confirm that it looks like /etc/security/limits.d settings are
> not honoured inside an LXC/LXD container on Linux. I am not sure that there
> is a way around this, as it seems that such limits are part of the
> technology use
Yes, I can confirm that it looks like /etc/security/limits.d settings are not
honoured inside an LXC/LXD container on Linux. I am not sure that there is a
way around this, as it seems that such limits are part of the technology used
to implement containers (and hence it might conflict with them
I didn’t read much of this thread but the VPS might give a hint. If you are in
a virtualized server and you want to modify kernel parameters the underlying
host needs to allow that.
Norbert
> Am 03.12.2018 um 16:55 schrieb horrido :
>
> Yes, I did. I even rebooted Ubuntu.
>
> Given that thi
Yes, I have a normal account. And, yes, the ownership is root:root.
Sven Van Caekenberghe-2 wrote
> sven@ubuntu:~/Documents/pharo7$ uname -a
> Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018
> x86_64 x86_64 x86_64 GNU/Linux
>
> sven@ubuntu:~/Documents/pharo7$ cat /etc/
sven@ubuntu:~/Documents/pharo7$ uname -a
Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
sven@ubuntu:~/Documents/pharo7$ cat /etc/issue
Ubuntu 18.04.1 LTS
sven@ubuntu:~/Documents/pharo7$ id
uid=1000(sven) gid=1000(sven)
groups=1000(sven)
Yes, I did. I even rebooted Ubuntu.
Given that this problem occurs for both Debian and Ubuntu, there must be
some commonality that hasn't been documented.
Ben Coman wrote
> At https://linux.die.net/man/5/limits.conf
> I read "note that all limit settings are set per login."
> You haven't mentio
At https://linux.die.net/man/5/limits.conf
I read "note that all limit settings are set per login."
You haven't mentioned whether you logged out and back in again?
cheers -ben
On Mon, 3 Dec 2018 at 23:17, horrido wrote:
> I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the step
I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the steps to
arrive at Pharo installation. I'm still having the same problem:
pthread_setschedparam failed.
Here's my /etc/security/limits.d/pharo.conf:
* hard rtprio 2
* soft rtprio 2
Sven Van Caekenberghe-2 wrote
>> On 2 Dec 20
That is strange. Can you post your "/etc/security/limits.d/pharo.conf" file?
cheers -ben
On Mon, 3 Dec 2018 at 01:42, horrido wrote:
> Bizarre. I've created a new VirtualBox image of Debian and now this
> solution
> no longer works! I'm still getting the thread priority warning. So this
> solut
> On 2 Dec 2018, at 18:40, horrido wrote:
>
> Bizarre. I've created a new VirtualBox image of Debian and now this solution
> no longer works! I'm still getting the thread priority warning. So this
> solution appears to be unreliable.
Why use Debian (not that it is bad, it is just a bit more t
Bizarre. I've created a new VirtualBox image of Debian and now this solution
no longer works! I'm still getting the thread priority warning. So this
solution appears to be unreliable.
On Fri, 23 Nov 2018 at 04:02, horrido wrote:
> Okay, I've resolved everything. First, the r
If you mean by removing the '-m32' flag, it didn't work for me. I can't
remember the error messages.
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
On Wed, Nov 21, 2018 at 07:06:08PM -0500, Richard Kenneth Eng wrote:
> I'm creating the competition website using Pharo and Teapot. For
> encryption, I'm using Pierce Ng's PasswordCrypt, which requires a 32-bit C
> library. This means I must run 32-bit Pharo.
PasswordCrypt can be built as a 64-bit
This works! Everything is copacetic.
On Fri, 23 Nov 2018 at 04:02, horrido wrote:
> Okay, I've resolved everything. First, the reason why I'm getting the
> 'pthread_setschedparam failed' error when I run Pharo under Debian is
> because it must be run as 'root'! Don't ask me w
By the way, after looking at password hashing algorithms and what the experts
say about them, I've decided to implement an interface to the Argon2 library
(see https://password-hashing.net/argon2-specs.pdf for a whitepaper). The
algorithm is designed to be far more resistant against cracking than m
--- Begin Message ---
On Fri, 23 Nov 2018 at 04:02, horrido wrote:
> Okay, I've resolved everything. First, the reason why I'm getting the
> 'pthread_setschedparam failed' error when I run Pharo under Debian is
> because it must be run as 'root'! Don't ask me why, but that's the reason
> why Phar
It can't find the display drivers since the appropriate 32 bit libraries
are missing. Use the 'ldd' command on the VM binary and on the shared
libraries in its directory to find out which ones you're missing.
Cheers,
Hans-Martin
Am 22. November 2018 4:22:19 nachm. schrieb horrido
:
I'm run
Okay, I've resolved everything. First, the reason why I'm getting the
'pthread_setschedparam failed' error when I run Pharo under Debian is
because it must be run as 'root'! Don't ask me why, but that's the reason
why Pharo can't set thread priorities. (This wasn't an issue under Ubuntu
Server – go
On Thu, 22 Nov 2018 at 23:22, horrido wrote:
> I'm running 64-bit Debian in a VirtualBox image on my Mac.
>
> When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I
> get the error message below. What's the difference??? Why can one find the
> display driver and the other can'
Using Linux requires certain skills/knowledge, this has nothing to do with
Pharo or Smalltalk.
To run 32-bit binaries on a 64-bit system you need 32-bit libraries.
This might help (although maybe it is not totally up to date for Pharo 7)
https://github.com/svenvc/pharo-server-tools/blob/master/
I'm running 64-bit Debian in a VirtualBox image on my Mac.
When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I
get the error message below. What's the difference??? Why can one find the
display driver and the other can't? This makes no sense.
Earlier, people have been telli
Those errors are not related to a 32 or 64 bits problem. The issue looks
like you've launched pharo-ui which looks for a physical screen that
isn't there. Are you trying to run pharo-ui in a debian VPS ?
You should run 'pharo' and 'pharo-ui', something like this:
$ pharo myApplication.image
S
On Thu, 22 Nov 2018 at 20:27, horrido wrote:
> I tried recompiling the SHA256 library without the '-m32' flag and 64-bit
>
Would the in-Image SHA256 be sufficient to start with?
Perhaps allow you to move forward while sorting out the main problem.
Another option could be libsodium
https://l
I ran 32-bit Pharo under 64-bit Debian and got this error:
[1] 8127
richard@debian:~/pharo32$ could not find display driver vm-display-X11;
either:
- check that
/home/richard/pharo32/pharo-vm/lib/pharo/5.0-201806281256//vm-display-X11.so
exists, or
- use the '-plugins ' option to tell me where
I tried recompiling the SHA256 library without the '-m32' flag and 64-bit
Pharo seg faulted:
pthread_setschedparam failed: Operation not permitted
This VM uses a separate heartbeat thread to update its internal clock
and handle events. For best operation, this thread should run at a
higher priori
He's got a 32 bit library that he wants to use, that won't work with a 64
bit VM.
Of course, recompiling the library for 64 bit is an option, too, but
probably more complicated.
Cheers,
Hans-Martin
Am 22. November 2018 9:21:47 vorm. schrieb Sven Van Caekenberghe
:
Just use 64 bit Pharo 7 o
I think Sven is probably right - but my notes show a DO installation from 5
months ago with:
curl https://get.pharo.org | bash
wget -O -
http://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/xUbuntu_16.04/Release.key
| apt-key add -
echo "deb
http://download.opensuse.org/r
Just use 64 bit Pharo 7 on a 64 bit Linux and be done with all this mess.
> On 22 Nov 2018, at 01:39, horrido wrote:
>
> Using zeroconf, I installed 32-bit Pharo under 64-bit Debian. Pharo refused
> to run – it threw up a bunch of errors.
>
>
>
> Mariano Martinez Peck wrote
>> Run Pharo 32 bi
horrido wrote
> it threw up a bunch of errors.
Can you be more specific and did you try Mariano's suggestion about 32-bit
libs?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Using zeroconf, I installed 32-bit Pharo under 64-bit Debian. Pharo refused
to run – it threw up a bunch of errors.
Mariano Martinez Peck wrote
> Run Pharo 32 bits and install 32 bit libs...
>
> On Wed, Nov 21, 2018, 21:07 Richard Kenneth Eng <
> horrido.hobbies@
> wrote:
>
> > I'm creating
Run Pharo 32 bits and install 32 bit libs...
On Wed, Nov 21, 2018, 21:07 Richard Kenneth Eng I'm creating the competition website using Pharo and Teapot. For
> encryption, I'm using Pierce Ng's PasswordCrypt, which requires a 32-bit C
> library. This means I must run 32-bit Pharo.
>
> And this me
I'm creating the competition website using Pharo and Teapot. For
encryption, I'm using Pierce Ng's PasswordCrypt, which requires a 32-bit C
library. This means I must run 32-bit Pharo.
And this means I must run 32-bit Pharo under 32-bit Linux. Therein lies the
rub...
I would like to host the webs
33 matches
Mail list logo