Re: [DNG] How to fix rng-tools hang

[Dimitris via Dng]

On 10/28/19 5:24 AM, s@po wrote:
> Does anyone knows how to surpass this?

probably install haveged in systems without hwrng.

other suggestion would be to use `HRNGDEVICE=/dev/urandom` in
/etc/default/rng-tools, but that should be avoided for crypto entropy, iirc.



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan sparc port

[Fred]

On 10/28/19 8:12 PM, Adam Borowski wrote:

On Fri, Oct 25, 2019 at 09:02:13AM -0700, Fred wrote:

Hello,

Will there ever be a sparc64 port of Devuan?

Very very likely no.  The focus of this distribution is fixing systemd
caused regression, not porting.  And reviving the arch would require a lot
of effort:

Sparc is dead.  Oracle killed its hardware in 2016-17, and was mostly
hostile to Linux development for it (and Solaris is now dead, too).  The
kernel maintainer did the last commit in Nov 2018, any newer stuff is
someone doing drive-by work to avoid blockers to an unrelated arch-indep
change, same as happens with other dead archs.

It might be tempting to do that effort to allow some hardware not go to
waste, but human time is expensive, hardware cheap -- thus I'd recommend
migrating to a supported arch sooner.


Meow!


Hi Adam,
Thanks for your response.  I am planning to change from Debian (x86) to 
Devuan but I also have a Sun U10 that has been running Solaris 2.6 for 
21 years that is very useful but will probably have to fall by the wayside.


Best regards,
Fred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan sparc port

[s]

> On Fri, Oct 25, 2019 at 09:02:13AM -0700, Fred wrote:
> > Hello,
> > 
> > Will there ever be a sparc64 port of Devuan?
> 
> Very very likely no.  The focus of this distribution is fixing systemd
> caused regression, not porting.  And reviving the arch would require a lot
> of effort:
> 

Oracle doesn't have a very well defined future for Sparc( the dead line was 
somewhat defined to 2021 or 2022 iirc ), the next range of devices roadmap, is 
undefined, but they have put great effort in trying to sell their Oracle Linux 
distro with Oracle databases as a package( after the amount of bugs found in 
x86 and others.. ).
They have been optimizing Sparc on Linux for Oracle databases, for years..
And they have found a jump in sales.. wether it will be suficient to maintain 
Sparc Alive, I really don't know..

IMHO, first I think we need ecosystem & stability, later a choose can, 
eventually, be made on what archs to add..

-- 
tux 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] I wrote IBM

[Rick Moen]

Quoting goli...@devuan.org (goli...@devuan.org):

> This is what arrived with your above reply:
> 
> From  Hendrik Boom   Add contact
> SenderDng   Add contact
> Todng@lists.dyne.org  Add contact
> Date  Today 14:56
> Mailing List   href="mailto:dng-requ...@lists.dyne.org?subject=help";
> target="_blank" onclick="return 
> rcmail.command('compose','dng-requ...@lists.dyne.org?subject=help',this)">Help   href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng";
> target="_blank">Subscribe   href="https://mailinglists.dyne.org/cgi-bin/mailman/options/dng";
> target="_blank">Unsubscribe   href="mailto:dng@lists.dyne.org"; target="_blank" onclick="return 
> rcmail.command('compose','dng@lists.dyne.org',this)">Post   href="https://mailinglists.dyne.org/cgi-bin/mailman/private/dng/";
> target="_blank">List Archive  
> 
> All lists on dyne server(s) are suffering from this.  It is a
> mystery and very annoying . . .

FWIW, I'm _not_ seeing that on any postings to Dng.  (I cannot speak at
this writing to possible strangeness on other dyne.org mailing lists,
but on a hunch would expect to see the same thing as there I do on Dng.)

I would surmise that the effect you speak of us happening in some
misbehaving MUA (mail client), like maybe someone's installation of
Roundcube.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] I wrote IBM

[Rick Moen]

Quoting goli...@devuan.org (goli...@devuan.org):

> This email does not address the content of this email but rather
> something very strange that came through in the header:
> 
> https://dev1galaxy.org/files/cruft.png
> 
> This started with the above email from Steve.

I'll retain for a while that verbatim message from Steve Litt, in case
you and I need to discuss it.  E.g, I could put the full headers as seen
here into Pastebin.  To be clear, as received here, Steve's mail and all
the others recently (received from Dng) look just fine as received here.

Locally on linuxmafia.com, all the mail from my Devuan mailing list
subscriptions arrive at my SMTP daemon (Exim4), get handed off to
Procmail as Local Delivery Agent, and get appended to mbox file
/home/rick/inboxes/lists .  And the contents (including recently arrived
mails including Steve's) look correct and properly formatted both when
viewed using a terminal pager such as /usr/bin/less or when viewed using
my preferred Mail User Agent (mail client), mutt.

I notice that your own headers include:

User-Agent: Dyne.org Webmail

This raises the probably unwelcome and very annoying possibility that
the program referenced had a parsing problem on one or more recently
arrived pieces of mail.

If you can get the attention of someone who has local administrative
access (at the shell) on the dyne.org host, he/she could take a look at
whatever mailbox file this 'Dyne.org Webmail' program relies on for your
mail -- to see if there's any obvious corruption in the file as stored
locally (your Inbox folder, I mean).  Maybe it's an mbox file (or a
Maildir directory tree).  Either of those is pretty easy to expunge file
corruption from.


But also, something is confusing me, here:

> Here's the complete header.  Problem is under "Precedence: list":

> Return-Path: 
> Delivered-To: goli...@devuan.org
[big snip]
> Precedence: list
> List-Id: "The first mailinglist after debianfork.org"
> 
> List-Unsubscribe:
> ,
> 
> List-Archive:
> 
> List-Post: 
> List-Help: 
> List-Subscribe:
> ,
> 
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: base64
> Errors-To: dng-boun...@lists.dyne.org
> Sender: "Dng" 


Um... nothing there looks corrupted in any way, to my eyes.
If 'Dyne.org Webmail' cannot parse that correctly, then IMO it has a
big (parsing) problem.  That's a bog-standard set of headers.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng