Re: QEMU guests can ping but can't access host

[Charles Curley]

On Sat, 04 Sep 2021 18:08:18 -0500
"David Palacio"  wrote:

> I have compared my previous install nft ruleset and installed
> packages list with the current install and found that firewalld
> wasn't installed in the working system but ufw was. The nft ruleset
> was nearly identical save for the missing firewalld rules.
> 
> And so after purging firewalld, plasma-firewall and installing ufw
> the VM guest can communicate with the host.

Excellent. Good detective work.

> 
> This was odd, though. I had already uninstalled firewalld and
> restarted the system before in an attempt to fix the issue only to
> find the VM couldn't access *anything* then. Maybe the installation
> of ufw helps somehow or plasma-firewall breaks something.

Ah. That is because routing between the two networks is usually shut
off by default. The firewall software usually silently takes care of
that for you.

> 
> Thank you for trying to help me.

You are welcome.

And I've learned something also, that comparing packages installed
might be useful. Thank you.

-- 
Does anybody read signatures any more?

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

Re: Why ``color_prompt`` is only set for ``xterm``? (colored prompt examples)

[Intense Red]

> In /root/.bashrc I use this to give a red prompt including host and
> full path followed by a new line.

   I take this idea a bit further, setting a longer prompt and setting 
workstation hosts for specific colors for user logins, and then doing a red 
prompt for servers.

   Part of my ~/.bashrc:

# Set the hostname to a specific color
HostName=`hostname -s`
if [ $HostName = "capncrunch" ]; then
   HostColor="\[\033[1;36m\]" # Bright Cyan
 elif [ $HostName = "piglet" ]; then
   HostColor="\[\033[1;35m\]" # Bright Purple
 elif [ $HostName = "wiseguy" ]; then
   HostColor="\[\033[1;32m\]" # Bright Green
 elif [ $HostName = "munchkin" ]; then
   HostColor="\[\033[1;34m\]" # Bright Blue
 elif [ $HostName = "bingo" ]; then
   HostColor="\[\033[1;33m\]" # Bright Yellow
# Now set red colors for servers:
 elif [ $HostName = "toto" ]; then
   HostColor="\[\033[1;31m\]" # Bright Red
 elif [ $HostName = "dorothy" ]; then
   HostColor="\[\033[1;31m\]" # Bright Red
# set any other machine to Bright White
 else
   HostColor="\[\033[1;37m\]" # Bright White
fi

# Check to see if the script is being run by root and set
# appropriate prompts:
if [ "$(id -u)" != "0" ]; then
   PromptSymbol="$"
   UserNameColor="\[\033[1;32m\]"
else
# let's make the root user's prompt a blinking red prompt
   PromptSymbol="\[\033[1;31m\]\[\033[5m\]#\[\033[0m\]"
   UserNameColor="\[\033[1;31m\]"
fi

# And everyone wants a 3-line prompt that gives a little more info than the
# default bash prompt, right?!
#
# E-mail messaging might screw this up a little, but try this as your PS1
# prompt:
PS1="┌─[$UserNameColor\u\033[0m@$HostColor$HostName\033[0m][\033[1;33m\]
\w\033[0m]\n│ [\033[1;36m\]\t   \d\033[0m]\n└─$PromptSymbol "
#
# That PS1 above, of course, should be all on one line.

# We'll unset the temporary variables we set above just to clean things up:
unset HostName HostColor PromptSymbol UserNameColor 

# I like to tweak the Bash colors a bit for "ls" listings. This might give
# someone some ideas:
LS_COLORS='no=00:fi=00:di=01;33:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.rar=01;31:*.arj=01;31:*.taz=01;31:
*.lzh=01;31:*.zip=01;31:*.bz2=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.deb=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:
*.tif=01;35:*.mpg=01;37:*.mp4=01;37:*.avi=01;37:*.mkv=01;37:*.gl=01;37:*.dl=01;37:'
# That LS_COLORS line should, of course, all be on one long line.

# Then we need to export them so the shell picks things up.
export PS1 LS_COLORS

   That's worth playing with to change some of the default settings if one 
wants to play with the colors of a terminal (I use KDE's "konsole" rather than 
xterm, but it's the same idea.

-- 
"I remember when I was a boy and I heard repeated time and time again the 
phrase, 'My country, right or wrong, my country!' How absolutely absurd is 
such an idea. How absolutely absurd to teach this idea to the youth of the 
country." -- Mark Twain, 1907.

Re: Trouble upgrading Debian

[David Wright]

On Sat 04 Sep 2021 at 23:04:49 (-0300), Dedeco Balaco wrote:
> 
> today, i started to upgrade my computer from Debian 9 (Stretch) to
> Debian 11 (Bullseye). I had some trouble finding what i wanted to do, a
> completely internet based upgrade, if possible. In the Debian
> documention, i did not find this explanation. It says it can be done,
> but it does not explain how to do it.
> 
> So, i opened the following thread. Do not read it now, there are more
> things i will say here, first.
> 
> https://www.linuxquestions.org/questions/linux-software-2/upgrading-debian-distribution-4175700202/#post6281677
> 
> In the thread, I was advised to not upgrade from Debian 9 to 11 in one
> step, because "jumping 2 releases will probably result in MASSIVE
> breakage". This should be in the official documentation, no? If there is
> this risk, it must be.

Yes, in the Release Notes. You can download the appropriate version from
https://www.debian.org/releases/bullseye/releasenotes

The warning is in § 4.2.1. It's recursive, so when you go back to
buster's, it has the same warning (§ 4.2), and the same for stretch,
jessie, and so on.

> So, i should to 2 upgrades: one to Debian 10, and one more to Debian 11.
> Fine. And for each one, the steps are:
> 
> 1. Disable all third party repositories.
> 
> 2. Edit /etc/apt/sources.list to reflect the next distribution i will
> have. Directly, this is just changing all "stretch" occurencies to
> "buster"; or all "buster" to "bullseye", in the second upgrade.

No, follow the Release Notes. For example, you should update and
upgrade the current version before you change sources.list, as the
main upgrade should be made from the latest point-release.

> 3. apt update
> 
> 4. apt upgrade
> 
> 5. apt full-upgrade
> 
> But after my first edition to sources.list, apt update fails. I have
> tried apt-get update to, but it also fails for the apparently same reason.
> 
> What should i do to solve this?

Presumably you need help here, so posting the error message is needed.
But do read the Release Notes (buster's in the first instance):
if you follow them carefully, it's possible you won't get failures.

Cheers,
David.

Re: Why ``color_prompt`` is only set for ``xterm``?

[David Wright]

On Fri 03 Sep 2021 at 02:45:03 (+0100), piorunz wrote:
> On 03/09/2021 01:34, David Wright wrote:
> > (I use my own customisations for distinct colours on each host,
> > and inverse colours for root's prompt.)
> 
> Can you please share your root prompt invocation? Thanks!

Sure. The colours come from a set of files by hostname:

$ cat /var/local/lib/myhosts/colours/axis 
5 magenta bbarbutton=white,magenta,none:bbarhotkey=magenta,white,none
$ 

5 is for ANSI colours,
magenta is for, eg emacs, mutt, etc,
bbarbutton is for mc.

The lines from /root/.bashrc are:

if [[ $- = *i* ]]; then

export PROMPT_COMMAND='Myprompt="$? " && [ "$Myprompt" = "0 " ] && 
Myprompt=""'

# read value from file, and sanitise it
Hue=$(head -c 1 /var/local/lib/myhosts/colours/"$HOSTNAME")
if grep -q ·"$Hue"· <<<"·0·1·2·3·4·5·6·7·8·9·"; then
PS1='\['$(tput setaf 3)$(tput setab 1)'\]$Myprompt\['$(tput bold)$(tput 
setaf 7)$(tput setab "$Hue")'\]\H \t \w\['$(tput sgr0)'\]\$ '
else
PS1='—$Myprompt—\H \t \w\$ '
fi

#hexdump -C <<<"$PS1"

fi

Cheers,
David.

Installing old/deprecated packages

[riveravaldez]

Hi,

I have this `phwmon.py`[1] which I use with fluxbox to have a couple
of system monitors at hand. It depends on some python2 packages, so
stopped working some time ago.
I've just made it work, installing manually (# apt-get install packages.deb)
this packages that I've downloaded from Debian OldStable official archives:

python-psutil
python-is-python2 (this is in fact in Testing)
python-numpy
python-pkg-resources
python-cairo
libffi6
python-gobject-2
python-gtk2

Therefore, my questions:

How safe is this?

Is it better to install them as I did, or adding the corresponding line in
sources.list and pull them from there? Is there any difference?

Thanks a lot in advance and sorry (I previously asked this in another
thread...)

Kind regards!

1] https://gitlab.com/o9000/phwmon

Re: Trouble upgrading Debian

[Greg Wooledge]

On Sat, Sep 04, 2021 at 11:04:49PM -0300, Dedeco Balaco wrote:
> So, i should to 2 upgrades: one to Debian 10, and one more to Debian 11.
> Fine. And for each one, the steps are:

> But after my first edition to sources.list, apt update fails. I have
> tried apt-get update to, but it also fails for the apparently same reason.
> 
> What should i do to solve this?

Start by reading the error message.  If you can't understand it, then
paste it here.

Re: APT testing and unstabe Firefox: can't find newest version from unstable

[Keith Bainbridge]

On Sat, 4 Sep 2021 13:50:19 +0200
"Daniel M."  wrote:

> To my understanding, unstable has 91.0.1-1 and experimental has
> 91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.
> 

Or you can download v92.0.b9 from 

https://www.mozilla.org/en-US/firefox/developer/

The button links to:

https://download.mozilla.org/?product=firefox-devedition-latest-ssl=linux64=en-US


Extract the tar.bz2 on to a partition with exec priveledges.  Start it
by running 

path/extracted/to/firefox/firefox

I don't recall having to mark it executable, but it's been a couple of
years.

All the best

Keith Bainbridge
keith.bainbridge.3...@gmail.com

Re: QEMU guests can ping but can't access host

[David Palacio]

I have compared my previous install nft ruleset and installed packages list 
with the current install and found that firewalld wasn't installed in the 
working system but ufw was. The nft ruleset was nearly identical save for the 
missing firewalld rules.

And so after purging firewalld, plasma-firewall and installing ufw the VM guest 
can communicate with the host.

This was odd, though. I had already uninstalled firewalld and restarted the 
system before in an attempt to fix the issue only to find the VM couldn't 
access *anything* then. Maybe the installation of ufw helps somehow or 
plasma-firewall breaks something.

Thank you for trying to help me.

On Thu, Sep 2, 2021, at 5:13 PM, Charles Curley wrote:
> On Thu, 02 Sep 2021 16:09:23 -0500
> "David Palacio"  wrote:
> 
> > Hi,
> > 
> > > If you copied a disk image (.qcow2 extension) over, but not the
> > > setup files that Virtual Machine Manager (VMM) uses
> > > (in /etc/libvirt), then Windows is on a new machine, and can have
> > > conniptions over it. Go into Windows' device manager (or whatever
> > > they're calling it this week) and see if it is finding all its
> > > hardware correctly.  
> > 
> > The VM virtual network hardware is working. It can access the
> > internet. It can't access only the host, either on the virtual
> > network ip or the physical network ip. I have since removed the old
> > guest image and replaced it with a new installation on a new VM
> > configuration. The same behavior is also seen on a new Linux VM
> > running the Debian Bullseye Live KDE CD.
> 
> OK, then that's not the issue.
> 
> > > What program are you using to try to contact the host?  
> > 
> > I noticed the problem first with Windows Explorer to access the samba
> > share. It simply timesout after a minute or two. Then I have tried
> > ping and a browser. Pinging the host works and the host responds.
> > Then I used nc to test connections like this: nc -lp 8080 On the host
> > and point a guest browser to http://hostip:8080/ but nc never
> > receives anything.
> 
> That sounds suspiciously like firewall ports aren't open.
> 
> > 
> > > You may also have a firewall issue, as you say. On the host, please
> > > run whatever you use as a firewall control program and check to see
> > > if the relevant port(s) is open.  
> > 
> > I have to point out I haven't touched anything regarding firewall
> > since installation, however I have attached the output of iptables
> > and nft in this message.
> > 
> > > You may find it useful to open a terminal and, as root, run
> > > 
> > > tail -f /var/log/syslog
> > > 
> > > and, while that is sitting there, try contacting the host again. If
> > > the firewall is blocking you, you'll see it in syslog.  
> > 
> > Neither syslog nor journalctl display anything related at the time
> > this problem happens.
> > 
> > > If nothing obvious jumps out at you, let us know which program(s)
> > > you are using to control your firewall (shorewall, ufw, gufw,
> > > etc.), and we will see if someone familiar with that program can
> > > help.  
> > 
> > I don't `control` my firewall. It's all Debian's default and the
> > installed Debian packages defaults, like libvirt, which adds some
> > firewall rules automatically. Attached are the outputs of `iptables
> > -L`, `nft list tables` and `nft list table tablename`.
> 
> I looked at the ntf listings you provided. I am completely new to nft
> and nftables, so I may have missed something. I don't see any ports
> open on the guest network (192.168.122.0/24). So I suspect that's the
> problem.
> 
> Now we need an nftables guru to chime in.
> 
> I did find examples on the Web, but none of them looked like it was
> exactly what you needed. Sorry I can't help further.
> 
> 
> -- 
> Does anybody read signatures any more?
> 
> https://charlescurley.com
> https://charlescurley.com/blog/
> 
> 

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[Stefan Monnier]

Greg Wooledge [2021-09-04 11:35:25] wrote:
> On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
>> # file /sbin/reboot
>> /sbin/reboot: POSIX shell script, ASCII text executable
>
> That's not normal for a bullseye system using systemd for init.

Indeed.

> I'm not sure what you did or how your system got into this state.

Maybe

dpkg -S /sbin/reboot /usr/sbin/reboot

could give us a clue?


Stefan

Re: smart fans

[David Christensen]

On 9/3/21 7:42 PM, Emanuel Berg wrote:

David Christensen wrote:


OK, changed.


Your data format still has issues.


You seem to have got the old file again, check it out again,
because some of those issues have already been
mentioned/fixed:

   https://dataswamp.org/~incal/ebchw/cpu.txt



Much better:

http://www.holgerdanske.com/pub/dpchrist/debian-user/20210821-smart-fans/


Looking at the graph of CPU Temperature vs. Time by Governor, there are 
minor differences when running 1 or 2 cores.  After that, it really does 
not matter.



Have you isolated and identified the primary sound source(s) in the 
computer?



Have you implemented any vibration or sound mitigation measures?


If you have magnetic HDD's, switching to SSD's would eliminate those 
vibrations.



David

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[sp...@caiway.net]

On Sat, 04 Sep 2021 14:46:21 -0400
The Wanderer  wrote:

> On 2021-09-04 at 13:20, Greg Wooledge wrote:
> 
> > On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
> >
> >> Greg Wooledge [2021-09-04 11:35:25] wrote:
> >> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> >> >> # file /sbin/reboot

> 
> Based on what I read of the thread, that package is
> progress-linux-container.
> 
> $ apt-cache policy progress-linux-container
> progress-linux-container:
>   Installed: (none)
>   Candidate: 20210101-2
>   Version table:
>  20210101-2 900
> 800 http://ftp.us.debian.org/debian stable/main amd64 Packages
> 800 http://ftp.us.debian.org/debian stable/main i386 Packages
> 900 http://ftp.us.debian.org/debian testing/main amd64
> Packages 900 http://ftp.us.debian.org/debian testing/main i386
> Packages
> 
> progress-linux-container is a package in Debian, and at least at a
> glance, is apparently meant for installing on a Debian system. (Or
> else it made it from the downstream distribution into upstream Debian
> by mistake, somehow.)
> 
> It's just not meant for installing on a host system; it's meant for
> installing only inside a container.
> 
> What resulted in it being installed in the OP's case is unclear (the
> OP has said he doesn't know), but at least at a glance it doesn't
> look like this is a case of mixing different operating systems,
> unless I'm misunderstanding what you mean by that.
> 

Thw Wanderer, you are absolutely right
our posts may have crossed
the case is solved
see above


# apt remove progress-linux-container
solved the issue

and in addition,
I must have installed by hand, in the wrong place
in OS not inside container

my bad


glad it is cleared
thanks

sp007

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[The Wanderer]

On 2021-09-04 at 13:20, Greg Wooledge wrote:

> On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
>
>> Greg Wooledge [2021-09-04 11:35:25] wrote:
>> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
>> >> # file /sbin/reboot
>> >> /sbin/reboot: POSIX shell script, ASCII text executable
>> >
>> > That's not normal for a bullseye system using systemd for init.
>> 
>> Indeed.
>> 
>> > I'm not sure what you did or how your system got into this state.
>> 
>> Maybe
>> 
>> dpkg -S /sbin/reboot /usr/sbin/reboot
>> 
>> could give us a clue?
> 
> From the other part of the thread, it looks like they installed a
> package from a different operating system.  One that interfered with
> the Debian init system.
> 
> This is why we tell people: NEVER mix packages from different operating
> systems.  Especially low-level ones like systemd.

Based on what I read of the thread, that package is
progress-linux-container.

$ apt-cache policy progress-linux-container
progress-linux-container:
  Installed: (none)
  Candidate: 20210101-2
  Version table:
 20210101-2 900
800 http://ftp.us.debian.org/debian stable/main amd64 Packages
800 http://ftp.us.debian.org/debian stable/main i386 Packages
900 http://ftp.us.debian.org/debian testing/main amd64 Packages
900 http://ftp.us.debian.org/debian testing/main i386 Packages

progress-linux-container is a package in Debian, and at least at a
glance, is apparently meant for installing on a Debian system. (Or else
it made it from the downstream distribution into upstream Debian by
mistake, somehow.)

It's just not meant for installing on a host system; it's meant for
installing only inside a container.

What resulted in it being installed in the OP's case is unclear (the OP
has said he doesn't know), but at least at a glance it doesn't look like
this is a case of mixing different operating systems, unless I'm
misunderstanding what you mean by that.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[Greg Wooledge]

On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
> Greg Wooledge [2021-09-04 11:35:25] wrote:
> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> >> # file /sbin/reboot
> >> /sbin/reboot: POSIX shell script, ASCII text executable
> >
> > That's not normal for a bullseye system using systemd for init.
> 
> Indeed.
> 
> > I'm not sure what you did or how your system got into this state.
> 
> Maybe
> 
> dpkg -S /sbin/reboot /usr/sbin/reboot
> 
> could give us a clue?

>From the other part of the thread, it looks like they installed a
package from a different operating system.  One that interfered with
the Debian init system.

This is why we tell people: NEVER mix packages from different operating
systems.  Especially low-level ones like systemd.

Re: APT testing and unstabe Firefox: can't find newest version from unstable

[Anssi Saari]

rhkra...@gmail.com writes:

> Top posting and not quoting anything as I'm coming from a different POV.
>
> If the OP needs firefox 91 (or whatever), there is another option, installing 
> the package available from Mozilla as a separate executable.

Sure. I've had an issue with the Debian Buster's packaged Firefox ESR so
I actually run LibreWolf from an AppImage. LibreWolf is a variant of
Firefox where they remove some things that they think violate your
privacy too much. AppImage is a packaging system where the app is
distributed as a single executable file. So compared to the Firefox
package Mozilla provides, the LibreWolf AppImage is a single file. I
just download the latest to /opt/bin and go...

I don't know if my issue is with Firefox ESR is still in Debian
Bullseye. I'll check that out, at some point...

Re: APT testing and unstabe Firefox: can't find newest version from unstable

[rhkramer]

Top posting and not quoting anything as I'm coming from a different POV.

If the OP needs firefox 91 (or whatever), there is another option, installing 
the package available from Mozilla as a separate executable.

(Aside: I had to do that (for an earlier version of Firefox) because a website 
that I must access periodically changed their design / minimum browser 
requirement (without publicizing it very well).)

I don't remember exactly what I had to do, but the instructions (and 
downloads) are available and reasonably easy to find on the Mozilla website.

Now I have two versions of Firefox installed (on my Jessie system (I know, I 
know, I still plan to install bookworm on a new (to me) system -- life seems 
to keep getting in the way).

If I simply start Firefox in the normal way (I type "Firefox" in the  
textbox, I get the "current" version of Firefox installed in Jessie.

When I need the newer Firefox, I type /opt/firefox/firefox in the same  
 textbox.

IIUC, it is sort of a self-contained binary executable that doesn't depend on 
libraries or such from the "main" Debian Jessie system.

(I didn't notice that anyone else had suggested this, so I did -- sorry if it 
is a duplicate suggestion (or of no value).)

Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED

[sp...@caiway.net]

SOLVED

/usr/share/open-infrastructure/container/shutdown.txt
is from package progress-linux-container:

Progress Linux is a Debian derivative distribution focused on system
integration.

This package is a metapackage to be installed in a container
(systemd-nspawn).

# apt remove progress-linux-container

let's see if this is the problem

YES

I have no idea why it was installed.

Thanks, Reco

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[Greg Wooledge]

On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> On Sat, 4 Sep 2021 16:42:45 +0300
> Reco  wrote:
> 
> > Hi.
> > 
> > On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> > > Suddenly I can no longer reboot or poweroff my up-to-date
> > > bullseye system:
> > > 
> > > # reboot
> > > /usr/sbin/reboot: disabled in systemd-nspawn container
> > 
> > Unless I'm mistaken, these messages are not generated by systemd.
> > In fact, there's nothing that resembles such messages in systemd
> > sources.
> > 
> > So, try this, for starters:
> > 
> > /bin/systemd reboot
> > 
> 
> # /bin/systemd reboot
> Excess arguments.
> 
> > And, what about these:
> > 
> > ls -al /sbin/reboot
> 
> # ls -al /sbin/reboot
> -rwxr-xr-x 1 root root 319 Mar 24 05:22 /sbin/reboot
> 
> 
> > file /sbin/reboot
> > 
> 
> # file /sbin/reboot
> /sbin/reboot: POSIX shell script, ASCII text executable

That's not normal for a bullseye system using systemd for init.

unicorn:~$ ls -l /sbin/reboot
lrwxrwxrwx 1 root root 14 Jul 13 13:29 /sbin/reboot -> /bin/systemctl*

You might need to reinstall the systemd-sysv package, maybe.  I'm
not sure what you did or how your system got into this state.

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[Reco]

On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> On Sat, 4 Sep 2021 16:42:45 +0300
> Reco  wrote:
> 
> > Hi.
> > 
> > On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> > > Suddenly I can no longer reboot or poweroff my up-to-date
> > > bullseye system:
> > > 
> > > # reboot
> > > /usr/sbin/reboot: disabled in systemd-nspawn container
> > 
> > Unless I'm mistaken, these messages are not generated by systemd.
> > In fact, there's nothing that resembles such messages in systemd
> > sources.
> > 
> > So, try this, for starters:
> > 
> > /bin/systemd reboot
> > 
> 
> # /bin/systemd reboot
> Excess arguments.

Er, I meant /bin/systemctl reboot.
But anyway,

> > file /sbin/reboot
> 
> # file /sbin/reboot
> /sbin/reboot: POSIX shell script, ASCII text executable

That's not how it's supposed to be.
Somehow these shell scripts replaced actual halt, reboot and poweroff.

My suggestion:

ln -sf /bin/systemctl /sbin/reboot
ln -sf /bin/systemctl /sbin/halt
ln -sf /bin/systemctl /sbin/poweroff

Or, even better:

apt install --reinstall systemd-sysv

Reco

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[sp...@caiway.net]

On Sat, 4 Sep 2021 16:42:45 +0300
Reco  wrote:

>   Hi.

> /bin/systemd reboot
> 
> And, what about these:
> 
> ls -al /sbin/reboot
> file /sbin/reboot
> 
> Reco
> 

the commands poweroff and reboot are textfiles.
I have no idea

# mcedit /sbin/reboot:
#!/bin/sh

echo "${0}: disabled in systemd-nspawn container"

if [ -e /etc/open-infrastructure/container/shutdown.txt ]
then
cat /etc/open-infrastructure/container/shutdown.txt
elif [ -e /usr/share/open-infrastructure/container/shutdown.txt ]
then
cat /usr/share/open-infrastructure/container/shutdown.txt
fi

exit 1

#eof

# mcedit /sbin/poweroff:
#!/bin/sh

echo "${0}: disabled in systemd-nspawn container"

if [ -e /etc/open-infrastructure/container/shutdown.txt ]
then
cat /etc/open-infrastructure/container/shutdown.txt
elif [ -e /usr/share/open-infrastructure/container/shutdown.txt ]
then
cat /usr/share/open-infrastructure/container/shutdown.txt
fi

exit 1



# cat /usr/share/open-infrastructure/container/shutdown.txt

Linux container share the kernel of the host system they are running on,
there is no need to reboot just the container.

However, please contact your system administrator to reboot this
container from the host system.

So the reason is found, now I have to find out who/what take over these
basic commands

I have no packages with open-infrastructure installed

tia

Re: sources.list pour Debian Testing x86-64 en region parisienne

[Erwann Le Bras]

bonjour

pas chez moi (FFOX 78.13.0esr). Le site est accessible.

Le 04/09/2021 à 09:29, rok a écrit :

bonjour,

http://refpersys.org/

est une connexion non sécurisées et est bloquée par firefox;



amitiés,

--

Erwann

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[sp...@caiway.net]

On Sat, 4 Sep 2021 16:42:45 +0300
Reco  wrote:

>   Hi.
> 
> On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> > Suddenly I can no longer reboot or poweroff my up-to-date
> > bullseye system:
> > 
> > # reboot
> > /usr/sbin/reboot: disabled in systemd-nspawn container
> 
> Unless I'm mistaken, these messages are not generated by systemd.
> In fact, there's nothing that resembles such messages in systemd
> sources.
> 
> So, try this, for starters:
> 
> /bin/systemd reboot
> 

# /bin/systemd reboot
Excess arguments.

> And, what about these:
> 
> ls -al /sbin/reboot

# ls -al /sbin/reboot
-rwxr-xr-x 1 root root 319 Mar 24 05:22 /sbin/reboot


> file /sbin/reboot
> 

# file /sbin/reboot
/sbin/reboot: POSIX shell script, ASCII text executable

> Reco
> 

thx

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

[Reco]

Hi.

On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> Suddenly I can no longer reboot or poweroff my up-to-date
> bullseye system:
> 
> # reboot
> /usr/sbin/reboot: disabled in systemd-nspawn container

Unless I'm mistaken, these messages are not generated by systemd.
In fact, there's nothing that resembles such messages in systemd
sources.

So, try this, for starters:

/bin/systemd reboot

And, what about these:

ls -al /sbin/reboot
file /sbin/reboot

Reco

Re: Sound input source detected but not capturing

[Pankaj Jangid]

Marko Randjelovic  writes:

> Your control 'Capture',0 is turned on and volume is at maximum, so
> that's fine, but you don't have 'input source' control. On my machine
> output of 'amixer -c0' gives among other controls the following:
>
> Simple mixer control 'Input Source',0
>   Capabilities: cenum
>   Items: 'Rear Mic' 'Front Mic' 'Line' 'CD'
>   Item0: 'Rear Mic'
>
> I suppose this is the reason why your capture is not working, but don't
> know how to fix it. You might try to install kernel 5.13 from
> experimental or newest vanilla stable which is currently 5.14.1 (take
> care not to make your system unbootable). Also you might try with newer
> alsa userland software.

Hmm... I have returned from the macos world. I need to regain speed to
do all that. It has been a couple of years now. ;-)

Re: Sound input source detected but not capturing

[Pankaj Jangid]

"Andrew M.A. Cater"  writes:

> Very new laptop? Does it need Intel firmware for the soundcard? 
> firmware-intel-sound from non-free? 
>
> https://packages.debian.org/bullseye/firmware-intel-sound

Thanks for the advice, Andy. I just tried it. But this did not work. I
even rebooted the system after installing. That did not make any
difference.

Re: APT testing and unstabe Firefox: can't find newest version from unstable

[Daniel M.]

> If you mean the line from that page "[2021-08-18] Accepted firefox
> 91.0.1-1 (source) into unstable (Mike Hommey)", that doesn't mean binary
> packages are available as you've noticed.
Okay, that explains it. In fact, i was referring to the versions table
in the left column.

> I don't actually know where one could see when new binary packages are
> added to unstable? Would be somewhat interesting.
If you scroll down to the bottom of this page:
https://packages.debian.org/sid/firefox

there seems to be a list of what is available in sid at the moment.
And that is still 88. Okay, thank you for explaining, I learned
something today :)

Am Sa., 4. Sept. 2021 um 15:02 Uhr schrieb Anssi Saari :
>
> "Daniel M."  writes:
>
> > The debian package tracker (https://tracker.debian.org/pkg/firefox)
> > states that version 91.0.1-1 of firefox should be available, but I can
> > in no way install it.
>
> If you mean the line from that page "[2021-08-18] Accepted firefox
> 91.0.1-1 (source) into unstable (Mike Hommey)", that doesn't mean binary
> packages are available as you've noticed.
>
> I don't actually know where one could see when new binary packages are
> added to unstable? Would be somewhat interesting.
>

Re: APT testing and unstabe Firefox: can't find newest version from unstable

[Anssi Saari]

"Daniel M."  writes:

> The debian package tracker (https://tracker.debian.org/pkg/firefox)
> states that version 91.0.1-1 of firefox should be available, but I can
> in no way install it.

If you mean the line from that page "[2021-08-18] Accepted firefox
91.0.1-1 (source) into unstable (Mike Hommey)", that doesn't mean binary
packages are available as you've noticed.

I don't actually know where one could see when new binary packages are
added to unstable? Would be somewhat interesting.

/usr/sbin/reboot: disabled in systemd-nspawn container

[sp...@caiway.net]

Hi,

Suddenly I can no longer reboot or poweroff my up-to-date
bullseye system:

# reboot
/usr/sbin/reboot: disabled in systemd-nspawn container

Linux container share the kernel of the host system they are running on,
there is no need to reboot just the container.

However, please contact your system administrator to reboot this
container from the host system.



# poweroff
/usr/sbin/poweroff: disabled in systemd-nspawn container

Linux container share the kernel of the host system they are running on,
there is no need to reboot just the container.

However, please contact your system administrator to reboot this
container from the host system.



I am definitively NOT in a container.

I did experiment with systemd-nspawn some weeks ago and stopped using
it.
I did often reboot/poweroff this system after this, and I have no idea
where to look for the bug.

# apt purge systemd-container does not help


Now I do Alt+SysReq+...to reboot/poweroff




tia

Re: Question about DMARK and flood of mails...

[NoSpam]

Le 04/09/2021 à 14:02, Jean-François Bachelet a écrit :

Hello ^^)


Le 04/09/2021 à 11:37, NoSpam a écrit :

Bonjour

Le 04/09/2021 à 03:44, Jean-François Bachelet a écrit :

Hello ^^)


en ce moment je suis floodé de mails 'dmark aggregate reports' de la 
part de serveurs que j'ai pas contacté, pour un domaine (qui 
m'appartient) mais qui n'envoie pas de mails sauf si c'est moi qui 
le fait... et le dernier date de plus d'un mois.


c'est quoi ce binz ? une idée ?


On vous prévient que des courriels sont envoyés avec une/des 
adresse-s de votre domaine, les serveur MX expéditeurs, etc. Bref, 
quelle est l'utilisation faite de votre domaine sur Internet.


https://www.dmarcanalyzer.com/dmarc-aggregate-reports/


ouai, bin justement comme je le dit plus haut je n'en envoie pas. le 
serveur de mail est hors ligne. donc d'où ça sort ces m*rdes ? des 
usurpations d'identité mail ?


Et bien oui, et c'est ainsi depuis des années, utilisé entre autres par 
les spammeurs. N'importe qui peut envoyer des courriels à partir d'un 
domaine qui ne lui appartient pas en utilisant un serveur MX en open 
relay. Et il y en a à foison. C'est pour cela que DKIM & co ont été mis 
au point.


--
Daniel

Re: Re: APT testing and unstabe Firefox: can't find newest version from unstable

[Roberto C . Sánchez]

On Sat, Sep 04, 2021 at 01:50:19PM +0200, Daniel M. wrote:
> To my understanding, unstable has 91.0.1-1 and experimental has
> 91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.
> 
The buildd status page for the firefox package [0] shows that the
builders have the package in state BD-Uninstallable.  That means that
the dependencies required for the package cannot be installed on the
build machines, preventing the package from being built.  Looking at the
next upload, version 91.0.1-2 to experimental [1], its changelog entry
is:

firefox (91.0.1-2) experimental; urgency=medium

  * Upload to experimental for cbindgen 0.19 and rustc >= 1.51.

That would make it seem that if you want firefox 91, you will need to
enable experimental sources on your system and install from there.  Or
you can wait for the dependencies to make their way to unstable (will
require the maintainers to upload them into unstable) and then the
buildds will be able to build and distributed the newer firefox packages
in unstable.

Regards,

-Roberto

[0] https://buildd.debian.org/status/package.php?p=firefox
[1] 
https://tracker.debian.org/news/1248046/accepted-firefox-9101-2-source-into-experimental/

-- 
Roberto C. Sánchez

Re: APT testing and unstabe Firefox: can't find newest version from unstable

[Eike Lantzsch ZP6CGE]

On Samstag, 4. September 2021 07:50:19 -04 Daniel M. wrote:
> To my understanding, unstable has 91.0.1-1 and experimental has
> 91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.

Unstable here still with 88.0.1-1 not 91...
same as OP
Have no time neither today nor tomorrow to look into prob.
--
Eike Lantzsch ZP6CGE

Re: sources.list pour Debian Testing x86-64 en region parisienne

[Jérémy Prego]

Le 04/09/2021 à 08:06, Basile Starynkevitch a écrit :

Bonjour la liste,

Sur un portable x86-64 mon /etc/apt/sources.list (édité maintes fois à 
la main) contient actuellement




guiseppe# cat /etc/apt/sources.list

deb     http://ftp.lip6.fr/pub/linux/distributions/debian/ testing 
main contrib non-free

deb http://ftp.proxad.net/debian/ testing main contrib non-free
deb http://security.debian.org/debian-security bookworm-security main 
contrib non-free
deb-src http://security.debian.org/debian-security bookworm-security 
main contrib non-free


deb-src     http://ftp.lip6.fr/pub/linux/distributions/debian/ 
testing main contrib non-fre


mais aptitude update donne les erreurs suivantes
guiseppe# aptitude update
Hit http://security.debian.org/debian-security bookworm-security 
InRelease

Get: 1 http://ftp.proxad.net/debian testing InRelease [112 kB]
Hit http://dl.google.com/linux/chrome/deb stable InRelease
Get: 2 http://ftp.lip6.fr/pub/linux/distributions/debian testing 
InRelease [112 kB]

Fetched 224 kB in 1s (257 kB/s)
E: Repository 'http://ftp.proxad.net/debian testing InRelease' changed 
its 'Codename' value from 'bullseye' to 'bookworm'
E: Repository 'http://ftp.lip6.fr/pub/linux/distributions/debian 
testing InRelease' changed its 'Codename' value from 'bullseye' to 
'bookworm'


au lieu de aptitude update, fait un apt update et répond "o" a la 
question posé si tu acceptes le changement de code de version. il y a un 
moyen de faire ça avec aptitude, mais je ne m'en souviens plus.


Jerem

E: Failed to download some files
W: Failed to fetch 
http://ftp.lip6.fr/pub/linux/distributions/debian/dists/testing/InRelease:

W: Failed to fetch http://ftp.proxad.net/debian/dists/testing/InRelease:
E: Some index files failed to download. They have been ignored, or old 
ones used instead.



Où est mon erreur?


PS. Je fais un petit cours lundi sur GNU bash. Si vous avez quelques 
minutes pour relire mes transparents, envoyez moi un courriel.


NB. Je developpe aussi avec d'autres http://refpersys.org/  Si ça 
vous intéresse, faites moi signe

Re: Re: APT testing and unstabe Firefox: can't find newest version from unstable

[Daniel M.]

To my understanding, unstable has 91.0.1-1 and experimental has
91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.

Re: Question about DMARK and flood of mails...

[Jean-François Bachelet]

Hello ^^)


Le 04/09/2021 à 11:37, NoSpam a écrit :

Bonjour

Le 04/09/2021 à 03:44, Jean-François Bachelet a écrit :

Hello ^^)


en ce moment je suis floodé de mails 'dmark aggregate reports' de la 
part de serveurs que j'ai pas contacté, pour un domaine (qui 
m'appartient) mais qui n'envoie pas de mails sauf si c'est moi qui le 
fait... et le dernier date de plus d'un mois.


c'est quoi ce binz ? une idée ?


On vous prévient que des courriels sont envoyés avec une/des adresse-s 
de votre domaine, les serveur MX expéditeurs, etc. Bref, quelle est 
l'utilisation faite de votre domaine sur Internet.


https://www.dmarcanalyzer.com/dmarc-aggregate-reports/


ouai, bin justement comme je le dit plus haut je n'en envoie pas. le 
serveur de mail est hors ligne. donc d'où ça sort ces m*rdes ? des 
usurpations d'identité mail ?


JEff

Re: Sound input source detected but not capturing

[Marko Randjelovic]

On Sat, 04 Sep 2021 07:47:02 +0530
Pankaj Jangid  wrote:

> Marko Randjelovic  writes:
> 
> > Did you make sure:
> >
> > 1. correct device is set to record from 
> > 2. recording is enabled
> > 3. input volume is large enough  
> 
> I guess I have only one device so there is nothing to set.

I meant 'input source'. On my machine it can be:

'Rear Mic' 'Front Mic' 'Line' 'CD'

> 
> How is recording enabled? Do I need to add myself to some group? I am
> member of followin groups: pankaj cdrom floppy sudo audio dip video
> plugdev netdev bluetooth scanner.

You are member of audio group, so that's fine. By 'recording enabled I
meant on/off switch.

> 
> I have tried to set input volume using various knobs in gnome settings
> as well as alsamixer. It did not work.
> 
> >> If you are not sure send the output of command 'amixer' so we can check.  
> >
> > In fact, unless you have only one sound device, the command should
> > be 'amixer -cN' where N is the number of your sound card and can change
> > after reboot. So first you have to type 'cat /proc/asound/cards' to
> > find your card number.  
> 
> Output of ‘amixer’
> 
> --8<---cut here---start->8---
> $ amixer
> Simple mixer control 'Master',0
>   Capabilities: pvolume pswitch pswitch-joined
>   Playback channels: Front Left - Front Right
>   Limits: Playback 0 - 65536
>   Mono:
>   Front Left: Playback 64880 [99%] [on]
>   Front Right: Playback 64880 [99%] [on]
> Simple mixer control 'Capture',0
>   Capabilities: cvolume cswitch cswitch-joined
>   Capture channels: Front Left - Front Right
>   Limits: Capture 0 - 65536
>   Front Left: Capture 65540 [100%] [on]
>   Front Right: Capture 65540 [100%] [on]
> --8<---cut here---end--->8---
> 
> Output of ‘amixer -c0’
> 
> --8<---cut here---start->8---
> $ cat /proc/asound/cards
>  0 [PCH]: HDA-Intel - HDA Intel PCH
>   HDA Intel PCH at 0xb1328000 irq 137
> 
> $ amixer -c0
> Simple mixer control 'Master',0
>   Capabilities: pvolume pvolume-joined pswitch pswitch-joined
>   Playback channels: Mono
>   Limits: Playback 0 - 87
>   Mono: Playback 87 [100%] [0.00dB] [on]
> Simple mixer control 'Headphone',0
>   Capabilities: pvolume pswitch
>   Playback channels: Front Left - Front Right
>   Limits: Playback 0 - 87
>   Mono:
>   Front Left: Playback 0 [0%] [-65.25dB] [off]
>   Front Right: Playback 0 [0%] [-65.25dB] [off]
> Simple mixer control 'Speaker',0
>   Capabilities: pvolume pswitch
>   Playback channels: Front Left - Front Right
>   Limits: Playback 0 - 87
>   Mono:
>   Front Left: Playback 87 [100%] [0.00dB] [on]
>   Front Right: Playback 87 [100%] [0.00dB] [on]
> Simple mixer control 'PCM',0
>   Capabilities: pvolume
>   Playback channels: Front Left - Front Right
>   Limits: Playback 0 - 255
>   Mono:
>   Front Left: Playback 254 [100%] [-0.20dB]
>   Front Right: Playback 254 [100%] [-0.20dB]
> Simple mixer control 'Mic Boost',0
>   Capabilities: volume
>   Playback channels: Front Left - Front Right
>   Capture channels: Front Left - Front Right
>   Limits: 0 - 3
>   Front Left: 3 [100%] [30.00dB]
>   Front Right: 3 [100%] [30.00dB]
> Simple mixer control 'IEC958',0
>   Capabilities: pswitch pswitch-joined
>   Playback channels: Mono
>   Mono: Playback [off]
> Simple mixer control 'IEC958',1
>   Capabilities: pswitch pswitch-joined
>   Playback channels: Mono
>   Mono: Playback [on]
> Simple mixer control 'IEC958',2
>   Capabilities: pswitch pswitch-joined
>   Playback channels: Mono
>   Mono: Playback [on]
> Simple mixer control 'IEC958',3
>   Capabilities: pswitch pswitch-joined
>   Playback channels: Mono
>   Mono: Playback [on]
> Simple mixer control 'IEC958',4
>   Capabilities: pswitch pswitch-joined
>   Playback channels: Mono
>   Mono: Playback [on]
> Simple mixer control 'Capture',0
>   Capabilities: cvolume cswitch
>   Capture channels: Front Left - Front Right
>   Limits: Capture 0 - 63
>   Front Left: Capture 63 [100%] [30.00dB] [on]
>   Front Right: Capture 63 [100%] [30.00dB] [on]
> Simple mixer control 'Auto-Mute Mode',0
>   Capabilities: enum
>   Items: 'Disabled' 'Enabled'
>   Item0: 'Enabled'
> Simple mixer control 'Internal Mic Boost',0
>   Capabilities: volume
>   Playback channels: Front Left - Front Right
>   Capture channels: Front Left - Front Right
>   Limits: 0 - 3
>   Front Left: 0 [0%] [0.00dB]
>   Front Right: 0 [0%] [0.00dB]
> --8<---cut here---end--->8---
> 

Your control 'Capture',0 is turned on and volume is at maximum, so
that's fine, but you don't have 'input source' control. On my machine
output of 'amixer -c0' gives among other controls the following:

Simple mixer control 'Input Source',0
  Capabilities: cenum
  Items: 'Rear Mic' 'Front Mic' 'Line' 'CD'
  Item0: 'Rear Mic'

I suppose this is the reason why your capture is not working, but don't
know how to fix it. You might try to install kernel 

Re: Sound input source detected but not capturing

[Andrew M.A. Cater]

On Fri, Sep 03, 2021 at 10:52:45PM +0530, Pankaj Jangid wrote:
> I have a fresh Bullseye installation on a laptop. Sound output is
> working. But the input is not working. The device is detected.
> 
> --8<---cut here---start->8---
> $ arecord -l
>  List of CAPTURE Hardware Devices 
> card 0: PCH [HDA Intel PCH], device 0: ALC236 Analog [ALC236 Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> --8<---cut here---end--->8---
> 
> In the gnome settings, input is showing built-in microphone but there is
> not movement in the capturing indicator.
> 
> alsamixer is also showing the sound card (F6) - HDA Intel PCH.
> 

Very new laptop? Does it need Intel firmware for the soundcard? 
firmware-intel-sound from non-free? 

https://packages.debian.org/bullseye/firmware-intel-sound

All the very best, as ever,

Andy Cater

Re: How to update Debian 11 source.list to testing?

[Andrew M.A. Cater]

On Fri, Sep 03, 2021 at 10:17:21AM -0400, Roberto C. Sánchez wrote:
> On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote:
> > I just installed Debian using netinstall image. I thought I install testing 
> > version, but apparently it's Debian 11. So now my source.list looks like 
> > below:
> > 
> >     deb http://deb.debian.org/debian/ bullseye main non-free contrib
> >     deb-src http://deb.debian.org/debian/ bullseye main non-free contrib
> > 
> >     deb http://security.debian.org/debian-security bullseye-security main 
> > contrib non-free
> >     deb-src http://security.debian.org/debian-security bullseye-security 
> > main contrib non-free
> > 
> >     deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
> >     deb-src http://deb.debian.org/debian/ bullseye-updates main contrib 
> > non-free
> > 
> > I want to switch to testing version. In the past I just change the keyword 
> > from e.g. bullseye to testing, and generally there is no weird problem. But 
> > I read on the internet saying that the source.list should not mix up with 
> > different version. For instance, Debian 11 with testing. So I am wondering 
> > if there is a better way to switch to testing? Or reinstalling is the only 
> > way to go?
> > 
> If you change all instances of bullseye -> testing, then you are not
> mixing.  Go ahead with that, modulo the standard caveats associated with
> running testing.  The problem would come if you tried to include both
> bullseye *and* testing sources in your sources.list.  Then you might
> create very difficult to resolve problems.
> 
> You might consider using bookwork rather than testing, however.  That is
> the name of the testing release and unless you specifically want to
> continue tracking testing even after bookwork is released, it is
> probably better for most use cases to use the specific release code name
> rather than stable or testing.
> 
> Regards,
> 
> -Roberto
> 
> -- 
> Roberto C. Sánchez
> 

Small thing: the release that should eventually become Debian 12 - that is 
currently also referred to as testing is bookworm NOT bookwork.

Given that even the CD release team were consistently mistyping it - and
mental autocorrect will change it automatically - that's unsurprising.

In general: referring to current/future releases by codeword is a good 
thing - it does keep you consistent.

Mixing releases is having concurrent lines for stable AND testing in the 
same file (also testing and unstable). It's not a real sin, but you have to
know which bits come from where and how to resolve breakages. With the
passing of time, you're more or less guaranteed to be running testing in
that scenario anyway.

https://wiki.debian.org/DontBreakDebian is relevant here to most people 
who would want to install a random .deb from a third party vendor or 
random website.

All the very best, as ever,

Andy Cater

Re: sources.list pour Debian Testing x86-64 en region parisienne

[Eric Degenetais]

Le sam. 4 sept. 2021 09:49, Basile Starynkevitch 
a écrit :

>
> On 9/4/21 9:29 AM, rok wrote:
> > bonjour,
>

Bonjour

> >
> > http://refpersys.org/
> >
> > est une connexion non sécurisées et est bloquée par firefox;
>
>
> Qui peut m'expliquer l'intérêt de HTTPS (encrypté) par rapport à HTTP
> (textuel) sur un site web en lecture seule?
>
Cela dépend du type de contenu offert. Pour du texte c'est sans importance.
Cependant le site semble offrir des téléchargements d'exécutables,
également en HTTP clair.

>
>
> De mon point de vue, encrypter le protocole dans le serveur, et le
> décoder dans votre navigateur, ne fait que contribuer au réchauffement
> climatique: consommation de calcul (donc d'energie) inutile sur le
> serveur et sur le client.
>


>
> Les attaques "man in the middle" pour un petit site en lecture seule me
> paraissent improbables et dérisoires.
>
C'est là que l'offre de télécharger du code change la donne. Bien sûr ce
n'est pas le sac à point que représenterait une mitm sur les dépôts de
Debian ou Windows, mais subvertir un téléchargement de code c'est un moyen
d'infecter les machines de ceux qui téléchargent et exécutent le code.

>
>
>
> --
> Basile Starynkevitch  
> (only mine opinions / les opinions sont miennes uniquement)
> 92340 Bourg-la-Reine, France
> web page: starynkevitch.net/Basile/
>
>

Re: which vs. type, and recursion?

[Richard Hector]

On 4/09/21 9:26 pm, Brian wrote:

On Sat 04 Sep 2021 at 21:21:38 +1200, Richard Hector wrote:


Greg Wooledge pointed out in another thread that 'type' is often better than
'which' for finding out what kind of command you're about to run, and where
it comes from.

A quick test, however, threw up another issue:

richard@zircon:~$ type ls
ls is aliased to `ls --color=auto'

Great, so it's an alias. But what is the underlying ls? How do I find out? I
did find out, by unaliasing ls and trying again, which showed that it's an
actual executable, /usr/bin/ls, and not a shell builtin.

But is there an easier/better way? Can 'type' be asked to recursively decode
aliases?

I looked at the relevant section of bash(1) (when I eventually found it),
but was not particularly enlightened.


Use 'help type' and try 'type -a ls'.



That ('help type') is much more readable than bash(1), thanks. I think I 
might have known about 'help', but had forgotten ...


Cheers,
Richard

Re: Question about DMARK and flood of mails...

[NoSpam]

Bonjour

Le 04/09/2021 à 03:44, Jean-François Bachelet a écrit :

Hello ^^)


en ce moment je suis floodé de mails 'dmark aggregate reports' de la 
part de serveurs que j'ai pas contacté, pour un domaine (qui 
m'appartient) mais qui n'envoie pas de mails sauf si c'est moi qui le 
fait... et le dernier date de plus d'un mois.


c'est quoi ce binz ? une idée ?


On vous prévient que des courriels sont envoyés avec une/des adresse-s 
de votre domaine, les serveur MX expéditeurs, etc. Bref, quelle est 
l'utilisation faite de votre domaine sur Internet.


https://www.dmarcanalyzer.com/dmarc-aggregate-reports/

--
Daniel

Re: which vs. type, and recursion?

[Brian]

On Sat 04 Sep 2021 at 21:21:38 +1200, Richard Hector wrote:

> Greg Wooledge pointed out in another thread that 'type' is often better than
> 'which' for finding out what kind of command you're about to run, and where
> it comes from.
> 
> A quick test, however, threw up another issue:
> 
> richard@zircon:~$ type ls
> ls is aliased to `ls --color=auto'
> 
> Great, so it's an alias. But what is the underlying ls? How do I find out? I
> did find out, by unaliasing ls and trying again, which showed that it's an
> actual executable, /usr/bin/ls, and not a shell builtin.
> 
> But is there an easier/better way? Can 'type' be asked to recursively decode
> aliases?
> 
> I looked at the relevant section of bash(1) (when I eventually found it),
> but was not particularly enlightened.

Use 'help type' and try 'type -a ls'.

-- 
Brian.

Re: which vs. type, and recursion?

[john doe]

On 9/4/2021 11:21 AM, Richard Hector wrote:

Greg Wooledge pointed out in another thread that 'type' is often better
than 'which' for finding out what kind of command you're about to run,
and where it comes from.

A quick test, however, threw up another issue:

richard@zircon:~$ type ls
ls is aliased to `ls --color=auto'

Great, so it's an alias. But what is the underlying ls? How do I find
out? I did find out, by unaliasing ls and trying again, which showed
that it's an actual executable, /usr/bin/ls, and not a shell builtin.

But is there an easier/better way? Can 'type' be asked to recursively
decode aliases?

I looked at the relevant section of bash(1) (when I eventually found
it), but was not particularly enlightened.



My understanding is that 'type' is to find the type while 'which' is to
find the executable path.

--
John Doe

Re: icewm anomaly after bullseye upgrade

[Andrew M.A. Cater]

On Sat, Sep 04, 2021 at 01:58:41AM -0400, Bob Bernstein wrote:
> On Fri, 3 Sep 2021, Michael Lange wrote:
> 
> > according to https://ice-wm.org/man/icewm-preferences the syntax for
> > using a bold font should rather be:
> 
> > ActiveTaskBarFontNameXft=”sans-serif:size=12:bold” .
> 
> Ah. RTFM still applies.
> 
> That did the trick for me. Thank You Sir!
> 
> > I have some doubt though, that this has anything to do with your
> > original problem.
> 
> That is correct. I did resolve my problem with 'WorkspaceNames=' not
> governing the number of workspaces shown on the Taskbar, but my error was so
> stupid I am ashamed to reveal it here in front of everyone, and probably
> won't even tell anyone off-list.
> 
> As a rule I am not above posting really dumb questions (no wisecracks, thank
> you), but that one was beyond anything even I could suffer.

No dumb questions ever. After 23 years around Debian, I still find the 
best and quickest way to find an error is to stare at it for three days,
ask someone else to look at it - and they find it in 30 seconds.

Smart wisecrack answers / demeaning someone else's efforts (always provided
they show they've done something) - that's another thing.

It's very worthwhile to think we have all sorts of people with all sorts
of experience and expertise lurking here and that somebody will know the
answer / direct you to resources to find it / have an "Aha!" moment and
sort out their own puzzle when they see you raise it.

All best, as ever,

Andy Cater

Re: Tips/advice for installing latest version of fzf?

[Richard Hector]

On 1/09/21 3:32 am, Greg Wooledge wrote:

In bash, which is *not* a shell builtin -- it's a separate program,
/usr/bin/which.


Well _that_ took a while to parse correctly :-) I know bash is not a 
shell builtin, that would be weird ...


Cheers,
Richard

which vs. type, and recursion?

[Richard Hector]

Greg Wooledge pointed out in another thread that 'type' is often better 
than 'which' for finding out what kind of command you're about to run, 
and where it comes from.


A quick test, however, threw up another issue:

richard@zircon:~$ type ls
ls is aliased to `ls --color=auto'

Great, so it's an alias. But what is the underlying ls? How do I find 
out? I did find out, by unaliasing ls and trying again, which showed 
that it's an actual executable, /usr/bin/ls, and not a shell builtin.


But is there an easier/better way? Can 'type' be asked to recursively 
decode aliases?


I looked at the relevant section of bash(1) (when I eventually found 
it), but was not particularly enlightened.


Cheers,
Richard

Re: sources.list pour Debian Testing x86-64 en region parisienne

[Basile Starynkevitch]

Pour les autres, voici mon /etc/apt/sources.list qui marche (en Île de 
France à Bourg La Reine)



# fichier /etc/apt/sources.list sur guiseppe
deb     http://ftp.lip6.fr/pub/linux/distributions/debian/ testing 
main contrib non-free
deb-src  http://ftp.lip6.fr/pub/linux/distributions/debian/   testing 
main contrib non-free
deb http://ftp.proxad.net/pub/Distributions_Linux/debian/ testing main 
contrib non-free
deb-src http://ftp.proxad.net/pub/Distributions_Linux/debian/ testing 
main contrib non-free
deb http://security.debian.org/debian-security bookworm-security main 
contrib non-free
deb-src http://security.debian.org/debian-security bookworm-security 
main contrib non-free

deb http://ftp2.fr.debian.org/debian/  testing main contrib non-free


--
Basile Starynkevitch  
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

Re: Clamav question ^^)

[Jean-François Bachelet]

HEllo ^^)

Le 04/09/2021 à 09:32, l0f...@tuta.io a écrit :

Bonjour Jeff,

4 sept. 2021, 02:23 de jfbache...@free.fr:


Le 03/09/2021 à 16:10, Luc Novales a écrit :


Pourquoi penses tu que c’est une vieille lib ?


Parce ce que c'est que disent les auteurs du logiciel dans leur propre site, ce 
que je cite dans mon mel en vient directement.

je te le remet :


"I upgraded to the latest stable version but I still get the
message "/Your ClamAV installation is OUTDATED/", why?


Make sure there is really only one version of ClamAV installed on your system:

|whereis freshclam whereis clamscan |

--> Also make sure that you haven't got old libraries (|libclamav.so*|) lying 
around your filesystem. You can verify it using:

|ldd $(which freshclam)" |


si tu veux vérifier c'est la : > https://docs.clamav.net/faq/faq-upgrade.html


Je pense que la documentation ClamAV se veut la plus universelle possible.

La phrase "Also make sure that you haven't got old libraries (libclamav.so*) lying around your 
filesystem" ne doit certainement pas être comprise comme "libclamav.so = librairie obsolète" 
mais plutôt comme "vérifiez que votre version de libclamav.so n'est pas obsolète".


ok, donc il vaudrait mieux qu'ils mettent 'old versions of libraries 
(libclamav.so) lying around...' ce serait moins prône à mauvaise 
traduction...




Autrement dit c'est le "*" final qui est important dans la phrase (par exemple 
si tu fais tourner aujourd'hui libclamav.so.7 alors il y a certainement un problème...).

Maintenant tu utilises Debian qui fournit des *paquets* déjà tout prêts et 
cohérents donc commencer à jouer avec les librairies me parait périlleux...


oki c'est noté, merkitouplin ^^)


Jeff

Re: sources.list pour Debian Testing x86-64 en region parisienne

[Basile Starynkevitch]

On 9/4/21 9:29 AM, rok wrote:

bonjour,

http://refpersys.org/

est une connexion non sécurisées et est bloquée par firefox;



Qui peut m'expliquer l'intérêt de HTTPS (encrypté) par rapport à HTTP 
(textuel) sur un site web en lecture seule?



De mon point de vue, encrypter le protocole dans le serveur, et le 
décoder dans votre navigateur, ne fait que contribuer au réchauffement 
climatique: consommation de calcul (donc d'energie) inutile sur le 
serveur et sur le client.



Les attaques "man in the middle" pour un petit site en lecture seule me 
paraissent improbables et dérisoires.




--
Basile Starynkevitch  
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

Re: sources.list pour Debian Testing x86-64 en region parisienne

[rok]

bonjour,

http://refpersys.org/

est une connexion non sécurisées et est bloquée par firefox;


Le 4/09/21 à 08:06, Basile Starynkevitch a écrit :

Bonjour la liste,

Sur un portable x86-64 mon /etc/apt/sources.list (édité maintes fois à 
la main) contient actuellement




guiseppe# cat /etc/apt/sources.list

deb     http://ftp.lip6.fr/pub/linux/distributions/debian/ testing 
main contrib non-free

deb http://ftp.proxad.net/debian/ testing main contrib non-free
deb http://security.debian.org/debian-security bookworm-security main 
contrib non-free
deb-src http://security.debian.org/debian-security bookworm-security 
main contrib non-free


deb-src     http://ftp.lip6.fr/pub/linux/distributions/debian/ 
testing main contrib non-fre


mais aptitude update donne les erreurs suivantes
guiseppe# aptitude update
Hit http://security.debian.org/debian-security bookworm-security 
InRelease

Get: 1 http://ftp.proxad.net/debian testing InRelease [112 kB]
Hit http://dl.google.com/linux/chrome/deb stable InRelease
Get: 2 http://ftp.lip6.fr/pub/linux/distributions/debian testing 
InRelease [112 kB]

Fetched 224 kB in 1s (257 kB/s)
E: Repository 'http://ftp.proxad.net/debian testing InRelease' changed 
its 'Codename' value from 'bullseye' to 'bookworm'
E: Repository 'http://ftp.lip6.fr/pub/linux/distributions/debian 
testing InRelease' changed its 'Codename' value from 'bullseye' to 
'bookworm'

E: Failed to download some files
W: Failed to fetch 
http://ftp.lip6.fr/pub/linux/distributions/debian/dists/testing/InRelease:

W: Failed to fetch http://ftp.proxad.net/debian/dists/testing/InRelease:
E: Some index files failed to download. They have been ignored, or old 
ones used instead.



Où est mon erreur?


PS. Je fais un petit cours lundi sur GNU bash. Si vous avez quelques 
minutes pour relire mes transparents, envoyez moi un courriel.


NB. Je developpe aussi avec d'autres http://refpersys.org/  Si ça 
vous intéresse, faites moi signe

Re: Clamav question ^^)

[l0f4r0]

Bonjour Jeff,

4 sept. 2021, 02:23 de jfbache...@free.fr:

> Le 03/09/2021 à 16:10, Luc Novales a écrit :
>
>> Pourquoi penses tu que c’est une vieille lib ?
>>
> Parce ce que c'est que disent les auteurs du logiciel dans leur propre site, 
> ce que je cite dans mon mel en vient directement.
>
> je te le remet :
>
>
> "I upgraded to the latest stable version but I still get the
> message "/Your ClamAV installation is OUTDATED/", why?
> 
>
> Make sure there is really only one version of ClamAV installed on your system:
>
> |whereis freshclam whereis clamscan |
>
> --> Also make sure that you haven't got old libraries (|libclamav.so*|) lying 
> around your filesystem. You can verify it using:
>
> |ldd $(which freshclam)" |
>
>
> si tu veux vérifier c'est la : > https://docs.clamav.net/faq/faq-upgrade.html
>
Je pense que la documentation ClamAV se veut la plus universelle possible.

La phrase "Also make sure that you haven't got old libraries (libclamav.so*) 
lying around your filesystem" ne doit certainement pas être comprise comme 
"libclamav.so = librairie obsolète" mais plutôt comme "vérifiez que votre 
version de libclamav.so n'est pas obsolète".
Autrement dit c'est le "*" final qui est important dans la phrase (par exemple 
si tu fais tourner aujourd'hui libclamav.so.7 alors il y a certainement un 
problème...).

Maintenant tu utilises Debian qui fournit des *paquets* déjà tout prêts et 
cohérents donc commencer à jouer avec les librairies me parait périlleux...

l0f4r0

Re: cups no puedo ingresar

[Camaleón]

El 2021-09-04 a las 08:46 +0200, Camaleón escribió:

> El 2021-09-03 a las 17:00 -0300, Marcelo Eduardo Giordano escribió:
> 
> > El 3/9/21 a las 03:28, Camaleón escribió:
> > > El 2021-09-02 a las 18:49 -0300, Marcelo Eduardo Giordano escribió:
> > > 
> > > > Tengo Debian bullseye kde y he cambiado unas configuraciones de cups 
> > > > por lo
> > > > cual me pidió mi usuario root y se reinició.
> > > > 
> > > > Ahora no puedo ingresar a localhost:631 me dice "localhost rechazó la
> > > > conexión"
> > > > 
> > > > No tengo firewall instalado
> > > Comprueba que el servicio esté iniciado «service cups status» y manda
> > > también la salida de la orden «lpstat -t».
> > > 
> > > 
> > Gracias por contestar. Esto me dicen los comandos. Puedo imprimir
> > perfectamente desde la computadora, aunque por supuesto que no en red que es
> > lo que quiero lograr
> > 
> > antonella@Antonella:~$ service cups status
> 
> (...)
> 
> Todo parece correcto. El servicio de impresión está ejecutándose y 
> puedes ver las impresoras configuradas.
> 
> Manda la salida de esta orden, para comprobar que tengas configurado y 
> habilitado el acceso al servidor web desde el equipo local:
> 
> grep -i listen /etc/cups/cupsd.conf

(...)

Mejor sube el archivo completo a https://paste.debian.net/ o cualquier 
otro sitio para que veamos el contennido completo del archivo 
/etc/cups/cupsd.conf, así no nos dejamos nada por revisar.

Saludos,

-- 
Camaleón 

Re: sources.list pour Debian Testing x86-64 en region parisienne

[steve]

J'ai testé depuis chez moi.



guiseppe# cat /etc/apt/sources.list

deb     http://ftp.lip6.fr/pub/linux/distributions/debian/ testing main contrib 
non-free


cette ligne ne passe pas, ce qui est d'ailleurs bizarre puisque le
fichier InRelease existe.

Mais je pense qu'elle est redondante avec la suivante. Donc tu peux la
supprimer sans autre.


deb http://ftp.proxad.net/debian/ testing main contrib non-free
deb http://security.debian.org/debian-security bookworm-security main contrib 
non-free
deb-src http://security.debian.org/debian-security bookworm-security main 
contrib non-free

deb-src     http://ftp.lip6.fr/pub/linux/distributions/debian/ testing main 
contrib non-fre


le reste passe.

Re: cups no puedo ingresar

[Camaleón]

El 2021-09-03 a las 17:00 -0300, Marcelo Eduardo Giordano escribió:

> El 3/9/21 a las 03:28, Camaleón escribió:
> > El 2021-09-02 a las 18:49 -0300, Marcelo Eduardo Giordano escribió:
> > 
> > > Tengo Debian bullseye kde y he cambiado unas configuraciones de cups por 
> > > lo
> > > cual me pidió mi usuario root y se reinició.
> > > 
> > > Ahora no puedo ingresar a localhost:631 me dice "localhost rechazó la
> > > conexión"
> > > 
> > > No tengo firewall instalado
> > Comprueba que el servicio esté iniciado «service cups status» y manda
> > también la salida de la orden «lpstat -t».
> > 
> > 
> Gracias por contestar. Esto me dicen los comandos. Puedo imprimir
> perfectamente desde la computadora, aunque por supuesto que no en red que es
> lo que quiero lograr
> 
> antonella@Antonella:~$ service cups status

(...)

Todo parece correcto. El servicio de impresión está ejecutándose y 
puedes ver las impresoras configuradas.

Manda la salida de esta orden, para comprobar que tengas configurado y 
habilitado el acceso al servidor web desde el equipo local:

grep -i listen /etc/cups/cupsd.conf

Recuerda que, de manera predeterminada, sólo se permite el acceso a la 
interfaz web de Cups desde el equipo donde se encuentra instalado el 
servicio de impresión.

Saludos,

-- 
Camaleón 

Re: smart fans

[Emanuel Berg]

David Christensen wrote:

>> OK, changed.
>
> Your data format still has issues.

You seem to have got the old file again, check it out again,
because some of those issues have already been
mentioned/fixed:

  https://dataswamp.org/~incal/ebchw/cpu.txt

-- 
underground experts united
https://dataswamp.org/~incal

sources.list pour Debian Testing x86-64 en region parisienne

[Basile Starynkevitch]

Bonjour la liste,

Sur un portable x86-64 mon /etc/apt/sources.list (édité maintes fois à 
la main) contient actuellement




guiseppe# cat /etc/apt/sources.list

deb     http://ftp.lip6.fr/pub/linux/distributions/debian/ testing 
main contrib non-free

deb http://ftp.proxad.net/debian/ testing main contrib non-free
deb http://security.debian.org/debian-security bookworm-security main 
contrib non-free
deb-src http://security.debian.org/debian-security bookworm-security 
main contrib non-free


deb-src     http://ftp.lip6.fr/pub/linux/distributions/debian/ testing 
main contrib non-fre


mais aptitude update donne les erreurs suivantes
guiseppe# aptitude update
Hit http://security.debian.org/debian-security bookworm-security InRelease
Get: 1 http://ftp.proxad.net/debian testing InRelease [112 kB]
Hit http://dl.google.com/linux/chrome/deb stable InRelease
Get: 2 http://ftp.lip6.fr/pub/linux/distributions/debian testing 
InRelease [112 kB]

Fetched 224 kB in 1s (257 kB/s)
E: Repository 'http://ftp.proxad.net/debian testing InRelease' changed 
its 'Codename' value from 'bullseye' to 'bookworm'
E: Repository 'http://ftp.lip6.fr/pub/linux/distributions/debian testing 
InRelease' changed its 'Codename' value from 'bullseye' to 'bookworm'

E: Failed to download some files
W: Failed to fetch 
http://ftp.lip6.fr/pub/linux/distributions/debian/dists/testing/InRelease:

W: Failed to fetch http://ftp.proxad.net/debian/dists/testing/InRelease:
E: Some index files failed to download. They have been ignored, or old 
ones used instead.



Où est mon erreur?


PS. Je fais un petit cours lundi sur GNU bash. Si vous avez quelques 
minutes pour relire mes transparents, envoyez moi un courriel.


NB. Je developpe aussi avec d'autres http://refpersys.org/  Si ça 
vous intéresse, faites moi signe



--
Basile Starynkevitch  
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/