Re: [DNG] Firefox-esr freezes ASCII
On Fri, Jul 12, 2019 at 02:02:02PM -0700, spiralofhope wrote: > On Tue, 9 Jul 2019 06:24:56 -0400 > fsmithred via Dng wrote: > > > What I do when it starts to slow down is ctrl-alt-F2, log in and > > start killing programs. Thunderbird is usually on that kill list, > > because it takes a lot of ram, too. If I wait too long to do that, it > > freezes. At some point, even sysrq keys won't work. > > I recalled a program which automatically kills tasks which are being > hogs, which is an extreme and not-recommended workaround. I couldn't > find it offhand, but I found other solutions out there which act like > that. In theory, a monitoring script could be made for this, and even > made smart enough prompt for action (with a timeout for automatic > action). Would that be the oom-killer? > > > Also, would ulimit be helpful? > > https://ss64.com/bash/ulimit.html > ___ > 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] Systemd depends on random numbers in order to work properly
Quoting spiralofhope (spiralofh...@spiralofhope.com): > On Tue, 9 Jul 2019 07:07:20 -0400 > Steve Litt wrote: > > > I loosely attach my mouse to my stationary bike in such a way that the > > mouse's LED shines on the stationary bike's belt, building up entropy. > > Within 10 seconds boot begins! > > I would prefer a steam car-style hand crank. Somehow, I feel that there ought to be chrome slacks somewhere in there. https://www.hyundaiperformance.com/forums/off-topic/51471-car-drivers-best-review-ever-caddilac.html ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What do you think of Wayland?
On Fri, Jul 12, 2019 at 11:36:17PM +0200, Dr. Nikolaus Klepp wrote: > Anno domini 2019 Fri, 12 Jul 13:53:20 -0400 > Steve Litt scripsit: > > Hi all, > > > > What do you think of Wayland? I hear Buster now defaults to Wayland. > Another step in windosification of linux. It seems obvious that big players would have a powerful motivations to influence the software that millions of people run. It is one of the alternatives for explaining the famous bug in Debian's pseudorandom number generator. Here's a good write up with incisive comments. https://freedom-to-tinker.com/2013/09/20/software-transparency-debian-openssl-bug/ > Has the > "middle-mousebutton-press does not copy text" been fixed > at last? > Can it do display over network now? No, but one of the proposals is to do it the way X does. Quote from Wikipedia:[1] Initial versions of Wayland have not provided network transparency, though Høgsberg noted in 2010 that network transparency is possible.[12] It was attempted as a Google Summer of Code project in 2011, but was not successful.[13] Adam Jackson has envisioned providing remote access to a Wayland application by either "pixel-scraping" (like VNC) or getting it to send a "rendering command stream" across the network (as in RDP, SPICE or X11).[14] As of early 2013, Høgsberg is experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor.[15][16] In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland.[17] ISTR hearing assertions early on that network transparency was not a priority for the Wayland project, and thinking that it didn't seem like a good direction. > Dont know if wayland is compatible to anything not gnome. But I'm not verry > eger to try. Why throw-away a protocol stack that solves the problem? Why not just fix X? Keith Packard and the xorg team did a remarkable job of modularizing X, why not build on that? Of course anyone has the freedom to re-architect something, and perhaps network transparency will be neatly solved. I for one don't need to be their bug tester. I've scarcely noticed anything with X to complain about. Quoting wikipedia again[2] Unlike most earlier display protocols, X was specifically designed to be used over network connections rather than on an integral or attached display device. And here from askubuntu[3]: Wayland is a lot less complex than X which should make it easier to maintain - although some of this simplicity comes from pushing the complexity (eg: how to actually draw onto that buffer, network transparency) to other layers of the stack. By making clients responsible for all of their rendering the clients can be smarter about things things like double-buffering. Existing xclients will not work, and although those based on GTK+ or Qt *may* be supported in future. To paraphrase in doggerl: Wayland's like a step back counting on a future hack. Those less geeky won't think twice Hearing all is new and nice. They'd be more choosy what they run Knowing who's behind the fun 1. https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) 2. https://en.wikipedia.org/wiki/X_Window_System 3. https://askubuntu.com/questions/11537/why-is-wayland-better -- Joel Roth "Welcome to the World Heat Bank, where we store your waste energy and return it with interest." ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] removed encrypted file system? was date of publication of beowulf
On Fri, Jul 12, 2019 at 01:33:22PM -0400, Steve Litt wrote: > On Fri, 12 Jul 2019 12:00:35 -0400 > Hendrik Boom wrote: > > > > Debian actually removed one of the encrypted file systems because it > > turns out to be incompatible with systemd. > > Are you absolutely positive this is true? I was unable to find such a > thing with a 10 minute web search. Could you please tell us the name of > the encrypted filesystem and a URL describing the removal? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854 Debian Bug report logs - #765854 ecryptfs-utils: Private directory not automatically unmounted anymore on logout It seems there's poor interaction between ecryptfs-utils and user logout. Specifically, that the encrypted volume remains mounted. There's a long discussion how to tweak it and systemd to make it work, and it looks like they eventually just gave up. Maybe someone else can understand th problem in more detail than I can. The remocal is mentioned in section 5.1.9. Noteworthy obsolete packages, https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#noteworthy-obsolete-packages -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Systemd depends on random numbers in order to work properly
On Tue, 9 Jul 2019 07:07:20 -0400 Steve Litt wrote: > I loosely attach my mouse to my stationary bike in such a way that the > mouse's LED shines on the stationary bike's belt, building up entropy. > Within 10 seconds boot begins! I would prefer a steam car-style hand crank. I smell a Kickstarter. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What do you think of Wayland?
Anno domini 2019 Fri, 12 Jul 13:53:20 -0400 Steve Litt scripsit: > Hi all, > > What do you think of Wayland? I hear Buster now defaults to Wayland. Another step in windosification of linux. Has the "middle-mousebutton-press does not copy text" been fixed at last? Can it do display over network now? > I've always been under the impression that Wayland is just another > overly complexified mess from Redhat and Freedesktop.org. Dont know if wayland is compatible to anything not gnome. But I'm not verry eger to try. Nik > > SteveT > > Steve Litt > July 2019 featured book: Troubleshooting Techniques > of the Successful Technologist > http://www.troubleshooters.com/techniques > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > -- 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] removed encrypted file system? was date of publication of beowulf
On Fri, 12 Jul 2019 14:41:18 -0400 Hendrik Boom wrote: > Due to #765854 ecryptfs-utils has been removed from > Buster. http://debian.2.n7.nabble.com/Bug-928956-Document-removal-of-ecryptfs-utils-from-Buster-td4512502.html https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854 systemd-user doesn't properly close its PAM session https://github.com/systemd/systemd/issues/8598 -- I just happened to have removed reliance on it to simplify my system. I'm now glad I did. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What do you think of Wayland?
On Fri, 12 Jul 2019 13:53:20 -0400 Steve Litt wrote: > What do you think of Wayland? I hear Buster now defaults to Wayland. I had been waiting for it to come out into mainstream use for some time, because of its supposed solutions to video playback screen tearing issues. I've always assumed Devuan will eventually adopt it. > ... overly complexified mess from Redhat ... Aw shit.. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Firefox-esr freezes ASCII
On Tue, 9 Jul 2019 06:24:56 -0400 fsmithred via Dng wrote: > What I do when it starts to slow down is ctrl-alt-F2, log in and > start killing programs. Thunderbird is usually on that kill list, > because it takes a lot of ram, too. If I wait too long to do that, it > freezes. At some point, even sysrq keys won't work. I recalled a program which automatically kills tasks which are being hogs, which is an extreme and not-recommended workaround. I couldn't find it offhand, but I found other solutions out there which act like that. In theory, a monitoring script could be made for this, and even made smart enough prompt for action (with a timeout for automatic action). Also, would ulimit be helpful? https://ss64.com/bash/ulimit.html ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] removed encrypted file system? was date of publication of beowulf
On Fri, Jul 12, 2019 at 01:33:22PM -0400, Steve Litt wrote: > On Fri, 12 Jul 2019 12:00:35 -0400 > Hendrik Boom wrote: > > > > Debian actually removed one of the encrypted file systems because it > > turns out to be incompatible with systemd. > > Are you absolutely positive this is true? I was unable to find such a > thing with a 10 minute web search. Could you please tell us the name of > the encrypted filesystem and a URL describing the removal? Found a related message. I quote: Date: Mon, 13 May 2019 23:16:40 +0200 From: Daniel Lange To: Debian Bug Tracking System Subject: Bug#928956: Document removal of ecryptfs-utils from Buster User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 Package: release-notes Severity: important Due to #765854 ecryptfs-utils has been removed from Buster. The kernel module (ecryptfs.ko) is still built but depending on the upgrade path users will be unable to mount their encrypted home directories (pam module, ecryptfs-mount-private missing). So they should probably be strongly advised to not upgrade. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] removed encrypted file system? was date of publication of beowulf
On Fri, Jul 12, 2019 at 01:33:22PM -0400, Steve Litt wrote: > On Fri, 12 Jul 2019 12:00:35 -0400 > Hendrik Boom wrote: > > > > Debian actually removed one of the encrypted file systems because it > > turns out to be incompatible with systemd. > > Are you absolutely positive this is true? I was unable to find such a > thing with a 10 minute web search. Could you please tell us the name of > the encrypted filesystem and a URL describing the removal? I will look for it. It was discussed on the Debian documentation mailing list, where they were figuring out how to document it. -- hendrik > > Thanks, > > SteveT > > Steve Litt > July 2019 featured book: Troubleshooting Techniques > of the Successful Technologist > http://www.troubleshooters.com/techniques > ___ > 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
[DNG] What do you think of Wayland?
Hi all, What do you think of Wayland? I hear Buster now defaults to Wayland. I've always been under the impression that Wayland is just another overly complexified mess from Redhat and Freedesktop.org. SteveT Steve Litt July 2019 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] removed encrypted file system? was date of publication of beowulf
On Fri, 12 Jul 2019 12:00:35 -0400 Hendrik Boom wrote: > Debian actually removed one of the encrypted file systems because it > turns out to be incompatible with systemd. Are you absolutely positive this is true? I was unable to find such a thing with a 10 minute web search. Could you please tell us the name of the encrypted filesystem and a URL describing the removal? Thanks, SteveT Steve Litt July 2019 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] date of publication of beowulf
On Fri, Jul 12, 2019 at 05:40:54PM +0200, Basati wrote: > hello > > Can anyone tell me if there is an approximate date for the publication of > beowulf? > > buster has been published as stable, now it's beowulf's turn no? It will be released when it's ready. And it won't be ready until the developers agree that all the damage caused by systemd has been undone. Debian actually removed one of the encrypted file systems because it turns out to be incompatible with systemd. Fortunately it isn't the one I use. I've been running beowulf for months now. But I upgraded from ascii and as a result haven't really tested the installer. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] date of publication of beowulf
On Fri, Jul 12, 2019 at 05:40:54PM +0200, Basati wrote: > hello > > Can anyone tell me if there is an approximate date for the publication of > beowulf? The rule is same as that of Debian's release team: Quando paratus est. (Did this altum videtur enough? :p) > buster has been published as stable, now it's beowulf's turn no? Meh, I've moved to Bullseye almost a week ago :p Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ According to recent spams, "all my email accounts are owned ⢿⡄⠘⠷⠚⠋ by a hacker". So what's the problem? ⠈⠳⣄ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] date of publication of beowulf
hello Can anyone tell me if there is an approximate date for the publication of beowulf? buster has been published as stable, now it's beowulf's turn no? Greetings Basati ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] dns vs connection manager
Quoting Steve Litt (sl...@troubleshooters.com):
> Yes, and I think that's outdated.
You can configure your DHCP client software to _not_ use nameserver IPs
sent by the DHCPd and instead use locally defined ones. If using
ISC's dhclient, set
supersede domain-name-servers ip-address [, ip-address... ];
or
prepend domain-name-servers ip-address [, ip-address... ];
in dhclient.conf in the section for the interface concerned.
('supersede' means ignore what the DHCPd sends for resolv.conf namserver
IPs entirely. 'prepend' means accept them, but put the indicated IPs
as a line above any received from the DHCPd, so as to be used in
preference if available.)
Or, a different way, create a 'hook' file to signal that updates to
/etc/resolv.conf should be ignored: Create 'hook' shell script
/etc/dhcp/dhclient-enter-hooks.d/nodnsupdate to contain
#!/bin/sh
make_resolv_conf(){
:
}
Then, make executable by doing
# chmod +x /etc/dhcp/dhclient-enter-hooks.d/nodnsupdate
The above replaces dhclient's make_resolv_conf() function with a NO-OP
function.
A different conffile incantation would be required if you were using
dhcpcd, and yet a third for the 'pump' DHCP client. So, consult
docs for your choice of DHCP client software.
> Today, you can do one of these two
> things to guarantee you'll never need to change resolv.conf again:
>
> 1) Set resolv.conf to use two public DNS servers
>
> 2) Put a recursive resolver right on your computer. I use unbound.
Or #3, use resolvconf to manage the contents of the file.
http://linuxmafia.com/faq/Network_Other/resolvconf.html
> #2 has the advantage that you can put an authoritative server on there
> also, and then when you're at home or whatever you have DNS on your LAN
> too.
Hmm, either I'm misreading this suggestion or you are forgetting that
only one daemon process may bind to port 53 (DNS) on a single IP
address. E.g., if Unbound is running on your IP, it'll grab port 53.
If you then subsequently try to launch an authoritative nameserver such
as NSD on the same IP, it'll try to bind to 53, fail, and terminate.
There are workarounds if you're _determined_ to run both recursive and
authoritative servers sharing an IP, such as having dnsproxy bind to 53
on a public-facing IP address, and have it forward queries as
appropriate to either the recursive or authoritative server running each
on its own high-numbered port on 127.0.0.1 (localhost).
Or you could have the authoritative server bound to 53 on the
public-facing IP address, and the recursive server bound to 53 on
127.0.0.1 (localhost) -- at the cost (obviously) of restricting the
recursive server to local queries only.
In a LAN setup, it's best practices to run recursive service on a
well-protected inside machine, thus separating it from authoritative
nameservice. (Recursive servers are at risk of cache poisoning; you
want to try to control who and what sends them queries.)
(Most Dng users would have simple use-cases for which they'd have no
reason to run an authoritative nameserver, though. If you're not
publishing your own or a friend's domain's DNS to the public from a
fixed IP address, ignore anything about providing authoritative
nameservice, as you'll not be doing it.)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
