Groups > alt.comp.software.seamonkey > #177

Re: SeaMonkey Status Meeting - Sunday, 2 May 2021

Path	csiph.com!news.fcku.it!aioe.org!4+1/sO+hjgXu65daMoAjkg.user.gioia.aioe.org.POSTED!not-for-mail
From	Richmond <richmond@criptext.com>
Newsgroups	alt.comp.software.seamonkey
Subject	Re: SeaMonkey Status Meeting - Sunday, 2 May 2021
Date	Sat, 08 May 2021 15:00:24 +0100
Organization	Frantic
Lines	18
Message-ID	<84sg2xnx53.fsf@example.com> (permalink)
References	<CAOSOqAuCbTp7tbG1gy173iyUGAFQbZPkb1izNOavONE3NnMMdw@mail.gmail.com> <if520aF9c2oU1@mid.individual.net> <841rahpi0o.fsf@example.com> <ifnf35Fr0bnU1@mid.individual.net>
NNTP-Posting-Host	4+1/sO+hjgXu65daMoAjkg.user.gioia.aioe.org
Mime-Version	1.0
Content-Type	text/plain
X-Complaints-To	abuse@aioe.org
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Cancel-Lock	sha1:fPxvO76R4h836K69NnJQZa4hu1A=
X-Notice	Filtered by postfilter v. 0.9.2
Xref	csiph.com alt.comp.software.seamonkey:177

Show key headers only | View raw

frg <frgrahl@gmx.net> writes:

> No getting complaints from Linux users too. Personally I think it is
> 2021 and at least in 2022 i686 should go. Does not mean to rip out
> build code but just no longer release or test it. Anything built after
> around 2007 with the Core2Duo or higher should run x64 fine and can
> use 4GB. Not familiar with AMD but probably similar.
>

If linux users run out of memory they should create more swap space in a
swap file.

Debian 10 386 has working versions of firefox and thunderbird. Seamonkey
gave an illegal instruction error even with the --version option. All my
historical email is stored in seamonkey I think and I had a working
version of seamonkey on slackware but I am not sure where it came from I
may have built it myself. Now I have installed debian 10.

Back to alt.comp.software.seamonkey | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

SeaMonkey Status Meeting - Sunday, 2 May 2021 frg <frgrahl@gmx.net> - 2021-05-01 15:05 +0200
  Re: SeaMonkey Status Meeting - Sunday, 2 May 2021 Richmond <richmond@criptext.com> - 2021-05-08 12:44 +0100
    Re: SeaMonkey Status Meeting - Sunday, 2 May 2021 frg <frgrahl@gmx.net> - 2021-05-08 14:38 +0200
      Re: SeaMonkey Status Meeting - Sunday, 2 May 2021 Richmond <richmond@criptext.com> - 2021-05-08 15:00 +0100
      Re: SeaMonkey Status Meeting - Sunday, 2 May 2021 Daniel65 <daniel47@eternal-september.org> - 2021-05-09 19:15 +1000
      Re: SeaMonkey Status Meeting - Sunday, 2 May 2021 Richmond <richmond@criptext.com> - 2021-05-10 13:27 +0100

csiph-web