Re: any gui for lm-sensors?

[Gene Heskett]

On Wednesday 08 July 2020 22:52:22 Long Wind wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!

gkrellm and helpers. Small, still shows everything.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Putting a Debian Repository in a Mint 20 System for Chromium

[Tom Dial]

On 7/8/20 18:11, Kenneth Parker wrote:
> Hello,
> 
> [background]
> I happily run Chromium under, both Debian Buster and Devuan Ascii (non
> SystemD equivalent to Stretch).  It comes with proper .deb files and
> installs quite well, thank you very much.
> 
> Somehow, Ubuntu decided to make Chromium a Snap Package.  (I'm reading the
> articles about it now.  I don't like it).
> 
> I am not running Ubuntu (except as a Cloud Server, but that will change
> eventually to Debian).
> 
> *But*, I decided to install Mint 20, to help out a Friend, who is doing
> some work I support under it.  Mint hates Snap, even though it's based on
> Ubuntu.  However, they didn't take the step themselves to put the Debian
> Repositories in for Chromium.
> [/background]
> 
> Now, when running Debian Systems, people caution against mixing
> Repositories from other Distributions.  Does this work the other way?
> Would I get into trouble, adding the Buster (or Bullseye) Repositories,
> only for installing Chromium from it?

I also am not a fan of things like Snap. But for ample reasons it
probably would be a rather bad idea to throw a Debian repository into
the Ubuntu-based Mint sources.list.

Linux Mint Debian Edition might be a better choice if you do not rely on
packages on Ubuntu features Debian does not have. The present release
live dvd appears based on Debian 10.2; /etc/os-release shows:

PRETTY_NAME="LMDE 4 (debbie)"
NAME="LMDE"
VERSION_ID="4"
VERSION="4 (debbie)"
ID=linuxmint
ID_LIKE=debian
HOME_URL="https://www.linuxmint.com/";
SUPPORT_URL="https://forums.linuxmint.com/";
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/";
PRIVACY_POLICY_URL="https://www.linuxmint.com/";
VERSION_CODENAME=debbie
DEBIAN_CODENAME=busters

> 
> I'm asking here, because I'm sure people here have experience
> using derivatives, such as Ubuntu and Mint.  (And yes, Mint has a Forum,
> but I got into trouble, for "suggesting" that they provide an Expert Text
> Mode Install for Mint, like Debian does.  Yes, I needed help with the
> Ubiquity System Mint uses for its Install).
> 
> [Humor]
> There have been discussions about not creating a FrankenDebian System.  How
> about FrankenMint or FrankenUbuntu one?
> [/Humor]
> 
> Thanks in advance,
> 
> Kenneth Parker
> 

Regards,
Tom Dial

Re: any gui for lm-sensors?

[Long Wind]

 
Thank Charles! 
xsensors seems best for me 
On Thursday, July 9, 2020, 12:10:27 AM EDT, Charles Curley 
 wrote:  
 
 On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

Your desktop may have a suitable addon. For XFCE, xfce4-sensors-plugin.
Otherwise, run

apt-cache search sensors

and see if any of that gives you ideas.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

  

Re: any gui for lm-sensors?

[Tu Can]

On [4], 2020-07-09 at 02:52 +, Long Wind wrote:
> i want a small app that show cpu temperature
> which package shall i install?
> Thanks!
> 
conky, as a background of desktop. not only cpu informaiton. Here is my
configuration file[1].

[1]https://github.com/bestucan/conky

Re: any gui for lm-sensors?

[Charles Curley]

On Thu, 9 Jul 2020 02:52:22 + (UTC)
Long Wind  wrote:

> i want a small app that show cpu temperaturewhich package shall i
> install?Thanks!
> 

Your desktop may have a suitable addon. For XFCE, xfce4-sensors-plugin.
Otherwise, run

apt-cache search sensors

and see if any of that gives you ideas.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: any gui for lm-sensors?

[David Christensen]

On 2020-07-08 19:52, Long Wind wrote:

i want a small app that show cpu temperaturewhich package shall i 
install?Thanks!


I use Xfce with the CPU Frequency Monitor, CPU Graph, and Sensor panel 
plug-ins.



David

Re: any gui for lm-sensors?

[Joe Pfeiffer]

Long Wind  writes:

> i want a small app that show cpu temperature
> which package shall i install?
> Thanks!

I've been using gkrellm to show quite a bit of system information
(including temperatures) for years and years now.

Re: minimizing buffer size (i.e. page cache) for bulk copy/rsync -- Re: Swappiness in Buster

[Zenaan Harkness]

- Forwarded message -

‐‐‐ Original Message ‐‐‐
On Wednesday, July 8, 2020 7:53 AM, Zenaan Harkness  wrote:

> Anyone here able to answer this annoying buffer issue on bulk copies?

[ paraphrasing: page cache gets swamped by bulk copy, driving interactive 
desktop applications to heavy latency... ]

use an LD_PRELOAD hack to force mlock() on the apps you want to keep 
interactive:

https://stackoverflow.com/questions/37818335/mlock-a-program-from-a-wrapper

---


If you have the sources for the program, add a command-line option so that the 
program calls mlockall(MCL_CURRENT | MCL_FUTURE) at some point. That locks it 
in memory.

If you want to control the address spaces the kernel loads the program into, 
you need to delve into kernel internals. Most likely, there is no reason to do 
so; only people with really funky hardware would.

If you don't have the sources, or don't want to recompile the program, then you 
can create a dynamic library that executes the command, and inject it into the 
process via LD_PRELOAD.

Save the following as lockall.c:

#include 
#include 
#include 
#include 
#include 

static void wrerr(const char *p)
{
if (p) {
const char *q = p + strlen(p);
ssize_t n;

while (p < q) {
n = write(STDERR_FILENO, p, (size_t)(q - p));
if (n > 0)
p += n;
else
if (n != -1 || errno != EINTR)
return;
}
}
}

static void init(void) __attribute__((constructor));
static void init(void)
{
int saved_errno = errno;

if (mlockall(MCL_CURRENT | MCL_FUTURE) == -1) {
const char *errmsg = strerror(errno);
wrerr("Cannot lock all memory: ");
wrerr(errmsg);
wrerr(".\n");
exit(127);
} else
wrerr("All memory locked.\n");

errno = saved_errno;
}

Compile it to a dynamic library liblockall.so using

gcc -Wall -O2 -fPIC -shared lockall.c -Wl,-soname,liblockall.so -o liblockall.so

Install the library somewhere typical, for example

sudo install -o 0 -g 0 -m 0664 liblockall.so /usr/lib/

so you can run any binary, and lock it into memory, using

LD_PRELOAD=liblockall.so binary arguments..

If you install the library somewhere else (not listed in /etc/ld.so.conf), 
you'll need to specify path to the library, like

LD_PRELOAD=/usr/lib/liblockall.so binary arguments..

Typically, you'll see the message Cannot lock all memory: Cannot allocate 
memory. printed by the interposed library, when running commands as a normal 
user. (The superuser, or root, typically has no such limit.) This is because 
for obvious reasons, most Linux distributions limit the amount of memory an 
unprivileged user can lock into memory; this is the RLIMIT_MEMLOCK resource 
limit. Run ulimit -l to see the per-process resource limits currently set (for 
the current user, obviously).

I suggest you set a suitable limit of how much memory the process can run, 
running e.g. ulimit -l 16384 bash-built-in before executing the (to set the 
limit to 16384*1024 bytes, or 16 MiB), if running as superuser (root). If the 
process leaks memory, instead of crashing your machine (because it locked all 
available memory), the process will die (from SIGSEGV) if it exceeds the limit. 
That is, you'd start your process using

ulimit -l 16384
LD_PRELOAD=/usr/lib/liblockall.so binary arguments..

if using Bash or dash shell.

If running as a dedicated user, most distributions use the pam_limits.so PAM 
module to set the resource limits "automatically". The limits are listed either 
in the /etc/security/limits.conf file, or in a file in the 
/etc/security/limits.d/ subdirectory, using this format; the memlock item 
specifies the amount of memory each process can lock, in units of 1024 bytes. 
So, if your service runs as user mydev, and you wish to allow the user to lock 
up to 16 megabytes = 16384*1024 bytes per process, then add line mydev - 
memlock 16384 into /etc/security/limits.conf or 
/etc/security/limits.d/mydev.conf, whichever your Linux distribution 
prefers/suggests.

Prior to PAM, shadow-utils were used to control the resource limits. The 
memlock resource limit is specified in units of 1024 bytes; a limit of 16 
megabytes would be set using M16384. So, if using shadow-utils instead of PAM, 
adding line mydev M16384 (followed by whatever the other limits you wish to 
specify) to /etc/limits should do the trick.

---end-cut---

best regards,

- End forwarded message -

Re: Using .XCompose

[Zenaan Harkness]

On Wed, Jul 08, 2020 at 07:14:33PM -0500, David Wright wrote:

> > I was just trying to find out the reason why the 'composting' was
> > not working. I tried including the modifier name and also without
> > it. I tried moving the key to the first layer of keyboard layout
> > (without shift or other modifiers). Even that was not working.
> 
> I think you're now talking about the /usr/share/X11/xkb/ files,
> and overriding them in /etc/. I don't touch those, and can't help you
> there. I read them, to help in configuring /etc/default/ files, but
> no more than that.

I added a new "FunkyZen" layout file to /usr/share/X11/xkb/, a modification of 
the US keymap I think.

Can we create new layouts by just adding a file to /etc ??


> I should have said that the usual way to write this file is to run
> # dpkg-reconfigure keyboard-configuration
> (and that command can also be run after editing it in order to
> validate/correct it). I should also add that in my experience,
> it's best done in a VC, without an X session even running.

Ooh!  Now _that_ could be highly useful next time he (this friend of mine who 
seems to be oddly wearing a brown paper bag right now) looks at my, I mean his 
custom keyboard layout...


> (In systemd, there's also this mysterious command
> # service keyboard-setup restart
> about which I know nothing. I've never used it.)

Must investigate.

If my friend were to write an ad hock end user custom keyboard layout 
customizer, what would be the minimal set of perms required to do its job?  (My 
friend does not use `sudo` you see...)

> > and my .XCompose file now is 
> > include "%L" 
> >    : "✄"   U2704 # WHITE SCISSORS
> > 
> > However, when I press Caps Lock followed by s and then x or if I
> > keep the Caps Lock pressed while I press s and x in sequence, I
> > don't get scissors. I get S and X.
> 
> That appears to indicate that CapsLock is not your Compose Key, but is
> behaving as normal, turning s and x into S and X.

Although various desktops have GUIs to choose Compose key, it is Better ™©® to 
set this at a lower level so it also kinda works in the Linux console.  I guess 
my friend's question is how best to arrange the perms/sudo side of things for a 
GUI that wants to make this easy for end users?

Re: Using .XCompose

[Zenaan Harkness]

On Wed, Jul 08, 2020 at 04:37:19PM +, Ajith R wrote:
> Hi Zenaan,
> 
> > Under the "Layout" tab, I have the option for "Compose key" - this is a 
> > drop down list, and I chose the "Scroll Lock" key as my compose key.
> 
> 
> Similar options are there for KDE too. I tried setting the Compose key from 
> the KDE settings menu after trying xmodmap -e "keysym Caps_Lock = Multi_key" 
> suggested by Greg. My .XCompose file is:
> include "%L"
>    : "✄"   U2704 # WHITE SCISSORS
> 
> Now, things are even more strange. When I press the Caps Lock, a strange 
> character appears. (I copy pasted it, searched the net and found it to be 
> unicode compose character.) Then when I type s, the Caps Lock light gets 
> switched on and the character S (caps) appears on screen. Then when I type X, 
> the compose character and S become invisible and x/X doesn't appear. When I 
> change focus to another window, the terminal in which I was typing shows the 
> compose character and S.
> 
> This behaviour has not changed after I unchecked the settings through KDE 
> settings menu, after restarting computer, re-issuing xmodmap command or 
> changing the layout to us. The same sequence is seen with typing in Kate as 
> well. Even when I use Scroll Lock as the compose key, the situation is only 
> different in that the s is not capitalised.
> 
> Any idea what might be wrong?

It sounds like something is fundamentally wrong with your keymap.

I suggest starting again, resetting everything back to your chosen defaults at 
install - reset your modified keymap file back to whatever you copied to begin 
the exercise, and test that compose is working as it should.

Then, make no more than a single change, apply and test that single change.  
Don't move forward till the one change is working.

That's what I did (although it's been a 2 or 3 years since I dabbled) - I had 
one tiny little brace missing at one stage, and when you don't see it, you just 
don't see it, so after that I brutally realigned everything with obnoxious 
spaces, so that all tha braces, and commas, lined up - THAT solved the 
accidental missing brace which never bit me again :/

Re: Putting a Debian Repository in a Mint 20 System for Chromium

[Kenneth Parker]

On Wed, Jul 8, 2020 at 8:47 PM Dan Ritter  wrote:

> Kenneth Parker wrote:
> > I happily run Chromium under, both Debian Buster and Devuan Ascii (non
> > SystemD equivalent to Stretch).  It comes with proper .deb files and
> > installs quite well, thank you very much.
>
> Chromium is the open-source version of Chrome. You can also get
> Chrome itself from Google, if that's what you want. That's not
> an open-source package.
>
> > Somehow, Ubuntu decided to make Chromium a Snap Package.  (I'm reading
> the
> > articles about it now.  I don't like it).
> >
> > *But*, I decided to install Mint 20, to help out a Friend, who is doing
> > some work I support under it.  Mint hates Snap, even though it's based on
> > Ubuntu.  However, they didn't take the step themselves to put the Debian
> > Repositories in for Chromium.
> > [/background]
> >
> > Now, when running Debian Systems, people caution against mixing
> > Repositories from other Distributions.  Does this work the other way?
> > Would I get into trouble, adding the Buster (or Bullseye) Repositories,
> > only for installing Chromium from it?
>
> The underlying reason for avoiding mixing repos is that you
> create a system where things stop working and you might not be
> able to get back to usable.
>
> This is least likely to happen when you install a repo that only
> adds an application package: if the package doesn't work, you
> know what went wrong and how to remove it.
>

In my earlier search, I missed  a rather important article [1] in the Mint
Install Guide which, among other things, mentions "Apt Pinning", and even
does a Shoutout to Debian Buster.  I think this "Technique" will work for
me.

It is most likely to happen when you install a repo with lots of
> packages, especially libraries that many other packages depend
> on.
>
> > [Humor]
> > There have been discussions about not creating a FrankenDebian System.
> How
> > about FrankenMint or FrankenUbuntu one?
> > [/Humor]
>
> In the end, you are responsible for what you do. When you know
> what you are doing, it is much safer to experiment than when you
> don't know what you are doing.
>

+1  --  We are *absolutely* responsible for what we do!

You might try getting the Debian Chromium package directly,
> without a repo. It won't update automatically, but that might
> also be what you want.
>

That will also be an option if I have problems.  But I'm going to try the
"Apt Pinning" technique, mentioned above and in this Article.  Apparently,
it limits what is installed from a particular Repository, so that I don't
"Busterize Mint".

[1] https://linuxmint-user-guide.readthedocs.io/en/latest/chromium.html

Thank you, by the way!

Kenneth Parker

Re: Putting a Debian Repository in a Mint 20 System for Chromium

[Dan Ritter]

Kenneth Parker wrote: 
> I happily run Chromium under, both Debian Buster and Devuan Ascii (non
> SystemD equivalent to Stretch).  It comes with proper .deb files and
> installs quite well, thank you very much.

Chromium is the open-source version of Chrome. You can also get
Chrome itself from Google, if that's what you want. That's not
an open-source package.

> Somehow, Ubuntu decided to make Chromium a Snap Package.  (I'm reading the
> articles about it now.  I don't like it).
> 
> *But*, I decided to install Mint 20, to help out a Friend, who is doing
> some work I support under it.  Mint hates Snap, even though it's based on
> Ubuntu.  However, they didn't take the step themselves to put the Debian
> Repositories in for Chromium.
> [/background]
> 
> Now, when running Debian Systems, people caution against mixing
> Repositories from other Distributions.  Does this work the other way?
> Would I get into trouble, adding the Buster (or Bullseye) Repositories,
> only for installing Chromium from it?

The underlying reason for avoiding mixing repos is that you
create a system where things stop working and you might not be
able to get back to usable.

This is least likely to happen when you install a repo that only
adds an application package: if the package doesn't work, you
know what went wrong and how to remove it.

It is most likely to happen when you install a repo with lots of
packages, especially libraries that many other packages depend
on.

> [Humor]
> There have been discussions about not creating a FrankenDebian System.  How
> about FrankenMint or FrankenUbuntu one?
> [/Humor]

In the end, you are responsible for what you do. When you know
what you are doing, it is much safer to experiment than when you
don't know what you are doing.

You might try getting the Debian Chromium package directly,
without a repo. It won't update automatically, but that might
also be what you want.

-dsr-

Re: Lost usb wifi device

[Dan Ritter]

Gregory Sharp wrote: 
> Hi all,
> 
> My usb wifi connection has been working for two years, and it just stopped 
> and can't figure out why.  This is on Debian testing.  Help!
> 

If you boot with a Debian stable live-USB or similar, does it
work?

-dsr-

Re: Using .XCompose

[David Wright]

Sorry if the format looks a mess, but it's a consequence of replying to HTML.

On Tue 07 Jul 2020 at 09:44:38 (+), Ajith R wrote:

> I was looking at XCompose(3). Thanks for pointing out the mistake.

It wasn't a mistake on your part. It was pointed out to me that
section 3 has an alias redirecting to the real man page, which is
actually still in the right place, section 5. You just followed that
link. I was worried that you might have been reading a real section 3
man page, most of which are incomprehensible to us mere mortals.

> > As I understand .XCompose, it is designed for "compositing", […]

> I understand that. My letter is in the 'shift' set of
> keystrokes. That was the reason I included it. Moreover, the Compose
> manual page states that 'Each event consists of a specified input
> keysym, and optional modifier states:
> [([!] ([~] MODIFIER)...) | None] ". '

Sure. But typically, for ordinary letter keys, you would expect each
to have its own keysym when shifted. Thus (using English) you see
definitions sequences like

   : "©"   copyright # COPYRIGHT SIGN
   : "©"   copyright # COPYRIGHT SIGN
   : "©"   copyright # COPYRIGHT SIGN
   : "©"   copyright # COPYRIGHT SIGN
   : "©"   copyright # COPYRIGHT SIGN
   : "©"   copyright # COPYRIGHT SIGN

Obviously, I'm struggling when it comes to your own example as I don't
know how these characters relate to one another. So my examples will
be using Latin characters.

It's perfectly possible to write compositions like these:

 : "xx"
 : "XX"

where X is shifted x.

You can even have:

  : "yes"

but the problem is that whenever you type the key y, the system will
wait for another character to be typed. If you want to type the letter
y, you have to type y y Rubout Rubout. For the letter X, you have to
type X Rubout. Not very satisfactory.

What appears on the right is flexible, but the left part, before the
colon, is more constrained. To repeat myself, you should probably look
at the system file for your own locale (and perhaps others) to see
what they use. My own, /usr/share/X11/locale/en_US.UTF-8/Compose, has
the letters (in both cases) and digits (including  as well as <3>,
surprisingly), and punctuation keys by name ( etc). My Compose
key (CapsLock) is .

I also see keys that I have no idea about how to generate them, like
   and most of the
Unicode-defined ones. But noticeable is the fact that the *first* key is
almost always  or . That's because
those few keys become unusable on their own, dead. (There are also 9
oddities that mean nothing to me.)

What I don't see are any modifiers like shift and ctrl. In fact, I
found none in /usr/share/X11/locale/*/Compose on my system. Perhaps
yours do, in which case you can follow their style. I can't help
you there.

> I was just trying to find out the reason why the 'composting' was
> not working. I tried including the modifier name and also without
> it. I tried moving the key to the first layer of keyboard layout
> (without shift or other modifiers). Even that was not working.

I think you're now talking about the /usr/share/X11/xkb/ files,
and overriding them in /etc/. I don't touch those, and can't help you
there. I read them, to help in configuring /etc/default/ files, but
no more than that.

> So, I
> was wondering if there was a syntax error in the way I was
> specifying my requirement. I understand the use of Compose key. But,
> I was not trying the usual 'composting' (by means of a compose
> key). I  want one character to be replaced with its geminate form
> whenever it is typed. If the keyboard layout specification allowed
> more than one character for a keystroke, I wouldn't have needed
> it. Hence the need for Compose mechanism. A similar approach is
> explained here https://dominiko.livejournal.com/20206.html . However
> in it, the author has defined a personal use Unicode character, but
> I use one of the Unicode defined characters.

If you're willing to lose the normal function of the key, then as
shown above, you can turn any keystroke into a string.

> In the symbol file, he had used key
>  { type[group1] = "FOUR_LEVEL_C_HWERTY", [ UF8FD, UF8FE, UF8FF, 
> Greek_alpha ] };
> I didn't understand the use of type[group1 = "..."], but thought
> that it was not essential. Anyway, the layout is working as expected
> in that the characters returned by layout is as defined.

No idea about that stuff.

> The compose mechanism is not working.

Syntax errors are one possibility. I don't know how and when they are
handled. Another is making changes have any effect. (In the past,
I've edited the file in a VC, and started X from another VC after any
changes have been saved.)

A third is that every recipe at the left side must not entirely
include any other. Hence:

: "—"   U201

Putting a Debian Repository in a Mint 20 System for Chromium

[Kenneth Parker]

Hello,

[background]
I happily run Chromium under, both Debian Buster and Devuan Ascii (non
SystemD equivalent to Stretch).  It comes with proper .deb files and
installs quite well, thank you very much.

Somehow, Ubuntu decided to make Chromium a Snap Package.  (I'm reading the
articles about it now.  I don't like it).

I am not running Ubuntu (except as a Cloud Server, but that will change
eventually to Debian).

*But*, I decided to install Mint 20, to help out a Friend, who is doing
some work I support under it.  Mint hates Snap, even though it's based on
Ubuntu.  However, they didn't take the step themselves to put the Debian
Repositories in for Chromium.
[/background]

Now, when running Debian Systems, people caution against mixing
Repositories from other Distributions.  Does this work the other way?
Would I get into trouble, adding the Buster (or Bullseye) Repositories,
only for installing Chromium from it?

I'm asking here, because I'm sure people here have experience
using derivatives, such as Ubuntu and Mint.  (And yes, Mint has a Forum,
but I got into trouble, for "suggesting" that they provide an Expert Text
Mode Install for Mint, like Debian does.  Yes, I needed help with the
Ubiquity System Mint uses for its Install).

[Humor]
There have been discussions about not creating a FrankenDebian System.  How
about FrankenMint or FrankenUbuntu one?
[/Humor]

Thanks in advance,

Kenneth Parker

Re: Firefox non-ESR update needed

[Richard Hector]

On 8/07/20 5:42 am, John Hasler wrote:
> Look at
> 
> https://backports.debian.org/
> 
> Note that for Firefox you need to go to
> 
> https://mozilla.debian.net/
> 

I think you'll find that mozilla.debian.net is a bit out of date - it
only goes up to stretch.

Richard

Re: Using .XCompose

[Ajith R]

Hi Zenaan,

> Under the "Layout" tab, I have the option for "Compose key" - this is a drop 
> down list, and I chose the "Scroll Lock" key as my compose key.


Similar options are there for KDE too. I tried setting the Compose key from the 
KDE settings menu after trying xmodmap -e "keysym Caps_Lock = Multi_key" 
suggested by Greg. My .XCompose file is:
include "%L"
   : "✄"   U2704 # WHITE SCISSORS

Now, things are even more strange. When I press the Caps Lock, a strange 
character appears. (I copy pasted it, searched the net and found it to be 
unicode compose character.) Then when I type s, the Caps Lock light gets 
switched on and the character S (caps) appears on screen. Then when I type X, 
the compose character and S become invisible and x/X doesn't appear. When I 
change focus to another window, the terminal in which I was typing shows the 
compose character and S.

This behaviour has not changed after I unchecked the settings through KDE 
settings menu, after restarting computer, re-issuing xmodmap command or 
changing the layout to us. The same sequence is seen with typing in Kate as 
well. Even when I use Scroll Lock as the compose key, the situation is only 
different in that the s is not capitalised.

Any idea what might be wrong?
Thanks,
ajith

Re: systemd-nspawn networking inside VirtualBox VM

[Didar Hossain]

On Wed, Jul 08, 2020 at 07:20:18AM +0200, Alexandre Rossi wrote:
> Hi,
> 
> > > since I am not well educated about macvlan, ipvlan, I could not get the
> > > networking working at all. I would like to avoid using
> > > "systemd-networkd/systemd-resolvd" especially on the Buster host - using 
> > > those
> > > it seems should make everything work automagically.
> > 
> > If you realy want to do the networking yourself, you will need to create
> > the bridge based on the examples found in '/lib/systemd/network'.
> 
> I've had success declaring a bridge in /etc/network/interfaces:
> 
> iface br0 inet dhcp
> bridge_ports eth0 # this is your VM Ethernet
> 
> and launching my containers with:
> 
> $ cat /etc/systemd/nspawn/container.nspawn
> [Exec]
> Boot=yes
> 
> [Network]
> Bridge=br0
> $ sudo machinectl start container

I tried this as well. Looks like some specific problem for my setup.


> 
> Alex
> 

I have decided not to pursue this anymore, I need to get things done so will put
this off till I have proper resources and time.

Thanks for all the help to everyone.

Kind regards,
Didar

-- 
Put your brain in gear before starting your mouth in motion.

Re: systemd-nspawn networking inside VirtualBox VM

[Didar Hossain]

On Tue, Jul 07, 2020 at 06:05:14PM +0200, john doe wrote:
> On 7/7/2020 3:13 PM, Didar Hossain wrote:
> > Hi,
> > 
> > TL;DR
> > How to get systemd-nspawn containers networking so that they can talk to 
> > each
> > other, the host and the internet inside a Buster VM? VirtualBox on Windows 
> > 10
> > which has internet connectivity via a wireless interface.
> > 
> > 
> > 
> > I am running a Buster VM with hand picked minimal packages, networking is
> > configured simply using interfaces(5) file with DHCP. I have configured a
> > "NatNetwork" on VirtualBox which allows the VMs to connect to each other 
> > and the
> > internet. I was wondering if I can do similar thing with containers inside 
> > the
> > buster VM.
> > 
> > I used `debbootstrap' to have a template directory of buster under
> > "/opt/templates/buster". I then simply copy the directory tree over to
> > "/var/lib/machines". I tried a few networking options of `systemd-nspawn', 
> > but
> > since I am not well educated about macvlan, ipvlan, I could not get the
> > networking working at all. I would like to avoid using
> > "systemd-networkd/systemd-resolvd" especially on the Buster host - using 
> > those
> > it seems should make everything work automagically.
> > 
> > If it works then I will be able to test my Dovecot/Exim setup easily in such
> > throwaway containers. I currently do testing using VMs.
> > 
> > Does anyone have experience in having this kind of scenario working?
> > 
> 
> For testing purposes, I use in a Buster VM systemd-container.
> That is if your VM has internet access the containers will also get
> internet access .
> 
> For sake of simplicity, I would strongly suggest you to use in the VM
> systemd-networkd to get the networking working between the containers
> and the VM.

I finally gave in and tried things with systemd-networkd - it worked. It seems
the trick is mostly the way routing is setup, "ip route" shows multiple line
output which is difficult to understant unless you know how to work iproute2
advanced routing.

> $ debootstrap --include=systemd-container
> 
> You need the above debootstrap pkg for systemd-networkd to work in the
> container.
> 
> Then in the VM and in eatch container, simply enable systemd-networkd.
> 
> 
> If you realy want to do the networking yourself, you will need to create
> the bridge based on the examples found in '/lib/systemd/network'.
> 
> --
> John Doe
> 

-- 
Don't forget to support the ERA apersonment.

Re: fsck crashes on buster

[Klaus Singvogel]

daggs wrote:
> can you point me to the bugzilla where I can open the bug?

No bugzilla just by command line tool: reportbug.
Can be installed by package: reportbug.

https://www.debian.org/Bugs/Reporting

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Re: fsck crashes on buster

[daggs]

Greetings Michael,

> Sent: Wednesday, July 08, 2020 at 4:12 PM
> From: "Michael Stone" 
> To: "daggs" 
> Cc: debian-user@lists.debian.org
> Subject: Re: fsck crashes on buster
>
> On Wed, Jul 08, 2020 at 10:17:44AM +0200, daggs wrote:
> >my backup hdd has errors in the fs, so I've stopped the backup process and 
> >unmounted it.
> >when I run fsck /dev/sdc1, I get this:
> >root@utilsserver:/home/igor# fsck /dev/sdc1
> >fsck from util-linux 2.33.1
> >e2fsck 1.44.5 (15-Dec-2018)
> >backup contains a file system with errors, check forced.
> >Pass 1: Checking inodes, blocks, and sizes
> >Pass 2: Checking directory structure
> >Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x13
>
> You'll have much better luck filing a bug than contacting debian-user.
> (The maintainer is very responsive, but doesn't AFAIK read debian-user.)
>
>

can you point me to the bugzilla where I can open the bug?

ZTESY? Realtek? How can you know for sure which driver to install? ...

[Albretch Mueller]

 I:

# uname -r
4.9.0-6-amd64

# uname -m
x86_64

 have a WiFi Dongle 802.11 AC Wireless Network Adapter:

// __  ZTESY USB 3.0 WiFi Dongle 802.11 AC Wireless Netzwerk Adapter
mit Dualband 2,4 GHz/300 Mbps + 5 GHz/866 Mbps 5 dBi High Gain Antenne

https://www.amazon.com/-/de/Adapter-1200Mbps-TECHKEY-Wireless-Network-300Mbps/dp/B07J65G9DD/

 which is detected as Realtek (apparently because this is the chipset
they use?)

# dmesg | grep Realtek
[  527.774047] usb 1-2: Manufacturer: Realtek

# dmesg | grep "usb 1-2"
[  527.624365] usb 1-2: new high-speed USB device number 10 using ehci-pci
[  527.774027] usb 1-2: New USB device found, idVendor=0bda, idProduct=b812
[  527.774037] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  527.774042] usb 1-2: Product: USB3.0 802.11ac 1200M Adapter
[  527.774047] usb 1-2: Manufacturer: Realtek
[  527.774051] usb 1-2: SerialNumber: 123456

 So, I installed the suggested firmware

 https://packages.debian.org/stretch/firmware-realtek

 firmware-realtek (20161130-5)

 but thing doesn't work. Yo don't even see the its led lighting up.
Realtek doesn't seem to be a Linux shy company. On their website they
advertise drivers going all the way back from windows XP to 10 as well
as for Macs and Linux:

 https://www.realtek.com/en/component/zoo/category/rtl8812bu-software

 https://wiki.gentoo.org/wiki/AC1200_Wireless_Adapters

 I know the thing works because I have tried it on the same labtop
under a Windows installation and other Windows boxes and it works just
fine without any kinds of hassles.

 Any idea how could I troubleshoot the actual problem in a more
detailed way and fix it?

 lbrtchx

Re: Update errors

[Frank McCormick]

On 7/8/20 10:45 AM, Sven Joachim wrote:

On 2020-07-08 10:20 -0400, Frank McCormick wrote:


Apt flagged a couple of errors during this morning upate.


Warnings, not errors, and they are coming from dpkg.


dpkg: warning: unable to delete old directory
'/usr/share/fonts/woff/font-awesome': Directory not empty dpkg:
warning: unable to delete old directory '/usr/share/fonts/woff':
Directory not empty dpkg: warning: unable to delete old directory
'/usr/share/fonts/svg/font-awesome': Directory not empty dpkg:
warning: unable to delete old directory '/usr/share/fonts/svg':
Directory not empty dpkg: warning: unable to delete old directory
'/usr/share/fonts/eot/font-awesome': Directory not empty dpkg:
warning: unable to delete old directory '/usr/share/fonts/eot':
Directory not empty

Should I go in an remove these directories/files...or just leave it alone ?


I have deleted the spurious .uuid files and their parent directories as
they are cruft, but leaving them in place would not cause harm either.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040

Cheers,
Sven



Seems this bug has been around for quite a while.

Thanks
--
Frank McCormick

Re: Firefox non-ESR update needed

[rhkramer]

On Tuesday, July 07, 2020 10:21:48 AM Greg Wooledge wrote:
> On Tue, Jul 07, 2020 at 10:06:08AM -0400, rhkra...@gmail.com wrote:
> > Wow, not sure what sparked that response, but I will say one thing, you
> > might run testing if your bank insists you have the latest thing
> > (browser).
> 
> Well, you could switch banks.
> 
> Or, you could install the unstable upstream Firefox releases from
> mozilla.com or whatever it's called this year.  And have fun playing
> "what broke this week".
> 
> Personally, I find it hard to believe your statement about a bank
> requiring a *new* web browser to work.  I would be more likely to believe
> "My bank requires that I use an incredibly *old* browser version."
> Or even "My bank only works with Microsoft Internet Explorer."

Aside: I suppose I should clarify that I am not the OP.

Then, more to the point, maybe I use incredibly old browsers (e.g., Firefox 
52.8.0 in Wheezy), and the bank(s) (and similar places that I sometimes deal 
with) insist on less incredibly old browsers -- in any case, I often get 
messages to the effect that I need to update my browser to work with a specific 
site.  

(Then I (usually) switch to my Jessie or Buster installation, which I will 
transtion to completely, one of these days, or maybe not.)

Re: Update errors

[Sven Joachim]

On 2020-07-08 10:20 -0400, Frank McCormick wrote:

> Apt flagged a couple of errors during this morning upate.

Warnings, not errors, and they are coming from dpkg.

> dpkg: warning: unable to delete old directory
> '/usr/share/fonts/woff/font-awesome': Directory not empty dpkg:
> warning: unable to delete old directory '/usr/share/fonts/woff':
> Directory not empty dpkg: warning: unable to delete old directory
> '/usr/share/fonts/svg/font-awesome': Directory not empty dpkg:
> warning: unable to delete old directory '/usr/share/fonts/svg':
> Directory not empty dpkg: warning: unable to delete old directory
> '/usr/share/fonts/eot/font-awesome': Directory not empty dpkg:
> warning: unable to delete old directory '/usr/share/fonts/eot':
> Directory not empty
>
> Should I go in an remove these directories/files...or just leave it alone ?

I have deleted the spurious .uuid files and their parent directories as
they are cruft, but leaving them in place would not cause harm either.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040

Cheers,
   Sven

Re: Suggestion for systemd and /usr on seperate partition

[David Wright]

On Wed 08 Jul 2020 at 18:07:05 (+1000), Andrew McGlashan wrote:
> On 8/7/20 3:35 pm, Andrei POPESCU wrote:
> > On Mi, 08 iul 20, 02:35:09, Andrew McGlashan wrote:
> >> On 8/7/20 2:11 am, Michael Stone wrote:
> >>>
> >>> The short answer is that there simply isn't a good reason to do this 
> >>> on a modern system, and there is no volunteer to donate the enormous 
> >>> amount of effort required to make
> >>> something work for which there isn't a good justification for 
> >>> expending that effort. There should be no flamewar, if someone wants 
> >>> the situation to change they simply need to be
> >>> the person who puts in all the work.
> >>
> >> Just doing dist-upgrade with a perfectly acceptable file system 
> >> previously is no reason why it should break.
> > 
> > Debian supports upgrading of most packages between releases.
> > 
> > It provides no guarantees about hardware, partitioning schemes, 
> > partition sizes, file systems, etc.

I'm not going to suggest that this is proof, but the Release Notes for
buster still carry the warning that one should make sure any /usr
partition has been remounted rw if necessary.

> > I was under the impression that LVM is used in particular for its 
> > flexibility in adjusting your partitions. What prevents you from merging 
> > '/' and '/usr'?
> 
> Yes, that might be the best fix; but I didn't expect it to be necessary.

I haven't seen anything in the Release Notes suggesting that it is necessary.

> On 8/7/20 9:40 am, David Wright wrote:
> >> The mentioned intramfs config file has a strange note about it being 
> >> "dangerous" to enable activate all logical volumes, why?!?!?!
> > A reference to the specific file would help. I see no mention here.
> 
> Line 35 of /usr/share/initramfs-tools/scripts/local-top/lvm2 (see below) that 
> mentions the risk:
> 
> Also see the attached email that I sent to the Devuan DNG list for more 
> reference.
> 
> Below is the file I changed, added line numbered as 63.
> 
> # cat -n /usr/share/initramfs-tools/scripts/local-top/lvm2
>  1#!/bin/sh
>  2
>  3PREREQ="mdadm mdrun multipath"
>  4
>  5prereqs()
>  6{
>  7echo "$PREREQ"
>  8}
>  9
> 10case $1 in
> 11# get pre-requisites
> 12prereqs)
> 13prereqs
> 14exit 0
> 15;;
> 16esac
> 17
> 18if [ ! -e /sbin/lvm ]; then
> 19exit 0
> 20fi
> 21
> 22lvchange_activate() {
> 23lvm lvchange -aay -y --sysinit --ignoreskippedcluster 
> "$@"
> 24}
> 25
> 26activate() {
> 27local dev="$1"
> 28
> 29# Make sure that we have a non-empty argument
> 30if [ -z "$dev" ]; then
> 31return 1
> 32fi
> 33
> 34case "$dev" in
> 35# Take care of lilo boot arg, risky activating of all vg
> 36fe[0-9]*)
> 37lvchange_activate
> 38exit 0
> 39;;
> 40# FIXME: check major
> 41/dev/root)
> 42lvchange_activate
> 43exit 0
> 44;;
> 45
> 46/dev/mapper/*)
> 47eval $(dmsetup splitname --nameprefixes 
> --noheadings --rows "${dev#/dev/mapper/}")
> 48if [ "$DM_VG_NAME" ] && [ "$DM_LV_NAME" ]; then
> 49lvchange_activate 
> "$DM_VG_NAME/$DM_LV_NAME"
> 50fi
> 51;;
> 52
> 53/dev/*/*)
> 54# Could be /dev/VG/LV; use lvs to check
> 55if lvm lvs -- "$dev" >/dev/null 2>&1; then
> 56lvchange_activate "$dev"
> 57fi
> 58;;
> 59esac
> 60}
> 61
> 62activate "$ROOT"
> 63activate "/dev/mapper/vg0-usr"
> 64activate "$resume"
> 65
> 66exit 0
> 
> A line for /usr is in /etc/fstab using it's UUID ... same as root is 
> referenced by UUID (both are in the same lvm2 volume group).

Well, this could be your problem. The jessie Release Notes say:

--✄

4.6.2  Changes to root and /usr filesystem mounting and checking

initramfs-tools will now also run fsck on the root filesystem before
mounting it. If the chosen init program is systemd and there is a
separate /usr filesystem, it will also fsck and mount /usr.

 • If /usr is a separate fil

Update errors

[Frank McCormick]

Apt flagged a couple of errors during this morning upate.

dpkg: warning: unable to delete old directory 
'/usr/share/fonts/woff/font-awesome': Directory not empty dpkg: warning: 
unable to delete old directory '/usr/share/fonts/woff': Directory not 
empty dpkg: warning: unable to delete old directory 
'/usr/share/fonts/svg/font-awesome': Directory not empty dpkg: warning: 
unable to delete old directory '/usr/share/fonts/svg': Directory not 
empty dpkg: warning: unable to delete old directory 
'/usr/share/fonts/eot/font-awesome': Directory not empty dpkg: warning: 
unable to delete old directory '/usr/share/fonts/eot': Directory not empty


Should I go in an remove these directories/files...or just leave it alone ?



--
Frank McCormick

Re: Using .XCompose

[Ajith R]

Hi Greg,

>
Does your Caps Lock key work for Compose if you set it with:

xmodmap -e "keysym Caps_Lock = Multi_key"
>

I tried this and found that the test definition in .XCopose file is working.
However, when I change the .XCompose definition to  <ങ>              
       : "✄"
or to
 <ങ> <ങ>                      : "✄", it is not working
or to
                   : "ങ്ങ"



>
Also, as mentioned before, please make sure you open a new terminal
(or other X11 application) after modifying your .XCompose file.  That
file is only read when libx11 initializes during the start of a new
client application.
>

Just an observation. When it works, the Compose definition works in the 
terminal from which the command is issued. I did test the definitions that 
don't work in a new terminal and Kate.

Thanks,
ajith

Re: minimizing buffer size (i.e. page cache) for bulk copy/rsync -- Re: Swappiness in Buster

[Greg Wooledge]

On Thu, Jul 09, 2020 at 12:02:39AM +1000, Zenaan Harkness wrote:
> What I imagine, and surely hope is that this softlimit program works as
> advertised.

It's hardly unique.  You could do the same thing with a shell script
wrapper that calls ulimit and then exec's the target program.

> [stuff about buffers]

> Since if it's not written in a totally insane way, cp (and to a lesser
> extent rsync) should work like this already, what we really need to
> limit is that pig with the strange "Linux" name

rsync uses a shitload of memory not because it's copying a file with
an enormous buffer size, but because it's tracking *all* of the file
metadata in the entire hierarchy that you feed to it.

> What has been happening since the dawn of time is that this kernel
> caches _every_ disk page read by a program such as cp [...]

Well, prematurely killing rsync is not going to affect the kernel's
retention or discarding of specific disk cache pages that are more
precious to you.

Re: minimizing buffer size (i.e. page cache) for bulk copy/rsync -- Re: Swappiness in Buster

[Zenaan Harkness]

On Wed, Jul 08, 2020 at 08:05:23AM -0400, Greg Wooledge wrote:
> On Wed, Jul 08, 2020 at 08:00:38AM -0400, Dan Ritter wrote:
> > Zenaan Harkness wrote: 
> > > 
> > > Seriously, is there a way to stop bulk copies from eternally flushing my
> > > $Desktop's cached pages down the drain minute after blessful minute,
> > > hour after gratitude filled hour?
> > 
> > softlimit is packaged in daemontools.
> > 
> > NAME
> >softlimit - runs another program with new resource
> > limits.
> 
> I haven't been following this thread because I don't know anything
> about the kernel's "swappiness" settings.
> 
> But I'm a little bit confused about the intent here -- setting a
> resource limit on memory is just going to make the program crash
> with an "out of memory" error when it tries to exceed the limit.
> It's not going to discipline a memory hog program into using
> different algorithms.

I also know nothing about swappiness.

But this soft limit tool sounds exceedingly powerful ()

Hmm. Excuse me ... where was I?

Oh yes, powERRR!

What I imagine, and surely hope is that this softlimit program works as
advertised.  You see, the copy program (normally aliased as `cp`) when
copying say 900 Gigabytes, does not, or certainly should not, consume
more than say 1 Megabyte of memory as a read buffer.  Of course _some_
buffer is needed, since otherwise each read call reads only one byte,
which would result in a ridiculous number of kernel calls and the
performance that doing so entails.  But half a MiB being written to the
destination, whilst another half MiB is being read from the source
"should" be more than enough, since, roughly speaking, those buffers can
simply swap over when they're both ready for another round.

Since if it's not written in a totally insane way, cp (and to a lesser
extent rsync) should work like this already, what we really need to
limit is that pig with the strange "Linux" name (I think it's called
fake lipschtick on an even-toed ungulate family Suidae, I mean kernel).

You see Linux in its eternal and fruitless desire to make user's happy,
gladly tells cp's read side that reading is finished, and also tells its
write side that writing is finished, and so cp races as fast as it
possibly can even if, and especially if, one of the drives is a
different speed than the other (almost always the case) - and the bigger
the difference, the quicker RAM is filled up, and Firefox's tabs evicted
from memory.

What has been happening since the dawn of time is that this kernel
caches _every_ disk page read by a program such as cp (I know, I know,
this is previously unheard of and amazing information I'm leaking) into
something Linux calls the 'page cache' (totally bizzare thing to call an
in memory cache of disk pages, but hey, what do I know...).

And Linux, ever generous with other peoples' resources, hands out your
RAM, ballooning the page cache as though the world will end if it does
not do this to the greatest extent possible "because you might refer to
one of those pages in the near future" and of course you do, when you
write it to the destination disk, at which point, like a pregnant Sow on
meth, Linux almost faints in excitement as its prediction that you would
use that page again, comes true.

And so now Linux is ecstaticly hyping the utility of all these "read
once, write once" pages in the vain hope that evicting all your firefox
Tab's cached memory pages is The Right Thing To Do ™©®.  (And Firefox,
unlike cp and rsync, is helpful enough to tag most of its RAM pages with
"Totally ephemeral dude, feel free to dump to disk or even completely
destroy at any time").

Firefox is super helpful like that :(

And, cp and rsync are evidently nowhere as helpful as Firefox is to
Linux's desire to please the user, and so your desktop experience goes
straight down the drain.

This has been happening since I discovered Linux - 20 years ago, the
symptom was the entire desktop stuttering, the X cursor jumping with a
latency of 10 seconds, if you were lucky.

Alas, every one of the 4000+ kernel developers works for Google or
Amazon ECS, and throughput is the only thing the datacenter needs - that
and the ability to compile Linux kernels.

Re: How To Permanently Add-to a Users PATH Statement in the Bash Shell

[Greg Wooledge]

On Wed, Jul 08, 2020 at 07:53:53AM -0500, Nate Bargmann wrote:
> https://noah.meyerhans.us/2020/07/07/setting-environment-variables-for-gnome-session/

> As I read it, where an environment variable should be set depends on the
> intended scope of the variable.  One comment in response to the blog
> post states that ~/.profile should be used to set such variables and
> that even Gnome on Wayland will read this file (I've not tried it yet
> myself).

I've heard this also, but I have no evidence for or against it.  If it's
true, it's *unique* to the Wayland session, because that sure as hell is
false for X11 sessions.

> There is a caveat!  Isn't there always?  The comments at the top of
> /etc/skel/.profile note:
> 
> # ~/.profile: executed by the command interpreter for login shells.
> # This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
> # exists.

You're over-thinking this.

> For whatever historical reason I do have ~/.bash_profile which does
> nothing other than source ~/.bashrc when Bash is invoked as a login
> shell.  I think I'll move it out of the way and use ~/.profile instead.

Set aside all of the X11 and Wayland and display manager and X session
stuff, and look ONLY at the shell.

When bash is invoked as a login shell (e.g. when you log in via ssh, or
on the console), it reads one of the following files:

~/.bash_profile
~/.bash_login
~/.profile

It searches for them in that order, and the first one that it finds is
what it reads.  Let's call this file "the profile".

YOU, the end user, are expected to configure "the profile" so that it
dots in (or sources, if you're sure you're in bash) the ~/.bashrc file
so that you also get your aliases, functions, and so forth, in your
login shell.

So, in a standard console-only setup, we might have the following files:

=== ~/.profile ===
export PATH=$HOME/bin:$PATH:/sbin:/usr/sbin
export EDITOR=vim
export VISUAL=vim
test "$BASH_VERSION" && . ~/.bashrc
==

=== ~/.bashrc ===
set -o vi
set +o histexpand
alias ll='ls -l'
==

Note that the standard Debian profile (/etc/skel/.profile) uses a similar
test to dot in ~/.bashrc and prepend ~/bin to PATH, so if you're using
the standard profile, it's pretty similar to what I wrote here.

The reason there's more than one possible filename for the profile is
largely historical, but it also ties into the fact that your home
directory can be *shared* across multiple systems.  And you might have
different login shells on different systems.  (Or, you might be the
kind of person who switches your login shell from time to time, and you
want to make sure you can still login with a mostly-sane environment
regardless of which shell is currently selected.)

The ~/.profile file is the traditional profile used by the Bourne shell,
the POSIX shell, and the Korn shell.  Bash reads it for compatibility.
However, bash has a lot of extensions that these other shells may not
offer, so you aren't supposed to put bash-specific syntax into ~/.profile,
because some day, it might be read by a different login shell.

With that in mind, bash offers the alternatives ~/.bash_profile and
~/.bash_login (the latter with csh refugees in mind).  Bash is the only
shell that will read either of those files, so if you use one of those,
you're safe to put bash syntax in it.

In a multi-shell environment (NFS shared home, or frequent use of chsh),
you might choose to put most of your environment variable in ~/.profile,
where they will be read by every file.  Then, you might choose to have
~/.bash_profile dot in ~/.profile, and then perform a bunch of
bash-specific tasks, and then finally dot in ~/.bashrc.

Or, you might choose to retain only ~/.profile and keep it shell-neutral.

There are lots of choices here.  And this is with only the login shell
layer involved -- no X11 or Wayland.

> Okay, having tried that I see that it works!  Set a variable in
> ~/.profile, restart the Gnome session (I did a warm restart and cold
> boot) and using the "Run Command" dialog (Alt-F2 in Gnome) run:
> 
>   'sh -c "env > /tmp/env"
> 
> and then see if your custom variable is set.  In my case with the laptop
> running Bullseye it does work.  I now see several things that I dumped
> in ~/.bashrc that aren't Bash specific and would be better put in
> ~/.profile.  Good thread.

That's interesting, but I'm not sure I fully trust that test you
performed.  I don't know whether the "Run Command dialog" is doing
something secretly.  I'd prefer to check the actual starting environment
of one of the GNOME processes.  I don't know what their names are, but
assuming you can find one that looks like it was started at the time
you logged in, grab its PID and then do something like this:

tr \\0 \\n < /proc/its_pid_here/environ | grep your_variable_here

That will show you the initial environment of that process, without
letting "Run Command" get involved to do any tricky stuff.

If it turns out that the Wayland session really does dot in ~/.profile,
th

Re: Whats chances of getting libTLSv1.3 for stretch

[Gene Heskett]

On Wednesday 08 July 2020 07:54:33 Greg Wooledge wrote:

> On Wed, Jul 08, 2020 at 05:12:20AM -0400, Gene Heskett wrote:
> > As a 2 decade user of fetchmail/procmail combo, I just updated to
> > stretch backports, but did not get a TLSv1.3, so when I configure
> > the newest fetchmail, I don't get ssl3 support.
>
> Er... what?  This question doesn't make any sense.  I can't figure
> out whether you're asking for a *newer* library or an *older* library
> than what you have right now.
>
> TLS 1.3 is very new, and is not assumed to be present by most
> applications.
>
> SSL 3 is extremely old, and has well-known exploited holes.  My
> first Google hit for SSL 3 is a refernce to the POODLE exploit from
> 2014.
> e-poodle-attack>
>
> Are you *really* trying to use SSL 3, because that's what you
> configured the other end to use, "2 decades" ago?  If so, it is time
> to stop doing that.  Upgrade *both* ends to use currently supported,
> non-vulnerable TLS protocols.  At this point, TLS 1.2 is your most
> likely target.

./configure --with-ssl, make, sudo make install, is whats working right 
now. But I won't know if it all just works again till the middle of the 
night when sa-train-bayes runs again.  But it runs as me, so nothing is 
stopping me from running it right now. And this time it did restart 
fetchmail ok when it was done. 6.4.3 was giving systemd a tummy ache 
after updating from backports, about 150 packages.  That also destroyed 
TDE and it took a reboot to restore it, a startx got me xfce.

But, while fetchmail-6.4.8 seems to be listed by synaptic, its ghosted 
and will not let me install the "approved" version, so I must dl and 
build my own.  Whats with that?

And I note that procmail is being bad-mouthed, but its been doing exactly 
what I want for 2 decades with no hiccups. I would submit that its docs 
might need help, but if you read them carefully, it does exactly what 
you tell it to do, so I've no need/urge to experiment with getmail. 

Thanks Gregg.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Suggestion for systemd and /usr on seperate partition

[Michael Stone]

On Wed, Jul 08, 2020 at 06:07:05PM +1000, Andrew McGlashan wrote:

A line for /usr is in /etc/fstab using it's UUID ... same as root is referenced 
by UUID (both are in the same lvm2 volume group).


Why not just reference it by path?

Re: fsck crashes on buster

[Michael Stone]

On Wed, Jul 08, 2020 at 10:17:44AM +0200, daggs wrote:

my backup hdd has errors in the fs, so I've stopped the backup process and 
unmounted it.
when I run fsck /dev/sdc1, I get this:
root@utilsserver:/home/igor# fsck /dev/sdc1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
backup contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x13


You'll have much better luck filing a bug than contacting debian-user. 
(The maintainer is very responsive, but doesn't AFAIK read debian-user.)

Re: How To Permanently Add-to a Users PATH Statement in the Bash Shell

[Nate Bargmann]

* On 2020 07 Jul 08:58 -0500, Stephen P. Molnar wrote:
> The Subject line is the problem with my Debian Buster platform. Now from
> Google I see that there has been a change in the way Debian handles this
> problem.
> 
> My user path statement is:
> 
> comp@AbNormal:~$ echo $PATH
> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> 
> Now I have a number of applications that have multiple executable in the app
> /bin subdirectory. Hence the need to add to the users PATH statement
> 
> As an example I have:
> 
> /home/comp/Apps/ADFRsuite-1.0/bin
> 
> which I would like to add to the PATH statement and:
> 
> export PATH=$PATH:'/home/comp/Apps/ADFRsuite-1.0/bin'
> 
> This works unless I open a new Terminal, in which case it is no longer in
> the PATH.
> 
> How do I make the addition persistent?

I just saw a related blog post from the Debian Planet blog aggregator
(https://planet.debian.org/):

https://noah.meyerhans.us/2020/07/07/setting-environment-variables-for-gnome-session/

The post does not reference this thread but may have been inspired by it
or not.  Regardless, the author is trying to solve a similar problem
with Gnome on Wayland.

As I read it, where an environment variable should be set depends on the
intended scope of the variable.  One comment in response to the blog
post states that ~/.profile should be used to set such variables and
that even Gnome on Wayland will read this file (I've not tried it yet
myself).

There is a caveat!  Isn't there always?  The comments at the top of
/etc/skel/.profile note:

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

For whatever historical reason I do have ~/.bash_profile which does
nothing other than source ~/.bashrc when Bash is invoked as a login
shell.  I think I'll move it out of the way and use ~/.profile instead.

Okay, having tried that I see that it works!  Set a variable in
~/.profile, restart the Gnome session (I did a warm restart and cold
boot) and using the "Run Command" dialog (Alt-F2 in Gnome) run:

'sh -c "env > /tmp/env"

and then see if your custom variable is set.  In my case with the laptop
running Bullseye it does work.  I now see several things that I dumped
in ~/.bashrc that aren't Bash specific and would be better put in
~/.profile.  Good thread.

- Nate

-- 

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

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: How To Permanently Add-to a Users PATH Statement in the Bash Shell

[Zenaan Harkness]

On Wed, Jul 08, 2020 at 07:39:40AM -0400, Greg Wooledge wrote:
> On Wed, Jul 08, 2020 at 10:44:39AM +1000, Zenaan Harkness wrote:
> >  - XFCE acts as, or uses, Dash or something that does not propagate shell 
> > functions in the parent env
> 
> There are many layers involved.  Assuming you're logging in with a "Debian
> X session", a POSIX shell (sh) is used to read most of the config files
> for the Xsession stuff.  Bash extensions like exporting functions won't
> be possible at that point.
> 
> >  - so launch startx, figuring out over many failures to start "modern" 
> > "sessions"
> 
> Yeah, as I keep saying to others on this list, the entire login paradigm
> is different when you use startx vs. a display manager.  Testing one by
> using the other is not going to work.
> 
> With a console+startx login, your session is begun by an interactive
> login shell (probably bash).  Tricks like exporting functions into the
> environment with the intent to make them available in all of your future
> xterms *will* work from here.
> 
> They *won't* work from a display manager login, though.
> 
> With a DM login, you have a bunch of sh scripts (which aren't even login
> shells) that can export variables but *not* functions.  You don't get
> a bash shell until you actually open a terminal.
> 
> None of your shell's dot files are used at all, until you open a terminal,
> and then *only* .bashrc gets read (unless you configure your terminal
> to run a login shell -- which some people do, just to make things even
> *more* difficult to explain and diagnose).
> 
> >  - but alas, XFCE would not propagate shell functions
> 
> It's not XFCE per se.  It's the fact that a display manager was used for
> the initial login.  Even if you configure it to run a single gigantic
> xterm and nothing else.
> 
> On Wed, Jul 08, 2020 at 08:24:56AM +0300, Andrei POPESCU wrote:
> > On Mi, 08 iul 20, 10:44:39, Zenaan Harkness wrote:
> > >  - so try somewhere in the session startup apps - nope, courdn't 
> > >  figure it out at least
> > 
> > For Debian you want ~/.xsessionrc
> 
> Do note, as I mentioned on the wiki, that ~/.xsessionrc is read by
> a POSIX shell, and you can't use bashisms in it.
> 
> unicorn:~$ grep -r USERXSESSIONRC /etc/X11
> /etc/X11/Xsession.d/40x11-common_xsessionrc:if [ -r "$USERXSESSIONRC" ]; then
> /etc/X11/Xsession.d/40x11-common_xsessionrc:  . "$USERXSESSIONRC"
> /etc/X11/Xsession:USERXSESSIONRC=$HOME/.xsessionrc
> 
> See, the ~/.xsessionrc file is dotted in (by a POSIX shell).  It's not
> executed as a program.  So you can't just change the shebang on it, or
> anything like that.
> 
> If the goal is to export bash functions into the environment for the
> entire session, honestly, sticking with console + startx is the best
> approach.


Some useful hints there, thank you.

But, snigger moan, xfce-session is "special".  No dice on the bashisms 
(admittedly, about 4 yrs since I looked).  You see, XFCE Just Wurked™©® for a 
number of things, and I like that nostalgic WindowsXP feel it gives (I 
know, I know, brown paper bag firmly planted on head...).

Re: minimizing buffer size (i.e. page cache) for bulk copy/rsync -- Re: Swappiness in Buster

[Greg Wooledge]

On Wed, Jul 08, 2020 at 08:00:38AM -0400, Dan Ritter wrote:
> Zenaan Harkness wrote: 
> > 
> > Seriously, is there a way to stop bulk copies from eternally flushing my
> > $Desktop's cached pages down the drain minute after blessful minute,
> > hour after gratitude filled hour?
> 
> softlimit is packaged in daemontools.
> 
> NAME
>softlimit - runs another program with new resource
> limits.

I haven't been following this thread because I don't know anything
about the kernel's "swappiness" settings.

But I'm a little bit confused about the intent here -- setting a
resource limit on memory is just going to make the program crash
with an "out of memory" error when it tries to exceed the limit.
It's not going to discipline a memory hog program into using
different algorithms.

Re: minimizing buffer size (i.e. page cache) for bulk copy/rsync -- Re: Swappiness in Buster

[Dan Ritter]

Zenaan Harkness wrote: 
> 
> Seriously, is there a way to stop bulk copies from eternally flushing my
> $Desktop's cached pages down the drain minute after blessful minute,
> hour after gratitude filled hour?

softlimit is packaged in daemontools.

NAME
   softlimit - runs another program with new resource
limits.

SYNOPSIS
   softlimit [ opts ] child

DESCRIPTION
   opts is a series of getopt-style options.  child consists
of one or more arguments.

   softlimit sets soft resource limits as specified by opts.
It then runs child.

OPTIONS
   In  each  of  the  following  opts, n may be =,
indicating that the soft limit should be set equal to the hard
   limit.

   opts controlling memory use:

   -m n   Same as -d n -s n -l n -a n.

   -d n   Limit the data segment per process to n bytes.

   -s n   Limit the stack segment per process to n bytes.

   -l n   Limit the locked physical pages per process to n
bytes. This option has no  effect  on  some  operating
  systems.

   -a n   Limit  the  total  of  all segments per process to
n bytes. This option has no effect on some operating
  systems.

 and so on for other resources to limit.

-dsr-

Re: Whats chances of getting libTLSv1.3 for stretch

[Greg Wooledge]

On Wed, Jul 08, 2020 at 05:12:20AM -0400, Gene Heskett wrote:
> As a 2 decade user of fetchmail/procmail combo, I just updated to stretch 
> backports, but did not get a TLSv1.3, so when I configure the newest 
> fetchmail, I don't get ssl3 support.

Er... what?  This question doesn't make any sense.  I can't figure
out whether you're asking for a *newer* library or an *older* library
than what you have right now.

TLS 1.3 is very new, and is not assumed to be present by most
applications.

SSL 3 is extremely old, and has well-known exploited holes.  My
first Google hit for SSL 3 is a refernce to the POODLE exploit from
2014. 


Are you *really* trying to use SSL 3, because that's what you configured
the other end to use, "2 decades" ago?  If so, it is time to stop
doing that.  Upgrade *both* ends to use currently supported, non-vulnerable
TLS protocols.  At this point, TLS 1.2 is your most likely target.

Re: How To Permanently Add-to a Users PATH Statement in the Bash Shell

[Greg Wooledge]

On Wed, Jul 08, 2020 at 10:44:39AM +1000, Zenaan Harkness wrote:
>  - XFCE acts as, or uses, Dash or something that does not propagate shell 
> functions in the parent env

There are many layers involved.  Assuming you're logging in with a "Debian
X session", a POSIX shell (sh) is used to read most of the config files
for the Xsession stuff.  Bash extensions like exporting functions won't
be possible at that point.

>  - so launch startx, figuring out over many failures to start "modern" 
> "sessions"

Yeah, as I keep saying to others on this list, the entire login paradigm
is different when you use startx vs. a display manager.  Testing one by
using the other is not going to work.

With a console+startx login, your session is begun by an interactive
login shell (probably bash).  Tricks like exporting functions into the
environment with the intent to make them available in all of your future
xterms *will* work from here.

They *won't* work from a display manager login, though.

With a DM login, you have a bunch of sh scripts (which aren't even login
shells) that can export variables but *not* functions.  You don't get
a bash shell until you actually open a terminal.

None of your shell's dot files are used at all, until you open a terminal,
and then *only* .bashrc gets read (unless you configure your terminal
to run a login shell -- which some people do, just to make things even
*more* difficult to explain and diagnose).

>  - but alas, XFCE would not propagate shell functions

It's not XFCE per se.  It's the fact that a display manager was used for
the initial login.  Even if you configure it to run a single gigantic
xterm and nothing else.

On Wed, Jul 08, 2020 at 08:24:56AM +0300, Andrei POPESCU wrote:
> On Mi, 08 iul 20, 10:44:39, Zenaan Harkness wrote:
> >  - so try somewhere in the session startup apps - nope, courdn't 
> >  figure it out at least
> 
> For Debian you want ~/.xsessionrc

Do note, as I mentioned on the wiki, that ~/.xsessionrc is read by
a POSIX shell, and you can't use bashisms in it.

unicorn:~$ grep -r USERXSESSIONRC /etc/X11
/etc/X11/Xsession.d/40x11-common_xsessionrc:if [ -r "$USERXSESSIONRC" ]; then
/etc/X11/Xsession.d/40x11-common_xsessionrc:  . "$USERXSESSIONRC"
/etc/X11/Xsession:USERXSESSIONRC=$HOME/.xsessionrc

See, the ~/.xsessionrc file is dotted in (by a POSIX shell).  It's not
executed as a program.  So you can't just change the shebang on it, or
anything like that.

If the goal is to export bash functions into the environment for the
entire session, honestly, sticking with console + startx is the best
approach.

RE: [External] Re: AMD Ryzen 7 Pro + Radeon Graphics

[Curtis Tucker1]

Hi Everyone,

All is working fine except the ability to get an external monitor working via 
HDMI.  Is there a config file I need to modify for the Wayland/XWayland Server 
to support multiple displays?

Thanks,
C
   
-Original Message-
From: Dan Ritter  
Sent: Monday, June 22, 2020 8:51 AM
To: Curtis Tucker1 
Cc: debian-user@lists.debian.org
Subject: [External] Re: AMD Ryzen 7 Pro + Radeon Graphics

Curtis Tucker1 wrote: 
> Hi,
> 
> After installing "firmware-bullseye-D1-alpha2-amd64-DVD-1" on an AMD Ryzen 7 
> Pro + Radeon Graphics platform, the system boots but no desktop (Gnome) is 
> launched & the screen is blank.
> 
> Is this platform supported?  I set "nomodeset" on the boot line, but that did 
> not work.  I booted to runlevel 3 to investigate, but the keyboard wasn't 
> configured properly.  I looked far & wide & could not find any solution or 
> information regarding this issue.
> 


You'll want to install 
xserver-xorg-video-amdgpu 
and
firmware-amd-graphics

and reboot.

-dsr-

Re: minimizing buffer size (i.e. page cache) for bulk copy/rsync -- Re: Swappiness in Buster

[Reco]

Hi.

On Wed, Jul 08, 2020 at 05:51:54PM +1000, Zenaan Harkness wrote:
> What needs to happen ™©®
> 
> What is needed is an option somewhere, strictly abided by, where "For
> the following command" only say 1MiB of buffer and Page Cache, in TOTAL,
> is able to be used by that command ever, until its completion.

This works for me in stable, it's systemwide though.

sysctl -w vm.dirty_bytes=16777216
sysctl -w vm.dirty_background_bytes=16777216

Reco

Whats chances of getting libTLSv1.3 for stretch

[Gene Heskett]

Greetings all;

2 questions.

As a 2 decade user of fetchmail/procmail combo, I just updated to stretch 
backports, but did not get a TLSv1.3, so when I configure the newest 
fetchmail, I don't get ssl3 support.

So whats chances of getting that in stretch security/backports?

Also, I've not a clue how to generate the systemd-service file that 
systemd seems to be demanding and that so far I have had to rebuild 
fetchmail from src and reinstall everytime cron runs 
~/bin/sa-train-bayes.  Thats not very friendly on systemd's intrusions 
into normal daily operations. I am the only O2 breathing user here, so I 
do eventually get it to work, as me, which is all it has to do, but I 
don't appreciate the PITA the battle is  with systemd to do what s/b 
normal housekeeping. So the 2nd question is how can this be fixed?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Suggestion for systemd and /usr on seperate partition

[tomas]

On Wed, Jul 08, 2020 at 08:35:35AM +0300, Andrei POPESCU wrote:

[...]

> I was under the impression that LVM is used in particular for its 
> flexibility in adjusting your partitions.

But it won't make disappear a separate /usr partition "by magic".

> What prevents you from merging '/' and '/usr'?

This thread is talking about upgrades. Do you suggest an upgrade
copying the contents of the /usr partition over to the / partition
and dropping the separate /usr (perhaps recovering the space somehow)?

Sounds pretty risky.

FWIW, I still have a separate /usr on Buster (inherited from older
installations). I'd have no problems with a merged /usr, but hey,
I have no problems with leaving things as they are either.

Cheers
-- t


signature.asc
Description: Digital signature

Re: Suggestion for systemd and /usr on seperate partition

[Andrew McGlashan]

On 8/7/20 3:35 pm, Andrei POPESCU wrote:
> On Mi, 08 iul 20, 02:35:09, Andrew McGlashan wrote:
>> On 8/7/20 2:11 am, Michael Stone wrote:
>>>
>>> The short answer is that there simply isn't a good reason to do this 
>>> on a modern system, and there is no volunteer to donate the enormous 
>>> amount of effort required to make
>>> something work for which there isn't a good justification for 
>>> expending that effort. There should be no flamewar, if someone wants 
>>> the situation to change they simply need to be
>>> the person who puts in all the work.
>>
>> Just doing dist-upgrade with a perfectly acceptable file system 
>> previously is no reason why it should break.
> 
> Debian supports upgrading of most packages between releases.
> 
> It provides no guarantees about hardware, partitioning schemes, 
> partition sizes, file systems, etc.
> 
> I was under the impression that LVM is used in particular for its 
> flexibility in adjusting your partitions. What prevents you from merging 
> '/' and '/usr'?

Yes, that might be the best fix; but I didn't expect it to be necessary.



On 8/7/20 9:40 am, David Wright wrote:
>> The mentioned intramfs config file has a strange note about it being 
>> "dangerous" to enable activate all logical volumes, why?!?!?!
> A reference to the specific file would help. I see no mention here.



Line 35 of /usr/share/initramfs-tools/scripts/local-top/lvm2 (see below) that 
mentions the risk:




Also see the attached email that I sent to the Devuan DNG list for more 
reference.


Below is the file I changed, added line numbered as 63.


# cat -n /usr/share/initramfs-tools/scripts/local-top/lvm2
 1  #!/bin/sh
 2  
 3  PREREQ="mdadm mdrun multipath"
 4  
 5  prereqs()
 6  {
 7  echo "$PREREQ"
 8  }
 9  
10  case $1 in
11  # get pre-requisites
12  prereqs)
13  prereqs
14  exit 0
15  ;;
16  esac
17  
18  if [ ! -e /sbin/lvm ]; then
19  exit 0
20  fi
21  
22  lvchange_activate() {
23  lvm lvchange -aay -y --sysinit --ignoreskippedcluster "$@"
24  }
25  
26  activate() {
27  local dev="$1"
28  
29  # Make sure that we have a non-empty argument
30  if [ -z "$dev" ]; then
31  return 1
32  fi
33  
34  case "$dev" in
35  # Take care of lilo boot arg, risky activating of all vg
36  fe[0-9]*)
37  lvchange_activate
38  exit 0
39  ;;
40  # FIXME: check major
41  /dev/root)
42  lvchange_activate
43  exit 0
44  ;;
45  
46  /dev/mapper/*)
47  eval $(dmsetup splitname --nameprefixes --noheadings 
--rows "${dev#/dev/mapper/}")
48  if [ "$DM_VG_NAME" ] && [ "$DM_LV_NAME" ]; then
49  lvchange_activate "$DM_VG_NAME/$DM_LV_NAME"
50  fi
51  ;;
52  
53  /dev/*/*)
54  # Could be /dev/VG/LV; use lvs to check
55  if lvm lvs -- "$dev" >/dev/null 2>&1; then
56  lvchange_activate "$dev"
57  fi
58  ;;
59  esac
60  }
61  
62  activate "$ROOT"
63  activate "/dev/mapper/vg0-usr"
64  activate "$resume"
65  
66  exit 0


A line for /usr is in /etc/fstab using it's UUID ... same as root is referenced 
by UUID (both are in the same lvm2 volume group).


NB: If /usr wasn't being used with lvm2, then this problem might not have 
surfaced and it probably would not have been a problem if the whole VG was 
activated instead of just the
root file system because the UUID would have been "known or attainable" from 
the logical volumes.



Kind Regards
AndrewM
--- Begin Message ---
Hi,

I had another "simple" server upgrade from Devuan Ascii to Devuan Beowulf, 
these are the details and my work around for the problem.


There was nothing particularly special about this server, it doesn't use 
encrypted file systems; it started out life as a Debian Wheezy installation, 
migrated to Devuan Jessie and
later to Devuan Ascii and now Beowulf.


The server has /boot on it's own RAID1 partition with another RAID1 volume for 
the rest of the disk being an LVM2 volume group having a number of logical 
volumes for root, swap,
/usr/, /var/, /home/ and more.


After the dist-upgrade, it failed to boot and remained at the ministrants shell 
environment after having complained about not being able to find the /usr file 
system via it's UUID.

It had another error as well which was fixed by allocating 25% to RUNSIZE 
variable (up from 10%) in /etc/initramfs-tools/initramfs.conf

- it was unable to find "rm" when running the boot up scripts bef

fsck crashes on buster

[daggs]

Greetings,

my backup hdd has errors in the fs, so I've stopped the backup process and 
unmounted it.
when I run fsck /dev/sdc1, I get this:
root@utilsserver:/home/igor# fsck /dev/sdc1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
backup contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x13
fsck.ext3(+0x31a59)[0x55bc7d8afa59]
/lib/x86_64-linux-gnu/libc.so.6(+0x37840)[0x7feed55ab840]
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7feed57e8b33]
/lib/x86_64-linux-gnu/libext2fs.so.2(+0x17802)[0x7feed57c1802]
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_icount_increment+0x158)[0x7feed57d3d48]
fsck.ext3(+0x21645)[0x55bc7d89f645]
fsck.ext3(+0x22997)[0x55bc7d8a0997]
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_dblist_iterate3+0x5f)[0x7feed57c72bf]
fsck.ext3(e2fsck_pass2+0x18a)[0x55bc7d89d9ba]
fsck.ext3(e2fsck_run+0x5a)[0x55bc7d89166a]
fsck.ext3(main+0xcce)[0x55bc7d88d2be]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7feed559809b]
fsck.ext3(_start+0x2a)[0x55bc7d88f58a]

the os is updated to latest. any hints on how to fix it?
I'd rather not turn it off to extract the hdd as it is a production server.

Thanks,

Dagg.

Re:📨[MCB Manancourt] (35)

[MCB Manancourt]

https://bit.ly/38vWiae





MCB Manancourt 
Prayerfully,MCB Manancourt







I'm hoping you are going through a beautiful day 














=NEWS=

Jamie Davis: Ex-serviceman took own life after suffering PTSD
A former soldier was "riddled with survivor's guilt" after seeing colleagues 
killed, his widow says.

7.8 million Brazilians out of work due to Covid-19
Nearly eight million people in Brazil have lost work due to the coronavirus 
pandemic, according to new figures released by the country's statistics agency 
Tuesday.

Here are some of the tech start-ups that took government payroll loans during 
the coronavirus crisis
Several tech start-ups were among the companies that received loans under a program intended to blunt the economic damage from Covid-19, according to a list released Monday by the Trump Administration. Bird, Mixpanel, Grindr and Zendrive were on the list. 


==

minimizing buffer size (i.e. page cache) for bulk copy/rsync -- Re: Swappiness in Buster

[Zenaan Harkness]

On Wed, Jul 08, 2020 at 08:26:18AM +0200, Martin Reissner wrote:
> For the sake of completeness, I seem to have solved it after some more
> research and it turned out to be systemd, as following bug that was
> reported for Centos7 seems to be applying to Debian Buster as well:
> 
> https://github.com/systemd/systemd/issues/9276
> 
> Luckily the workaround mentioned in:
> 
> https://github.com/systemd/systemd/issues/9276#issuecomment-442514543
> 
> applies here as well and by setting this to the desired swappiness value
> and rebooting the system so far it seems to work as before and swapping
> out is only done if it can't be avoided.


Your thread brings to mind an "$AGE_OF_LINUX_KERNEL + 1 year" years old
Linux kernel bona fydee, bulk copy bug bear:

Doing a bulk copy e.g. using cp or rsync, to copy GiBs far greater than
available RAM from one disk to another, results in ...

  
Total Annihilation of Desktop Latency
   

This happens to this day even on the latest Linux kernels on Sid such as
5.7.0-1-amd64 to pick an entirely random example... and has been
literally bugging me since the beginnings of my Debian journey ~20 years
ago.

Note that in this extremely humble user's experience, even

ionice --class Idle ...

is not even able to quell the Memory Beast's all consuming hunger games
for all possible RAM and then some, in it's insatiable appetite for all
the page cache in...

  
 The  Entire  Universe
   


What needs to happen ™©®

What is needed is an option somewhere, strictly abided by, where "For
the following command" only say 1MiB of buffer and Page Cache, in TOTAL,
is able to be used by that command ever, until its completion.

In this way my 16GiBs of RAM will __finally__ be left to its rightful
owners Firefox, mutt, and my XOrg's cursor, since to me as an extremely
humble desktop user, these are the only things in the world that I ever
care about, and I esPECIALLY want to NOT care that a 1,700 GiB movie
disk backup takes an extra 5 or 10 % longer than the NINE hours it
already takes across its USB 2 connection!

Seriously, is there a way to stop bulk copies from eternally flushing my
$Desktop's cached pages down the drain minute after blessful minute,
hour after gratitude filled hour?

The heavens will truly be pleased ..