Re: [DNG] DNS Ad-Blocking (Was: FF pulseaudio hard dependency is here)

[devuanfanboy]

You can setup lightttpd and use a host file as well (use unbound on 
embedded).


Create an "empty" html document on the server:

in index.htm:



I found this works better than using transparent gifs, pop ups are 
killed too.

 
On Monday, March 13, 2017 8:11 PM, Patrick Meade 
 wrote:

 

On 03/13/2017 02:46 PM, Rob van der Putten wrote:

On 12/03/17 16:49, Renaud (Ron) OLGIATI wrote:
 

Have you considered rolling your own add-blocking with a list of
unwanted sites in /etc/hosts ?

A bad idea, because your browser expects some sort of response.
It's better to replace unwanted content with a small transparent 
gif.


I run one of these on my network at home:

Pi-hole: A black hole for Internet advertisements
https://pi-hole.net/


Patrick
___
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] anybody going to libreplanet?

[Alessandro Selli]

Il 18/03/2017 21:18, Miles Fidelman ha scritto:
> Hi Folks,
>
> I didn't see any reaction to this - which makes me wonder.. is anybody
> here going to libreplanet?

  Not me.

> For that matter, is anybody in the Greater Boston area?

  Nope, I'm an ocean away.




>  forwarded message 
>
> Author: Miles Fidelman
> Date: 2017-03-15 21:49 -700
> To: dng
> Subject: Re: [DNG] We need to speak up
> On 3/15/17 9:14 PM, Christopher Clements wrote:
>
> >
> > The exact suggestion is here:
> > 
> >
> >> That is an excellent idea. Would be great if someone got organized
> >> enough to start a dialog with EVERY upstream dev individually and/or
> >> collectively. Unfortunately, that would be a mammoth task requiring
> >> more time than most people could find. I've done work like that on
> >> various issues and know from experience, it is a full time job.
> >
> > Perhaps just an open letter?
> >
> > It seemed relatively simple until you brought up the issue of actually
> > contacting all the developers (without using debian-devel, most
> likely).
> > I only thought about one aspect of it, and now it seems like it would
> > be _impossible_ without using debian-devel or mass-mailing every single
> > developer (out of the question).
> >
> I tried raising the question on libreplanet-discuss - asking what
> uptream developers are doing now. Not a tremendous response, so far.
>
> But maybe this would be a good workshop topic, or BOF session, at the
> upcoming libreplanet conference (sponsored by the Free Software
> Foundation) in Boston. It's coming up right spanking now (March 25-6),
> at MIT. An awful lot of open source upstream developers show up, and
> it's a good forum for discussion policy issues related to open source
> software. https://www.libreplanet.org/2017/
>
> It might be a little late to organize a formal talk or panel session,
> but someone might want to give the organizers a call. BOFs are easy to
> setup - see https://libreplanet.org/wiki/LibrePlanet:Conference/2017
>
> Everyone should also join FSF and the libreplanet-discuss list.
>
> It's generally a good time, with good people. I'm not sure I'll be able
> to make it - I live in the area, but I'm currently in AZ for an extended
> period, helping my 96-year-old Dad settle into a new house - not sure if
> I'll be back in time.
>
> Hopefully someone from the Devuan team will be there, and can organize
> something.
>
> Miles Fidelman
>
>



-- 
Alessandro Selli 
Tel. 3701355486
VOIP SIP: dhatarat...@ekiga.net
Chiave PGP/GPG key: B7FD89FD

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

[DNG] My 20th century writings on encapsulation

[Steve Litt]

My main gripe about systemd is lack of encapsulation: Every "module",
and I use that term very loosely, must know the intimate details of
every other "module."

Here's something I wrote on the subject, back in 1998:

http://troubleshooters.com/tpromag/9801.htm#StateOfTroubleshooting

Scan down to the subsection called "Watch Your Back". I read it for the
first time in several years and thought "Everything remains the same:
Only the faces change."

SteveT

Steve Litt
March 2017 featured book: Troubleshooting: Why Bother?
http://www.troubleshooters.com/twb
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] surf segmentation fault

[KatolaZ]

On Sun, Mar 19, 2017 at 03:39:41PM +0100, Joachim Fahrner wrote:
> Now I compiled the latest version from git with symbols and did a backtrace
> under gdb:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xaa5c5a00 in ?? ()
> (gdb) backtrace

[cut]

It would be good to file the bug to the surf mailing list.

My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


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

Re: [DNG] surf segmentation fault

[Joachim Fahrner]

Now I compiled the latest version from git with symbols and did a 
backtrace under gdb:


Program received signal SIGSEGV, Segmentation fault.
0xaa5c5a00 in ?? ()
(gdb) backtrace
#0  0xaa5c5a00 in ?? ()
#1  0xfffb in ?? ()
#2  0xae3d99c0 in ?? ()
#3  0xaa5c59eb in ?? ()
#4  0xabc51f1c in ?? ()
#5  0xb50b298b in ?? () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#6  0xb50b298b in ?? () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#7  0xb50b2aaf in ?? () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#8  0xb50b298b in ?? () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#9  0xb50b298b in ?? () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#10 0xb50b298b in ?? () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#11 0xb50af3e9 in ?? () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#12 0xb504b806 in JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, 
JSC::Register*) () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#13 0xb502993f in JSC::Interpreter::executeCall(JSC::ExecState*, 
JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, 
JSC::ArgList const&) () from 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#14 0xb516d234 in JSC::call(JSC::ExecState*, JSC::JSValue, 
JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) 
() from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#15 0xb62d2a86 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#16 0xb64a9b3d in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#17 0xb64a9ffe in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#18 0xb64bb96d in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#19 0xb64a38d4 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#20 0xb64a5bd2 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#21 0xb64bf145 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#22 0xb646ede5 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#23 0xb66a2e8c in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#24 0xb66cf3d4 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#25 0xb66a9540 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#26 0xb66a9591 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#27 0xb66abfd5 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#28 0xb66a9abf in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#29 0xb66acc22 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#30 0xb66accd1 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#31 0xb67facbf in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#32 0xb67faa76 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#33 0xb6807838 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#34 0xb6865976 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#35 0xb685b005 in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0
#36 0xb70d972d in ?? () from 
/usr/lib/i386-linux-gnu/libwebkitgtk-1.0.so.0

#37 0xb549a9f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#38 0xb54c12e7 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#39 0xb54c131b in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#40 0xb4c38510 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#41 0xb4c3bcc3 in g_main_context_dispatch () from 
/lib/i386-linux-gnu/libglib-2.0.so.0

#42 0xb4c3c0d9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#43 0xb4c3c489 in g_main_loop_run () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#44 0xb5b9b1b5 in gtk_main () from 
/usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0

#45 0x0804f5aa in main ()
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] surf segmentation fault

[Joachim Fahrner]

Am 18.03.2017 um 23:41 schrieb Steve Litt:

> 64 bit, and it's Surf 0.7. 

That confirms my theory that only 32 bit systems are affected.
Do you have a 32 bit system at hand and can proove that?

-- 
Mit besten Grüßen
Joachim Fahrner

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