[DNG] BUG (severe): chromium crashes

[Enrico Weigelt, metux IT consult]

Hi folks,


on devuan jessie (in chroot) chromium crashes immediately:

(devuan)nekrad@orion:~$ chromium -g --temp-profile
cat: /etc/debian_version: Datei oder Verzeichnis nicht gefunden
# Env:
# LD_LIBRARY_PATH=
# 
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

#GTK_PATH=
#  CHROMIUM_FLAGS= --user-data-dir=/tmp/tmp.67iwwtWLCD
/usr/bin/gdb /usr/lib/chromium/chromium -x /tmp/chromiumargs.jpNLMN
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/chromium/chromium...Reading symbols from 
/usr/lib/debug/.build-id/17/fd2cadc19874b306dbda8bcacd891a063ef00e.debug...(no 
debugging symbols found)...done.

(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/lib/chromium/chromium 
--user-data-dir=/tmp/tmp.67iwwtWLCD

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xf547fb40 (LWP 27442)]
[New Thread 0xf4c7fb40 (LWP 27448)]
[New Thread 0xf434ab40 (LWP 27449)]
[New Thread 0xf3b4ab40 (LWP 27450)]
[27438:27450:0701/035457.549274:ERROR:bus.cc(427)] Failed to connect to 
the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: 
Datei oder Verzeichnis nicht gefunden

[New Thread 0xf334ab40 (LWP 27451)]
[New Thread 0xf2b42b40 (LWP 27453)]
[New Thread 0xf2b4ab40 (LWP 27452)]
[New Thread 0xf2342b40 (LWP 27454)]
[New Thread 0xf09b9b40 (LWP 27455)]
[New Thread 0xf01b9b40 (LWP 27456)]
[New Thread 0xef9b9b40 (LWP 27457)]
[New Thread 0xef1b9b40 (LWP 27458)]
[New Thread 0xee9b9b40 (LWP 27459)]
[New Thread 0xee1b9b40 (LWP 27460)]
[New Thread 0xed9b9b40 (LWP 27461)]
[New Thread 0xed1b9b40 (LWP 27462)]
[New Thread 0xec9b9b40 (LWP 27463)]
[New Thread 0xec1b9b40 (LWP 27464)]
[New Thread 0xeb9b9b40 (LWP 27465)]
[New Thread 0xeb16db40 (LWP 27466)]
[New Thread 0xea887b40 (LWP 27467)]
[New Thread 0xea087b40 (LWP 27468)]
[New Thread 0xe95ccb40 (LWP 27469)]
shm_open() failed: Keine Berechtigung
[New Thread 0xe4d51b40 (LWP 27470)]
[New Thread 0xe4551b40 (LWP 27471)]
[New Thread 0xe3d51b40 (LWP 27482)]
[27438:27465:0701/035457.714170:FATAL:memory.cc(22)] Out of memory. 
size=131072


Program received signal SIGABRT, Aborted.
[Switching to Thread 0xeb9b9b40 (LWP 27465)]
0xf685fe2c in raise () from /lib/i386-linux-gnu/libc.so.6
(gdb) backtrace
#0  0xf685fe2c in raise () from /lib/i386-linux-gnu/libc.so.6
#1  0xf68614b3 in abort () from /lib/i386-linux-gnu/libc.so.6
#2  0x5870016c in base::debug::BreakDebugger() ()
#3  0x5871afc1 in logging::LogMessage::~LogMessage() ()
#4  0x58745b73 in base::(anonymous namespace)::OnNoMemory(unsigned int) ()
#5  0x58745ac1 in base::TerminateBecauseOutOfMemory(unsigned int) ()
#6  0x5872a34a in 
base::FieldTrialList::InstantiateFieldTrialAllocatorIfNeeded() ()
#7  0x5872a53b in base::FieldTrialList::CopyFieldTrialStateToFlags(char 
const*, char const*, char const*, base::CommandLine*) ()
#8  0x5791cca2 in 
content::BrowserChildProcessHostImpl::CopyFeatureAndFieldTrialFlags(base::CommandLine*) 
()
#9  0x57a86655 in 
content::GpuProcessHost::LaunchGpuProcess(gpu::GpuPreferences*) ()

#10 0x57a84aef in content::GpuProcessHost::Init() ()
#11 0x57a848c6 in 
content::GpuProcessHost::Get(content::GpuProcessHost::GpuProcessKind, 
bool) ()
#12 0x57a6d354 in 
content::BrowserGpuChannelHostFactory::EstablishRequest::EstablishOnIO() ()
#13 0x57a6e634 in base::internal::Invoker, void ()>::Run(base::internal::BindStateBase*) ()
#14 0x587abc71 in base::debug::TaskAnnotator::RunTask(char const*, 
base::PendingTask*) ()

#15 0x58723489 in base::MessageLoop::RunTask(base::PendingTask*) ()
#16 0x587238af in 
base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) ()

#17 0x58723c88 in base::MessageLoop::DoWork() ()
#18 0x587273bd in 
base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) ()

#19 0x587231d5 in base::MessageLoop::RunHandler() ()
#20 0x5874c9df in base::RunLoop::Run() ()
#21 0x58775b94 in base::Thread::Run(base::RunLoop*) ()
#22 0x57938f4a in content::BrowserThreadImpl::IOThreadRun(base::RunLoop*) ()
#23 0x57939115 in content::BrowserThreadImpl::Run(base::RunLoop*) ()
#24 0x58775cd8 in base::Thread::ThreadMain() ()
#25 0x587701d0 in base::(anonymous 

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[zap]

It is a little too confusing trying to install openrc at the moment so I
will pass for now...

It is just a shame that the runit-init package was taken down...


On 06/30/2017 06:46 PM, Steve Litt wrote:
> On Fri, 30 Jun 2017 21:45:23 +0200
> Joachim Fahrner  wrote:
>
>> Am 2017-06-30 19:16, schrieb Steve Litt:
>>
>>> Would it be possible for you to install OpenRC from upstream
>>> source? I know that's easily doable with runit or s6, but I know
>>> little about OpenRC.  
>> I'm wondering why there are lots of discussions about init systems.
>> What is wrong with sysv init? My notebook is booting (from ssd)
>> within 8 seconds. Nothing I would complain about.
> sysvinit works, always has. It's a good, workable init system. And it's
> for certain better than systemd unless 99% of your priority is boot
> time.
>
> Now let me explain why I personally prefer runit instead of sysvinit...
>
> * sysvinit requires those gigantic and messy init scripts, whereas
>   runit requires only a 10 line run script, give or take.
>
> * sysvinit depends on PID files that can make things go wrong in
>   difficult to understand ways. Runit has no PID files.
>
> * With runit, if you write a daemon program, your daemon program
>   doesn't need to background itself nor tell the init system that it's
>   ready.
>
> * I find runit more adaptable to varied usages than sysvinit.
>
> * With runit, I can look in one directory and easily see all my
>   daemons, with easy names that don't look like S50-whatever
>
> * Runit's sv command does all the stuff needed by the five mandatory
>   sections of a sysvinit script.
>
> * Runit doesn't require the commented out special numbers and stuff
>   that sysvinit init scripts do.
>
> * Runit is much less than thirty two years old. Although both you and I
>   know sysvinit's age doesn't make it one micron less competent, it's
>   much easier to argue that runit is better than systemd rather than
>   arguing that sysvinit is better than systemd. This benefit, of
>   course, is purely rhetoric and political, and in fact I think
>   sysvinit is MUCH better than systemd.
>
> * It's really a matter of personal preference, and it's easy to switch
>   between sysvinit and runit.
>
> By the way, everything I said about runit goes equally for the s6 init
> system.
>
>
>
>

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

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Steve Litt]

On Fri, 30 Jun 2017 21:45:23 +0200
Joachim Fahrner  wrote:

> Am 2017-06-30 19:16, schrieb Steve Litt:
> 
> > Would it be possible for you to install OpenRC from upstream
> > source? I know that's easily doable with runit or s6, but I know
> > little about OpenRC.  
> 
> I'm wondering why there are lots of discussions about init systems.
> What is wrong with sysv init? My notebook is booting (from ssd)
> within 8 seconds. Nothing I would complain about.

sysvinit works, always has. It's a good, workable init system. And it's
for certain better than systemd unless 99% of your priority is boot
time.

Now let me explain why I personally prefer runit instead of sysvinit...

* sysvinit requires those gigantic and messy init scripts, whereas
  runit requires only a 10 line run script, give or take.

* sysvinit depends on PID files that can make things go wrong in
  difficult to understand ways. Runit has no PID files.

* With runit, if you write a daemon program, your daemon program
  doesn't need to background itself nor tell the init system that it's
  ready.

* I find runit more adaptable to varied usages than sysvinit.

* With runit, I can look in one directory and easily see all my
  daemons, with easy names that don't look like S50-whatever

* Runit's sv command does all the stuff needed by the five mandatory
  sections of a sysvinit script.

* Runit doesn't require the commented out special numbers and stuff
  that sysvinit init scripts do.

* Runit is much less than thirty two years old. Although both you and I
  know sysvinit's age doesn't make it one micron less competent, it's
  much easier to argue that runit is better than systemd rather than
  arguing that sysvinit is better than systemd. This benefit, of
  course, is purely rhetoric and political, and in fact I think
  sysvinit is MUCH better than systemd.

* It's really a matter of personal preference, and it's easy to switch
  between sysvinit and runit.

By the way, everything I said about runit goes equally for the s6 init
system.




-- 
SteveT

Steve Litt 
June 2017 featured book: The Key to Everyday Excellence
http://www.troubleshooters.com/key
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Didier Kryn]

Le 30/06/2017 à 23:30, Vincent Bentley a écrit :

Along time ago, well designed and well behaved software could be
recognised by the number of years passed without changes. I worked at
one place that was proud of release version birthdays.


Agreed. That's why I'm always bothered with the fast release pace 
of some essential pieces of software, with the fastest being the GCC and 
the Linux kernel.


Didier


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

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Vincent Bentley]

Along time ago, well designed and well behaved software could be
recognised by the number of years passed without changes. I worked at
one place that was proud of release version birthdays.

On 30/06/17 21:22, zap wrote:
> 
> 
> On 06/30/2017 03:45 PM, Joachim Fahrner wrote:

> I just want to use an init that is more regularly updated that is all...
> 



smime.p7s
Description: S/MIME Cryptographic Signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[zap]

On 06/30/2017 03:45 PM, Joachim Fahrner wrote:
> Am 2017-06-30 19:16, schrieb Steve Litt:
>
>> Would it be possible for you to install OpenRC from upstream source? I
>> know that's easily doable with runit or s6, but I know little about
>> OpenRC.
>
> I'm wondering why there are lots of discussions about init systems.
> What is wrong with sysv init? My notebook is booting (from ssd) within
> 8 seconds. Nothing I would complain about.
>

I just want to use an init that is more regularly updated that is all...

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

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

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[zap]

On 06/30/2017 11:21 AM, Svante Signell wrote:
> On Thu, 2017-06-29 at 19:34 -0400, zap wrote:
>> not really complaining for the most part. But I am curious that's
>> all.
>>
> Hi zap,
>
> As I wrote earlier, you can install openrc by:
> 0) Enable ascii in /etc/apt/sources.list
> deb http://auto.mirror.devuan.org/merged ascii main
>
> 1) add to /etc/apt/sources.list
>  deb http://packages.devuan.org/devuan/ ascii-proposed main
>
> 2) apt-get update
>
> 3) apt-get download sysvinit-utils
>
> 4) Build* and install libfdisk1 and util-linux (2.29.21+devuan1). If
> you are in i386 I can send you them. Otherwise see below.
>
> dpkg -i libfdisk1_2.29.2-1+devuan1_i386.deb util-linux_2.29.2-
> 1+devuan1_i386.deb sysvinit-utils_2.88dsf-59.9+devuan2_i386.deb
>
> 5) apt-get upgrade: Installs latest initscripts:
> initscripts (2.88dsf-59.9+devuan2)
>
> 6) apt-get -s install openrc
> Check that all is OK, then remove the -s
> The following additional packages will be installed:
>   libeinfo1 librc1
> The following packages will be REMOVED:
>   sysv-rc
>
> To build util-linux for your arch:
> 1) Add to sources.list
> deb-src http://packages.devuan.org/devuan/ ascii-proposed main
>
> 2) Download sources
> dget https://packages.devuan.org/devuan/pool/main/u/util-linux/util-lin
> ux_2.29.2-1+devuan1.dsc
>
> 3) Unpack sources
> dpkg-source -x util-linux_2.29.2-1+devuan1.dsc
>
> 4) cd util-linux-2.29.2/
> Install all packages needed in debian/control as root:
> see Build-Depends: entry
>
> 5) dpkg-buildpackage 2>&1 | tee buildpackage-2.29.2-1+devuan1.log
> (see above at point 4)
Okay, this is a better way to know how to do so. I didn't understand the
instructions before. that's all... thanks
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Joachim Fahrner]

Am 2017-06-30 19:16, schrieb Steve Litt:


Would it be possible for you to install OpenRC from upstream source? I
know that's easily doable with runit or s6, but I know little about
OpenRC.


I'm wondering why there are lots of discussions about init systems. What 
is wrong with sysv init? My notebook is booting (from ssd) within 8 
seconds. Nothing I would complain about.


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

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Steve Litt]

On Fri, 30 Jun 2017 14:20:08 +
Miroslav Rovis  wrote:

> On 170629-19:34-0400, zap wrote:
> > not really complaining for the most part. But I am curious that's
> > all.  
> I wish I knew better, but, for a simple question of mine today (see
> my other email of today, and the links to dev1galaxy.org post of
> mine) I only after some time waiting got a reply...

Would it be possible for you to install OpenRC from upstream source? I
know that's easily doable with runit or s6, but I know little about
OpenRC.
 
SteveT

Steve Litt 
June 2017 featured book: The Key to Everyday Excellence
http://www.troubleshooters.com/key
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Miroslav Rovis]

On 170630-10:16-0500, goli...@dyne.org wrote:
> On 2017-06-30 09:20, Miroslav Rovis wrote:
> > 
> > . . .  (and although I can log in to GDO, I'm
> > very clumsy at finding out things in there still, to be able to tell
> > you).
> > 
> 
> I often get to gdo from the dev1galaxy forum:
> 
> https://dev1galaxy.org/viewforum.php?id=18  (gdo projects)
> https://dev1galaxy.org/viewforum.php?id=19  (gdo issues)
> 
> The bot that posts those threads is a bit whimsical.  But it does provide a
> handy, searchable db of what is on git and access to the target at one
> click.
> 
> golinux
> 
Thanks, golinux!

Aaah, I have browsed those on a few occasions, but only once you start using 
Devuan so much more you slowly start to get the grip on it... So slowly here...

But the Svante Signell's tips in the other email is so appealing... Except, 
time is needed more abundantly for all that one would like to do...

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


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

[DNG] Migrating from jessie to ascii

[Ismael L. Donis Garcia]

So far I'm using on my work PC to devuan jessie 32 bit, but I've thought 
about migrating to ascii.


I use virtualbox 5.1.22 with several virtual PCs: devuan ascii, 
manjaro-openrc and windows xp, 7, server2003


Do you think that at the moment I can move to ascii without being stopped 
working virtual PCs?


As my knowledge is not very advanced, that's why I ask the list not to fence 
to be made me all to lose.


Best Regards
--
ISMAEL
Devuan User : http://distrowatch.com/table.php?distribution=devuan
WebSite: http://sisconge.byethost15.com/ 



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

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Svante Signell]

On Thu, 2017-06-29 at 19:34 -0400, zap wrote:
> not really complaining for the most part. But I am curious that's
> all.
> 

Hi zap,

As I wrote earlier, you can install openrc by:
0) Enable ascii in /etc/apt/sources.list
deb http://auto.mirror.devuan.org/merged ascii main

1) add to /etc/apt/sources.list
 deb http://packages.devuan.org/devuan/ ascii-proposed main

2) apt-get update

3) apt-get download sysvinit-utils

4) Build* and install libfdisk1 and util-linux (2.29.21+devuan1). If
you are in i386 I can send you them. Otherwise see below.

dpkg -i libfdisk1_2.29.2-1+devuan1_i386.deb util-linux_2.29.2-
1+devuan1_i386.deb sysvinit-utils_2.88dsf-59.9+devuan2_i386.deb

5) apt-get upgrade: Installs latest initscripts:
initscripts (2.88dsf-59.9+devuan2)

6) apt-get -s install openrc
Check that all is OK, then remove the -s
The following additional packages will be installed:
  libeinfo1 librc1
The following packages will be REMOVED:
  sysv-rc

To build util-linux for your arch:
1) Add to sources.list
deb-src http://packages.devuan.org/devuan/ ascii-proposed main

2) Download sources
dget https://packages.devuan.org/devuan/pool/main/u/util-linux/util-lin
ux_2.29.2-1+devuan1.dsc

3) Unpack sources
dpkg-source -x util-linux_2.29.2-1+devuan1.dsc

4) cd util-linux-2.29.2/
Install all packages needed in debian/control as root:
see Build-Depends: entry

5) dpkg-buildpackage 2>&1 | tee buildpackage-2.29.2-1+devuan1.log
(see above at point 4)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[golinux]

On 2017-06-30 09:20, Miroslav Rovis wrote:


. . .  (and although I can log in to GDO, I'm
very clumsy at finding out things in there still, to be able to tell
you).



I often get to gdo from the dev1galaxy forum:

https://dev1galaxy.org/viewforum.php?id=18  (gdo projects)
https://dev1galaxy.org/viewforum.php?id=19  (gdo issues)

The bot that posts those threads is a bit whimsical.  But it does 
provide a handy, searchable db of what is on git and access to the 
target at one click.


golinux


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

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Miroslav Rovis]

On 170629-19:34-0400, zap wrote:
> not really complaining for the most part. But I am curious that's all.
I wish I knew better, but, for a simple question of mine today (see my other 
email of today, and the links to dev1galaxy.org post of mine) I only after some 
time waiting got a reply...

Some of our devs are really overworked already.

And yet, even though it's not a perfect place either, there is a whole lot more 
sanity here than many other places... Esp. those engulfed with 
systemDestruction but other places as well...

I wish I know better and were able to help in, esp. in development, because you 
can see by telltales here and there, more manpower is needed in Devuan... I 
hope at least that I'll be able to help more seriously with testing some day 
not too far from now.

I've used openrc a lot, because I've used Gentoo for some eight or nine 
years... But it very hard to know when to expect it to be in Devuan fully and 
operationally (and although I can log in to GDO, I'm very clumsy at finding out 
things in there still, to be able to tell you).

Just more patience, zap. You can almost never tell when things are going to be 
done in programming/in development. And it's almost always later then they have 
been expected to happen.

Regards!
-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


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

Re: [DNG] ascii-backports? for torbrowser-launcher install WAS: heads 0.3 released!

[Miroslav Rovis]

This topic is, among other things, where I learned about...

On 2017-06-23 19:17, Arnt Karlsen wrote:
> On Fri, 23 Jun 2017 15:24:48 +0200, Didier wrote in message 
> <84409ec6-371b-0839-b68a-48d36ad631e1@???>:
> 
> > Le 23/06/2017 à 11:48, KatolaZ a écrit :
> > > On Fri, Jun 23, 2017 at 11:41:14AM +0200, Didier Kryn wrote:
> > >> Le 23/06/2017 à 10:41, Arnt Karlsen a écrit :
> > >>> On Thu, 22 Jun 2017 17:41:34 +0200, parazyd@??? wrote in
> > >>> message <20170622154134.GA21849@fq>:
> > >>>
> >  Tor Browser 7
> >  -
> > 
> >  The Tor Browser has been bumped to version 7, and now introduces
> >  a dependency on Pulseaudio if we want sound in Tor Browser.
> >  heads does not ship with Pulseaudio so for the time being, there
> >  will be no sound in Tor Browser.
...

...about:
 
> ..there is, you want torbrowser-launcher.
> 
( well also the failed BTS which contained failed report with 
torbrowser-launcher,which I don't have in my Mutt, since I moved recently from 
Gentoo to Devuan... But that one is in the dev1galaxy link I give below )

And I'm courious if the way to install it is as I plan to do next, pls visit:

How to install TorBrowser in Ascii? From Stretch backports or?
https://dev1galaxy.org/viewtopic.php?pid=2694#p2694

The other question in this email of mine of course being: are there 
ascii-backports yet?


BTW, my Devuan (both the Air-Gapped master and this online clone of it) work 
great (a few glitches here and there, but it's a beauty! No systemDestruction, 
no pulse, and in my case no dbus, so great!).

NOTE: if this gets out of thread or anything, it's not intentional. Namely this 
is the first time I discovered that mailto-mutt works, and I was able to click 
on the link

in:
https://lists.dyne.org/lurker/message/20170623.191755.f4ea8611.en.html
and, this was previously missing in my understanding: forground the terminal in 
which I had started my palemoon browser (because all, but all the Palemoon 
windows were frozen), and there in this terminal was Mutt with the message set 
for replying.

Aarggh! I see why the thread by the subject:
"grsecurity ripoff by Google, with Linus' approval WAS: I have a question about 
libsystemd0 in devuan ascii" was split at one time...
If you reply from web, you don't get the "In-Reply-To: " header at all, it 
seems to me. But seeing that, I include it manually now...

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


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

Re: [DNG] systemd: good riddance!

[Ron]

On Fri, 30 Jun 2017 09:07:46 +0200
Jaromil  wrote:

> If you wait by the river long enough, the bodies of your enemies will float 
> by.
> - Sun Tzu

I'm afraid he never wrote that:  See for instance 
https://shibumimanagementcanada.wordpress.com/2014/02/06/invented-sun-tzu-art-of-war-quotes/
 
Cheers,
 
Ron.
-- 
  An ignorant person is one who doesn't know
what you have just found out.
  -- Will Rogers

   -- http://www.olgiati-in-paraguay.org --
 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd: good riddance!

[Jaromil]

On Fri, 30 Jun 2017, Aldemir Akpinar wrote:

> On 30 June 2017 at 09:14, Nate Bargmann  wrote:
> > * On 2017 30 Jun 00:55 -0500, Alessandro Selli wrote:
> >
> >>   Maybe it's me, but what the hell is a DNS resolver doing inside an init
> >> system?
> >
> > The same thing that a time sync (NTP) daemon is doing in there...
> >
> > - Nate
> > 
> 
> And these lads still think that they can do a better job rewriting all
> these daemons.


If you wait by the river long enough, the bodies of your enemies will float by.

- Sun Tzu



Besides the riddance, what I'm really worried by is that these lads
are not waiting to demonstrate their qualities, but selling them
already to an industry which often runs mission-critical services -
namely Red-Hat does provide the infrastructure for several public
sector operations, also here in Europe.

Last not least, its clear to some of us since years now that these
lads want to restrict ABI access and build a full vertical stack that
puts a machine completely under systemd's control from its boot - a
sort of revamp of the "trusted computing" weird techno-fascist dream

Before you think I'm crazy in writing what I wrote, please have a look
at the US patent 20150040216-A1 "Systems and Methods for Restricting
Application Binary Interfaces" filed by Paul Moore, Dan Walsh and
Lennart Poettering on behalf of Red Hat inc.

So to conclude I'm afraid that the bodies floating by in this war will
be many more than those of our "enemies".

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

Re: [DNG] systemd: good riddance!

[Dr. Nikolaus Klepp]

Am Freitag, 30. Juni 2017 schrieb Aldemir Akpinar:
> On 30 June 2017 at 09:14, Nate Bargmann  wrote:
> > * On 2017 30 Jun 00:55 -0500, Alessandro Selli wrote:
> >
> >>   Maybe it's me, but what the hell is a DNS resolver doing inside an init
> >> system?
> >
> > The same thing that a time sync (NTP) daemon is doing in there...
> >
> > - Nate
> > 
> 
> And these lads still think that they can do a better job rewriting all
> these daemons.

This is a remote administration feature, not a bug :-)



-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd: good riddance!

[Joachim Fahrner]

Am 2017-06-30 07:53, schrieb Alessandro Selli:

  Maybe it's me, but what the hell is a DNS resolver doing inside an 
init

system?


systemd is _NOT_ an init system. That's a mythos. Systemd started as an 
init system, but evolved step-by-step to a monolithic low level Linux 
userland. It's driven by Red Hat to make money out of supporting their 
development.


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

Re: [DNG] systemd: good riddance!

[Aldemir Akpinar]

On 30 June 2017 at 09:14, Nate Bargmann  wrote:
> * On 2017 30 Jun 00:55 -0500, Alessandro Selli wrote:
>
>>   Maybe it's me, but what the hell is a DNS resolver doing inside an init
>> system?
>
> The same thing that a time sync (NTP) daemon is doing in there...
>
> - Nate
> 

And these lads still think that they can do a better job rewriting all
these daemons.
--
aldemir
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd: good riddance!

[Nate Bargmann]

* On 2017 30 Jun 00:55 -0500, Alessandro Selli wrote:

>   Maybe it's me, but what the hell is a DNS resolver doing inside an init
> system?

The same thing that a time sync (NTP) daemon is doing in there...

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng