Re: Authentication required message window after nvidia drivers installation.

[Andrei POPESCU]

On Vi, 21 ian 22, 15:24:29, Thanos Katsiolis wrote:
> Hello,
> 
> the title of the post says pretty much everything.
> I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA
> drivers as described in Debian wiki NVIDIA Proprietary Driver
>  for Debian 11.2.
> 
> The message appears when an Application starts or when a window from an
> application opens. Some applications were left with a blank screen
> when launching, but after a restart, when I press escape on the message,
> the application starts normally.
> Any ideas on how to fix it?

This is likely completely unrelated to installing the NVIDIA drivers.

Please provide more information about your Desktop Environment and the 
applications that exhibit this behaviour.

Any other non-Debian software on the system?

The output of 'id' in a terminal might provide some hints as well (feel 
free to obscure your user and group name, the interesting part is what 
other groups, if any, your user is a member of).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

is it possible to install bullseye by copy whole disk?

[lou]

i've installed bullseye on usb disk

can i copy it to hard disk (sda2) and make necessary change in 
/etc/fstab and


then update grub of usb disk to boot sda2?

Thanks!

Re: firejail: changing Ethernet network adapter name is breaking Firefox profile

[Andrei POPESCU]

On Lu, 17 ian 22, 22:43:49, piorunz wrote:
> 
> Problem is, every now and then, Ethernet adapter name changes, from
> enp5s0 to enp6s0 for example. 

Those names are supposed to be stable.

Are you doing any changes to the hardware when that happens?


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: AMD EPYC throttled to 400 mhz

[Andrei POPESCU]

On Lu, 17 ian 22, 22:08:43, Alexander V. Makartsev wrote:
> On 17.01.2022 18:40, Simon Kainz wrote:
> > 
> > I did not set/change governor/driver settings, this is a stock debian
> > kernel.
> Is the server platform runs latest BIOS and firmware?
> Things I'd try first if I was in your place.
> I always flash latest firmware available as a pre-sale procedure, or during
> server installation.

Installing amd64-microcode (from nonfree) might be a good idea as well.
 
Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: hostname is being reset, killing net on reboot

[tomas]

On Fri, Jan 21, 2022 at 11:51:20PM -0500, gene heskett wrote:

[...]

> This is all well and good, Greg, but it still does NOT give a clue what 
> todo when the system picks a fictitious route out of its rear.

Start debugging from bottom to top. For the first round, just deal in IP
addresses and routes (those are set in term of IP addresses, not names).
Forget about names.

Once that part is flying, tackle names :)


> And that IS my squawk.
> 
> I did find a fix as posted earlier, but I doubt it will work under a pine 
> tree in Wash State where these two cards will get mailed to once I get a 
> realtime kernel installed and working. And I've got a v5.16.0-rc6-rt12, 
> downright bleeding edge to install tomorrow.

Pethaps you'll have to have stern words with your DHCP server. This may
be the one giving your machines their weird IP addresses and (at least
part of the) routes.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: hostname is being reset, killing net on reboot

[tomas]

On Fri, Jan 21, 2022 at 10:46:35PM -0500, Greg Wooledge wrote:

[...]

> Well, yes.  The "hostname" command sets the current hostname, which resides
> in memory only.  It has no permanent effect.
> 
> And it has nothing at all to do with IP addresses.  Or DNS.

[...]

> Routing has nothing to do with your system's hostname.  At all.

This is so important that it bears repeating. A couple of times :)

Hostname is a host's notion of its own host name. This can be different
from the name (or names) assigned to its IP addresses by the DNS. A
machine can have zero or IP addresses, and each of those can be known by
zero or more names in the DNS. Heck, several parts of a "split" DNS
world can disagree among them as to which names those IP addresses are
known by.

Of course, giving a host a name unrelated to (some of its) DNS names is
a bad idea in general, because it tends to confuse the heck out of
sysadmins (and in some case of applications: notably, SMTP servers
answer with "Hey, I'm patrick" (using the own hostname [1]): the server
at the other end will run away if it thinks it was talking to peter.

Cheers

[1] Unless you go to some lenghts to configure your SMTP server
otherwise.

-- 
t


signature.asc
Description: PGP signature

Re: hostname is being reset, killing net on reboot

[tomas]

On Fri, Jan 21, 2022 at 07:46:40PM -0500, Greg Wooledge wrote:
> On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> > On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > > > So how do I officially set the hostname so its reboot proof?
> > > 
> > > hostnamectl set hostname [foobar]
> 
> The standard Debian way is to put the desired hostname in /etc/hostname.
> 
> If I'm reading hostnamectl(1) correctly, the command you wanted should
> have a hyphen in it: hostnamectl set-hostname NEWNAME

Clarification: hostnamectl is from the systemd suite. For those using
another init system, put things directly in /etc/hostname.

Reading the source [1], `set-hostname' seems to be obsolete. The magic
word seems to be simply `hostname', these days, at least.

As far as I can see, after making sure the user hasn't made some error,
it passes the buck to some D-Bus service [2], which then does something.
Or not: I stopped my chase there.

For pedestrians (no D-Bus around here), writing to /etc/hostname is
still the way to go. Probably it'll work along with a systemd too.

Cheers

[1] 
https://sources.debian.org/src/systemd/250.3-1/src/hostname/hostnamectl.c/?hl=655#L655
[2] 
https://sources.debian.org/src/systemd/250.3-1/src/hostname/hostnamectl.c/?hl=655#L496

-- 
t


signature.asc
Description: PGP signature

Re: hostname is being reset, killing net on reboot

[gene heskett]

On Friday, January 21, 2022 10:46:35 PM EST Greg Wooledge wrote:
> On Fri, Jan 21, 2022 at 09:34:35PM -0500, gene heskett wrote:
> > /etc/resolv.conf has:
> > search coyote.den
> > nameserver 192.168.xx.1
> > 
> > the search line says to look in the /etc/hosts file, failing that,
> > the
> > nameserver line sends the dns lookup query to the router
> 
> No, that's not correct.
> 
> The config file that says "look in /etc/hosts first, then look in DNS
> next" is /etc/nsswitch.conf.  Specifically, it's the line that begins
> with "hosts:" in that file.
> 
> The "search" line in /etc/resolv.conf means "if I type ftp roadrunner,
> I want it to act as if I had typed ftp roadrunner.coyote.den".
> 
> In other words, it's the default DNS search domain for looking up the
> *other computers* on your local area network.
> 
> > However when I set hostname with hostname, the 169.bs stays out of
> > the
> > picture and networking works the world until a reboot.
> 
> Well, yes.  The "hostname" command sets the current hostname, which
> resides in memory only.  It has no permanent effect.
> 
> And it has nothing at all to do with IP addresses.  Or DNS.
> 
> > Setting the hostname with hostnamectl to the alias in /etc/hosts for
> > this machine, gets me exactly the same hostname but then the route
> > reported by "ip a" is the 169.bs.bs.bs and I can't get out of my
> > shirt pocket to even ping the router at 192.168.xx.1.
> 
> Routing has nothing to do with your system's hostname.  At all.
> 
> At the most basic level, your system's default route is set by whatever
> mechanism sets up your network interfaces.  On Debian, this can be any
> of *several* different pieces of software, depending on what's
> installed and what you've got in your config files.
> 
> In the *most* basic possible configuration, your routing table will be
> one automatic entry for your ethernet interface (created from the IP
> address and netmask which are assigned to that interface), and then one
> "default" route which is assigned for reaching every host that's *not*
> part of your LAN.
> 
> E.g. in /etc/network/interfaces you'd have something like this:
> 
> auto enp2s0
> 
> iface enp2s0 inet static
>   address 192.168.1.21/24
>   gateway 192.168.1.1
> 
> This tells the "ifupdown" software package that you'd like it to manage
> the enp2s0 network interface, assigning the IP address 192.168.1.21
> with a 24-bit netmask, which automatically creates a route to the
> 192.168.1.0/24 network.  In addition, it will create a default route
> via the 192.168.1.1 address.
> 
> None of this has *anything* to do with your system's hostname.
> 
> None of this has *anything* to do with your /etc/hosts file.
> 
> None of this has *anything* to do with DNS.
> 
> Of course, there are many other ways to configure network interfaces in
> Debian.  You might be using Network-Manager, for example.  Or
> systemd's systemd-networkd(8).  Or you might be using
> /etc/network/interfaces but telling it to ask for configuration from
> DHCP.
> 
> Also, by the way, "ip a" does not report routes.  That's "ip r".
> 
> unicorn:~$ ip r
> default via 10.0.0.1 dev lan0
> 10.0.0.0/24 dev lan0 proto kernel scope link src 10.0.0.7
> 
> 
> 
> You're probably still confused.  Let's go over everything again, from
> the beginning.
> 
> Your computer has a *network interface*.  This interface has some kind
> of name.  The names are very complicated and I don't want to introduce
> that particular piece of complexity here.  Let's say that you've
> somehow managed to determine your interface's name.  Let's say, for
> this example, that your interface's name is enp2s0.
> 
> In order for your network interface to *work*, it has to be assigned an
> IP address and a netmask.  This can come from DHCP, or it can come
> from files that you configure on your system.
> 
> With an IP address and a netmask, you will be able to communicate with
> other computers on your *local area network*, by using their IP
> addresses.
> 
> If you have a default route, then you can potentially talk to computers
> *outside* of your LAN.  This default route can come from DHCP, or from
> local files.  E.g. with a properly configured default route, you will
> be able to run commands like "ping 8.8.8.8" and get responses.
> 
> If you'd like to communicate with other computers by name instead of by
> IP addresses, you can either put their names and IP addresses in the
> /etc/hosts file (a simple text file), *or* you can configure your
> computer to use DNS.
> 
> DNS is configured in the /etc/resolv.conf file.  The most basic piece
> consists of "nameserver" lines which contain the IP addresses of DNS
> resolvers which will look up computer names for you.  These nameservers
> can come from DHCP, or they can be configured in your local files.
> 
> Your computer can also have a hostname.  This is how your computer
> identifies itself when it logs things, so that you can tell which
> 

Re: hostname is being reset, killing net on reboot

[Greg Wooledge]

On Fri, Jan 21, 2022 at 09:34:35PM -0500, gene heskett wrote:
> /etc/resolv.conf has:
> search coyote.den
> nameserver 192.168.xx.1
> 
> the search line says to look in the /etc/hosts file, failing that, the 
> nameserver line sends the dns lookup query to the router

No, that's not correct.

The config file that says "look in /etc/hosts first, then look in DNS
next" is /etc/nsswitch.conf.  Specifically, it's the line that begins
with "hosts:" in that file.

The "search" line in /etc/resolv.conf means "if I type ftp roadrunner,
I want it to act as if I had typed ftp roadrunner.coyote.den".

In other words, it's the default DNS search domain for looking up the
*other computers* on your local area network.

> However when I set hostname with hostname, the 169.bs stays out of the 
> picture and networking works the world until a reboot.

Well, yes.  The "hostname" command sets the current hostname, which resides
in memory only.  It has no permanent effect.

And it has nothing at all to do with IP addresses.  Or DNS.

> Setting the hostname with hostnamectl to the alias in /etc/hosts for this 
> machine, gets me exactly the same hostname but then the route reported by 
> "ip a" is the 169.bs.bs.bs and I can't get out of my shirt pocket to even 
> ping the router at 192.168.xx.1.

Routing has nothing to do with your system's hostname.  At all.

At the most basic level, your system's default route is set by whatever
mechanism sets up your network interfaces.  On Debian, this can be any
of *several* different pieces of software, depending on what's installed
and what you've got in your config files.

In the *most* basic possible configuration, your routing table will be
one automatic entry for your ethernet interface (created from the IP
address and netmask which are assigned to that interface), and then one
"default" route which is assigned for reaching every host that's *not*
part of your LAN.

E.g. in /etc/network/interfaces you'd have something like this:

auto enp2s0

iface enp2s0 inet static
address 192.168.1.21/24
gateway 192.168.1.1

This tells the "ifupdown" software package that you'd like it to manage
the enp2s0 network interface, assigning the IP address 192.168.1.21 with
a 24-bit netmask, which automatically creates a route to the 192.168.1.0/24
network.  In addition, it will create a default route via the 192.168.1.1
address.

None of this has *anything* to do with your system's hostname.

None of this has *anything* to do with your /etc/hosts file.

None of this has *anything* to do with DNS.

Of course, there are many other ways to configure network interfaces in
Debian.  You might be using Network-Manager, for example.  Or systemd's
systemd-networkd(8).  Or you might be using /etc/network/interfaces but
telling it to ask for configuration from DHCP.

Also, by the way, "ip a" does not report routes.  That's "ip r".

unicorn:~$ ip r
default via 10.0.0.1 dev lan0 
10.0.0.0/24 dev lan0 proto kernel scope link src 10.0.0.7 



You're probably still confused.  Let's go over everything again, from
the beginning.

Your computer has a *network interface*.  This interface has some kind of
name.  The names are very complicated and I don't want to introduce that
particular piece of complexity here.  Let's say that you've somehow
managed to determine your interface's name.  Let's say, for this example,
that your interface's name is enp2s0.

In order for your network interface to *work*, it has to be assigned an
IP address and a netmask.  This can come from DHCP, or it can come from
files that you configure on your system.

With an IP address and a netmask, you will be able to communicate with
other computers on your *local area network*, by using their IP addresses.

If you have a default route, then you can potentially talk to computers
*outside* of your LAN.  This default route can come from DHCP, or from
local files.  E.g. with a properly configured default route, you will be
able to run commands like "ping 8.8.8.8" and get responses.

If you'd like to communicate with other computers by name instead of by
IP addresses, you can either put their names and IP addresses in the
/etc/hosts file (a simple text file), *or* you can configure your
computer to use DNS.

DNS is configured in the /etc/resolv.conf file.  The most basic piece
consists of "nameserver" lines which contain the IP addresses of DNS
resolvers which will look up computer names for you.  These nameservers
can come from DHCP, or they can be configured in your local files.

Your computer can also have a hostname.  This is how your computer
identifies itself when it logs things, so that you can tell which computer
wrote which piece of the logfile.  Your computer can be named whatever
you like.  Its name has meaning only to you.  Other computers do not
know what your hostname is, and they do not care.

If you want other computers to be able to contact you by a name, then
you add that name to DNS, 

Re: hostname is being reset, killing net on reboot

[gene heskett]

On Friday, January 21, 2022 9:34:35 PM EST gene heskett wrote:
> On Friday, January 21, 2022 7:46:40 PM EST Greg Wooledge wrote:
> > On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> > > On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > > > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > > > > So how do I officially set the hostname so its reboot proof?
> > > > 
> > > > hostnamectl set hostname [foobar]
> > 
> > The standard Debian way is to put the desired hostname in
> > /etc/hostname.
> > 
> > If I'm reading hostnamectl(1) correctly, the command you wanted
> > should
> > have a hyphen in it: hostnamectl set-hostname NEWNAME
> > 
> > However, I've never used this command and I'm not sure what it
> > actually does, or how it interacts with the traditional Debian
> > configuration.> 
> > > Thank you Andy. IIRC that can set domainname too?
> > 
> > That depends on what you mean by "domainname".  There is a
> > "domainname" command in the nis package, which sets the NIS domain
> > name.  But I somehow suspect this isn't what you mean.  I also
> > suspect you aren't talking about Kerberos.  Or Samba.
> > 
> > Do you mean a DNS domain name of some kind?  That's my guess.  But
> > even then, the concept is ambiguous.  What are you actually trying
> > to do?
> > 
> > In order for *other* computers to know your system by a fully
> > qualified domain name, you would need to alter DNS.  Either the real
> > live global DNS that everyone uses, if systems are doing DNS lookups
> > on the public Internet, or else a local area network DNS server that
> > you maintain interally.  Or else modify the /etc/hosts files on the
> > other
> > computers.
> > 
> > Or perhaps what you mean is something like, "When I type telnet iota,
> > I want it to act like I had typed telnet iota.gene.local."  In this
> > case, you're probably aiming for a customized /etc/resolv.conf file.
> > Which in turn means you need to read up on how to avoid having your
> > changes to /etc/resolv.conf wiped out by roaming bands of daemons.
> > I've covered this topic so many times that I'm quite tired of it, so
> > just go to  and read.
> > 
> > Or maybe you mean something else?  Please be specific.
> 
> /etc/resolv.conf has:
> search coyote.den
> nameserver 192.168.xx.1
> 
> the search line says to look in the /etc/hosts file, failing that, the
> nameserver line sends the dns lookup query to the router which NAT's me
> to my isp assigned address, and fwds it to my isp's dns server. And
> its Just Worked much like that way since redhat 5.0 in 1998.
> 
> However when I set hostname with hostname, the 169.bs stays out of the
> picture and networking works the world until a reboot.
> Setting the hostname with hostnamectl to the alias in /etc/hosts for
> this machine, gets me exactly the same hostname but then the route
> reported by "ip a" is the 169.bs.bs.bs and I can't get out of my shirt
> pocket to even ping the router at 192.168.xx.1.
> 
> I tried to remove avahi but apt doesn't admit to knowing it. But thats
> what I had to do to buster in order to get rid of the bogus routing.
> ip route won't kill it, not even to the next reboot, so how do I get
> rid of the bogus 169.bs.bs.bs routing forever?  That whole avahi thing
> has never been anything but a headache for me, whoever wrote it is in
> search of a problem I have never had in 24 years.
> 
> My whole system here, 7 machines atm, has been as high as a dozen, is
> dhcpd-less, all host name based with a common hosts file on all
> machines. And until avahi sticks its camel nose in, it Just Works. So
> how do I get rid of the 169.xx.xx.xx bs? Forever, with shoot to kill
> prejudice?
> 
Never mind. I found the cure in the bottom of /etc/dhcpcd.conf, define a 
static_eth0 and a fallback to it if a dhcpd server can't be found, did 
it, rebooted and its fixed. I have a network. Why isn't that in the wiki?
Neither is there any reference to avahi that can be found in the wiki and 
I spent around 2 hours search and browsing it.. Frustrating is an 
inadequate description. Adequate isn't for mixed audiences.

Anyway, its fixed.  How long? Beats me...

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: hostname is being reset, killing net on reboot

[gene heskett]

On Friday, January 21, 2022 7:46:40 PM EST Greg Wooledge wrote:
> On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> > On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > > > So how do I officially set the hostname so its reboot proof?
> > > 
> > > hostnamectl set hostname [foobar]
> 
> The standard Debian way is to put the desired hostname in
> /etc/hostname.
> 
> If I'm reading hostnamectl(1) correctly, the command you wanted should
> have a hyphen in it: hostnamectl set-hostname NEWNAME
> 
> However, I've never used this command and I'm not sure what it actually
> does, or how it interacts with the traditional Debian configuration.
> > Thank you Andy. IIRC that can set domainname too?
> 
> That depends on what you mean by "domainname".  There is a "domainname"
> command in the nis package, which sets the NIS domain name.  But I
> somehow suspect this isn't what you mean.  I also suspect you aren't
> talking about Kerberos.  Or Samba.
> 
> Do you mean a DNS domain name of some kind?  That's my guess.  But even
> then, the concept is ambiguous.  What are you actually trying to do?
> 
> In order for *other* computers to know your system by a fully qualified
> domain name, you would need to alter DNS.  Either the real live global
> DNS that everyone uses, if systems are doing DNS lookups on the public
> Internet, or else a local area network DNS server that you maintain
> interally.  Or else modify the /etc/hosts files on the other
> computers.
> 
> Or perhaps what you mean is something like, "When I type telnet iota,
> I want it to act like I had typed telnet iota.gene.local."  In this
> case, you're probably aiming for a customized /etc/resolv.conf file. 
> Which in turn means you need to read up on how to avoid having your
> changes to /etc/resolv.conf wiped out by roaming bands of daemons. 
> I've covered this topic so many times that I'm quite tired of it, so
> just go to  and read.
> 
> Or maybe you mean something else?  Please be specific.
> 
/etc/resolv.conf has:
search coyote.den
nameserver 192.168.xx.1

the search line says to look in the /etc/hosts file, failing that, the 
nameserver line sends the dns lookup query to the router which NAT's me 
to my isp assigned address, and fwds it to my isp's dns server. And its 
Just Worked much like that way since redhat 5.0 in 1998.

However when I set hostname with hostname, the 169.bs stays out of the 
picture and networking works the world until a reboot.
Setting the hostname with hostnamectl to the alias in /etc/hosts for this 
machine, gets me exactly the same hostname but then the route reported by 
"ip a" is the 169.bs.bs.bs and I can't get out of my shirt pocket to even 
ping the router at 192.168.xx.1.

I tried to remove avahi but apt doesn't admit to knowing it. But thats 
what I had to do to buster in order to get rid of the bogus routing.
ip route won't kill it, not even to the next reboot, so how do I get rid 
of the bogus 169.bs.bs.bs routing forever?  That whole avahi thing has 
never been anything but a headache for me, whoever wrote it is in search 
of a problem I have never had in 24 years.

My whole system here, 7 machines atm, has been as high as a dozen, is 
dhcpd-less, all host name based with a common hosts file on all machines. 
And until avahi sticks its camel nose in, it Just Works. So how do I get 
rid of the 169.xx.xx.xx bs? Forever, with shoot to kill prejudice?

Thank you.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: hostname is being reset, killing net on reboot

[Greg Wooledge]

On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > > So how do I officially set the hostname so its reboot proof?
> > 
> > hostnamectl set hostname [foobar]

The standard Debian way is to put the desired hostname in /etc/hostname.

If I'm reading hostnamectl(1) correctly, the command you wanted should
have a hyphen in it: hostnamectl set-hostname NEWNAME

However, I've never used this command and I'm not sure what it actually
does, or how it interacts with the traditional Debian configuration.

> Thank you Andy. IIRC that can set domainname too?

That depends on what you mean by "domainname".  There is a "domainname"
command in the nis package, which sets the NIS domain name.  But I
somehow suspect this isn't what you mean.  I also suspect you aren't
talking about Kerberos.  Or Samba.

Do you mean a DNS domain name of some kind?  That's my guess.  But even
then, the concept is ambiguous.  What are you actually trying to do?

In order for *other* computers to know your system by a fully qualified
domain name, you would need to alter DNS.  Either the real live global DNS
that everyone uses, if systems are doing DNS lookups on the public
Internet, or else a local area network DNS server that you maintain
interally.  Or else modify the /etc/hosts files on the other computers.

Or perhaps what you mean is something like, "When I type telnet iota,
I want it to act like I had typed telnet iota.gene.local."  In this case,
you're probably aiming for a customized /etc/resolv.conf file.  Which
in turn means you need to read up on how to avoid having your changes
to /etc/resolv.conf wiped out by roaming bands of daemons.  I've covered
this topic so many times that I'm quite tired of it, so just go to
 and read.

Or maybe you mean something else?  Please be specific.

Re: hostname is being reset, killing net on reboot

[gene heskett]

On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > Hi all;
> > 
> > System is an rpi4b/bullseye, uptodate.
> > I had to fix this a year or more ago with buster, but this system has
> > crashed and burned thanks to a 2T shingled drive. Notes if any were
> > ever made are gone.
> > 
> > So how do I officially set the hostname so its reboot proof?
> 
> hostnamectl set hostname [foobar]
> 
> Hope that helps - all best, as ever,
> 
> Andy Cater
> 
Thank you Andy. IIRC that can set domainname too?

> > Thanks all.
> > 
> > Cheers, Gene Heskett.
> 
> .


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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Where is Debian 11 installer for amd64 that works please ?

[David Christensen]

On 1/21/22 12:10 AM, C.T.F. Jansen wrote:

Greetings

I have been trying to install Debian 11 on an Asus from 2018 with i5 
using amd64 install DVD's  with 11.1.0 and 11.2.0 and a net install CD 
with 11.2.0 . All three have fallen over because of installer bugs.


   There is currently a Debian 9 system on the laptop that went on 
without difficulty.


Am trying to install it to an external hard disk so it can be tested and 
debugged without much damage to the running Debian 9 system.


The Debian 11.2.0 net install CD is the unofficial one with non free 
firmware. Good to have all the drivers in one go.

It comes straight off the Debian website, is unmodified and is on a CD.

Where/how do I get one that works please ?

An alternate plan is to install from a Debian 10 net inst CD, non free, 
amd64. This one went on to another machine without difficulty . Then 
wait and see whether the Debian 12 installer is any better.


Thanks.

C.T.F. Jansen, ZL2TTS



What is the model of the Asus computer?  What model CPU?  How much RAM? 
 What is the make, model, and size of the external disk?  What is the 
connection between the computer and the external disk?  Are you certain 
that the computer port (USB?) is good, the cable is good, the external 
disk is good, and the external disk power adapter is good?  What are the 
source URL's and the file names of the Debian Installer images that you 
downloaded?  Did you verify the checksum of the images?  Did you verify 
the burned DVD's against the downloaded images?  What are the steps 
required to reproduce the installer bugs?



David

Re: hostname is being reset, killing net on reboot

[Andrew M.A. Cater]

On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> Hi all;
> 
> System is an rpi4b/bullseye, uptodate.
> I had to fix this a year or more ago with buster, but this system has 
> crashed and burned thanks to a 2T shingled drive. Notes if any were ever 
> made are gone.
> 
> So how do I officially set the hostname so its reboot proof?
> 

hostnamectl set hostname [foobar]

Hope that helps - all best, as ever,

Andy Cater

> Thanks all.
> 
> 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, 1940)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page 
> 
> 
> 

hostname is being reset, killing net on reboot

[gene heskett]

Hi all;

System is an rpi4b/bullseye, uptodate.
I had to fix this a year or more ago with buster, but this system has 
crashed and burned thanks to a 2T shingled drive. Notes if any were ever 
made are gone.

So how do I officially set the hostname so its reboot proof?

Thanks all.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

GPU PCIe link speed

[Grzesiek]

Hi there,

I noticed that all my GPU operate at PCIe 1.1=2.5GHz instead of PCIe 
2.0/3.0. Is there any way to force higher speed?


Hardware details below

---===### First system ###===---

CPU: i7-3770, Linux version 5.15.0-2-amd64

# dmesg  | grep bandwidth
[0.224924] pci :01:00.0: 16.000 Gb/s available PCIe bandwidth, 
limited by 2.5 GT/s PCIe x8 link at :00:01.0 (capable of 126.016 
Gb/s with 8.0 GT/s PCIe x16 link)


# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family 
High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI 
Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 2 (rev c4)

00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller 
(rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset 
Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus 
Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GK110 [GeForce GTX 
780] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK110 High Definition Audio 
Controller (rev a1)
03:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit 
Ethernet Controller (rev 13)
04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI 
Bridge (rev 03)


---===### Second system ###===---

CPU: i5-2500k, Linux version 5.15.0-2-amd64

# dmesg  | grep bandwidth
[0.285635] pci :03:00.0: 32.000 Gb/s available PCIe bandwidth, 
limited by 2.5 GT/s PCIe x16 link at :02:00.0 (capable of 126.016 
Gb/s with 8.0 GT/s PCIe x16 link)


# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network 
Connection (rev 05)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 5 (rev b5)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 7 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation P67 Express Chipset LPC Controller 
(rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port Desktop SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family 
SMBus Controller (rev 05)

01:00.0 PCI bridge: NVIDIA Corporation NF200 PCIe 2.0 switch (rev a3)
02:00.0 PCI bridge: NVIDIA Corporation NF200 PCIe 2.0 switch (rev a3)
02:02.0 PCI bridge: NVIDIA Corporation NF200 PCIe 2.0 switch (rev a3)
03:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 
970] (rev a1)
03:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio 
Controller (rev a1)
06:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet 
Controller (Copper) (rev 06)
07:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series 
Firewire Controller (rev 01)
08:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host 
Controller (rev 04)
09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
Connection


---===### Third system ###===---

CPU: Ryzen 7 1700, Linux version 5.10.0-10-amd64

# dmesg  | grep bandwidth
[0.647668] pci :22:00.0: 32.000 Gb/s available 

Re: Radicale zegt 404 tegen DAVdroid

[Geert Stappers]

On Fri, Jan 21, 2022 at 08:49:41PM +0100, Martijn van de Streek wrote:
> Geert Stappers schreef op vr 21-01-2022 om 19:59 [+0100]:
> > Wat zou er in directory  `/var/lib/radicale/collections/collection-
> > root`
> > moeten staan zodat "adresboek vernieuwen" wel lukt?
> > 
> > Diezelfde vraag wat specifieker:
> >   Bij werkende combinatie DAVdroid-Radicale-combinatie,
> >   wat is dan de output van `sudo find /var/lib/radicale`?
> 
> Heb je eerst een kalender aangemaakt, door via de browser in te loggen
} Heb je eerst een adresboek aangemaakt, door via de browser in te loggen
> bij Radicale en een beetje in de UI rond te klikken?

Dat had ik gedaan.  En dat ga ik dadelijk opnieuw doen, maar dan anders.
 
> Ik heb in `collections-root` een directory met mijn username als naam
> en daaronder directories voor de verschillende kalenders, met hun UUIDs
> als directorynaam.

Zo iets heb ik ook.
En ik heb het vermoeden dat "soort" belangrijk is.


Wat ik ondertussen gevonden heb:
"PROPFIND" van `vdirsyncer`
: [2022-01-21 21:49:44 +0100] [845400/Thread-23] [DEBUG] Request content:
: 
: 
:   
: 
: 
: 
:   
: 
: [2022-01-21 21:49:44 +0100] [845400/Thread-23] [DEBUG] 'stappers' has write 
access to collection with tag 'stappers/306c36a1-e
29e-35f1-cc07-8ffd8477c903'
: [2022-01-21 21:49:44 +0100] [845400/Thread-23] [DEBUG] Response content:
: 
: 
:   
: /stappers/306c36a1-e29e-35f1-cc07-8ffd8477c903/
: 
:   
: 
:   
:   
: 
: text/vcard
: 
"4a60cce2ea565b694b514401b7ae1381416398ae63a478219c5a18ac364d4786"
:   
:   HTTP/1.1 200 OK
: 
:   
: 
: [2022-01-21 21:49:44 +0100] [845400/Thread-23] [INFO] PROPFIND response 
status for '/stappers/306c36a1-e29e-35f1-cc07-8ffd8477
c903/' with depth '1' in 0.005 seconds: 207 Multi-Status

En de "PROPFIND" van `DAVdroid` ter vergelijk:
: [2022-01-21 21:50:49 +0100] [845400/Thread-25] [DEBUG] Request content:
: 
: 
:   
: 
: 
:   
: 
: [2022-01-21 21:50:49 +0100] [845400/Thread-25] [DEBUG] Response content:
: The requested resource could not be found.
: [2022-01-21 21:50:49 +0100] [845400/Thread-25] [INFO] PROPFIND response 
status for '/user/' with depth '0' in 0.003 seconds: 404 Not Found


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: strange file query

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256




‐‐‐ Original Message ‐‐‐
On Friday, January 21, 2022 10:46 AM, Andrei POPESCU  
wrote:

> On Lu, 17 ian 22, 17:00:48, ghe2001 wrote:
>
> > (I grew up, computer-wise, in the days of the 7" floppy disk -- a
> > megaByte still feels like a lot of disk space.)
>
> You generated more data than that with your first post sent to the 3000+
> d-u subscribers, not counting replies ;)

It wasn't me -- it was the headers, and somebody replied from a Winders OS :-)

--
Glenn English

-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAGBQJh6xnkACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDJG7wgAhMPn2SkzYVGTHo8rkeaBfad3UXzMQY1tb2+bxIOzJSaji3sE
Lj0DsAmM+MC3613JXuF6TZyZ+zUM3gwTpQVse8Viu4tjgh2K8leLPyM6hHjV
dpqnjwOWvLvfRrSkAbZj9dnUjKQkv19RmolI6m7AHlNaG+oiyT1NBr/jb3Hh
JBWyJyrYvl9P6uO4tGG+z4HZTsHsAW7nxnHhjaGDZWXfNPVfXXWKMI2zKfDL
6rX3qrF+Tnz/sd6OLnHBUGmCSDKFvtTmpzfhvZRDL26Jz8DfHhBenhmp8tsi
Rl7rj/wzBceo6peEWNUdNJ/of5fV5VLbDtdjPINurQncOms4qd6COA==
=gquO
-END PGP SIGNATURE-

Re: Radicale zegt 404 tegen DAVdroid

[Martijn van de Streek]

Geert Stappers schreef op vr 21-01-2022 om 19:59 [+0100]:
> Wat zou er in directory  `/var/lib/radicale/collections/collection-
> root`
> moeten staan zodat "adresboek vernieuwen" wel lukt?
> 
> Diezelfde vraag wat specifieker:
>   Bij werkende combinatie DAVdroid-Radicale-combinatie,
>   wat is dan de output van `sudo find /var/lib/radicale`?

Heb je eerst een kalender aangemaakt, door via de browser in te loggen
bij Radicale en een beetje in de UI rond te klikken?

Ik heb in `collections-root` een directory met mijn username als naam
en daaronder directories voor de verschillende kalenders, met hun UUIDs
als directorynaam.

(ik draai Radicale 3.1.1 in een Docker-container, maar dat zou niet
heel anders moeten zijn dan de 3.0.6 in bullseye)

-Martijn

Re: Bridger deux VLAN avec systemd network

[Olivier Lange]

Euh, si t'es en wifi, non. Ton tag est sur tes équipements, et pas sur les
équipements utilisateurs. Sauf si tu fournis un port réseau pour les
visiteurs. Et encore, la tu configure en untag vid visiteur le port de ton
switch.

Olivier

Le ven. 21 janv. 2022 à 14:03, Luc Novales  a écrit :

> Bonsoir,
>
> Je rajouterai qu'il vaut mieux taguer le VLAN normal. Taguer le VLAN
> invité, c'est obliger les invit·és à utiliser une configuration difficile à
> mettre en place, voire impossible sur certains équipements.
>
> Bonne soirée,
>
> Luc.
>
>
> Le 21/01/2022 à 16:26, Olivier Lange a écrit :
>
> Bonjour
>
> Je pense que tu as une ereur d'architecture. si tu veux avoir un réseau
> invité dédié et sécurisé, il te faut un vlan dédié, et un subnet (/24)
> dédié. Ce qui va te permettre de mettre en place des règles spécifiques,
> autant au niveau 3/4/6 (via ton subnet et ton routeur) que 2 (via ton vlan).
>
> Tenter de bridger tout ca, au mieux ca devient une usine a gaz ingérable
> avec plein de vulnérabilité, au pire ton réseau ne fonctionnera pas.
>
> C'est mon avis.
> Olivier
>
> Le ven. 21 janv. 2022 à 10:06, Patrick ZAJDA  a écrit :
>
>> Bonjour,
>>
>>
>> Le contexte est le suivant :
>>
>> J'utilise des TP-Link Deco M5 pour avoir un réseau wifi maillé et
>> souhaite activé le réseau wifi invité.
>>
>> La seule chose qui sépare ces réseau c'est un VLAN tagué pour le réseau
>> invité.
>>
>> Les adresses IP sont dans le même rang pour les deux réseaux, les
>> paramètres DHCP sont en tout point similaires pour les réseau principal et
>> invité. Il n'y a aucun paramètre DHCP séparé pour le réseau invité.
>>
>>
>> Sur un Raspberry Pi, j'ai installé Adguard et souhaite donc l'utiliser
>> comme résolveur au niveau de tout le réseau.
>>
>> Je pourais très bien spécifier l'adresse IP du Deco principal comme
>> résolveur et faire en sorte que celui-ci prenne Adguard comme résolveur
>> mais ça voudrait dire que toutes les requêtes viendraient de la même
>> adresse IP, ce qui ne convient pas.
>>
>>
>> Il faudrait donc que ce résolveur soit joignable depuis le réseau
>> principal comme invité et ce, en utilisant la même adresse IP.
>>
>>
>> J'espère avoir pu expliquer clairement pourquoi il n'y a pas d'autre
>> solution qu'une seule IP qui serait joignable sur les deux VLAN...
>>
>>
>>
>> Le 21/01/2022 à 14:10, JUPIN Alain a écrit :
>>
>> Bonjour,
>>
>> Je comprends pas trop le concept.
>> Pour moi l’intérêt des VLAN c'est d'isoler les réseaux (en utilisant les
>> même équipements réseaux, switch par exemple).
>> En général on relie les VLAN entre eux par du routage, du moins j'ai
>> toujours pratiqué de cette manière !
>>
>> Bridger des VLAN, si c'est pour du test/apprentissage pourquoi pas, mais
>> pour de la prod je me méfierait des effets de bords au niveau de la
>> sécurité.
>>
>> Alain JUPIN
>>
>> Le 20/01/2022 à 14:51, Patrick ZAJDA a écrit :
>>
>> Bonjour,
>>
>>
>> Est-il possible de bridger deux VLAN ?
>>
>>
>> Le but étant d'avoir une adresse IP commune aux deux VLAN pour que les
>> deux puissent utiliser le même résolveur entre les réseaux principal et
>> invité.
>>
>> Si une autre méthode que le bridge est possible, je reste bien entendu
>> ouvert aux alternatives :)
>>
>>
>> Pour le moment, j'ai testé ceci (en anglais) sans succès :
>> https://www.variantweb.net/blog/creating-vlan-bridges-with-systemd-networkd/
>>
>>
>> Il utilise deux bridges mais le raspberry Pi sur lequel je le fait ne
>> passe jamais en ligne.
>>
>> J'ai tenté de n'utiliser qu'un seul bridge, avec le même résultat.
>>
>>
>> --
>> Patrick ZAJDA
>>
>>
>> --
>> Patrick ZAJDA
>>
>

Re: chromium , google-chrome : ingérables avec Bullseye

[ajh-valmer]

On Friday 21 January 2022 19:15:55 didier gaumet wrote:
> > Tout ceci depuis que j'ai upgradé à Bullseye, avec un système
> > entièrement réinstallé à neuf.

J'ai bien lu ton commentaire et Merci : je suis sceptique...
J'ai upgradé à Bullseye, avec un système entièrement réinstallé à neuf,
sur une partition effacée et formatée, sur un ordinateur de test donc
vide d'applications, en attendant de le mettre en production,
J'ai bien fait exactement ce que tu écris plus bas :
>"installe une Debian 11 *standard* (avec *un* bureau *fourni par Debian* 
> dans ses paquets: Gnome, KDE, LXDE, LXQt, Xfce, Mate, Cinnamon) 
> sans *rien* paramétrer, sans rien installer d'autre, tu installes juste les
> firmwares nécessaires et après que l'installation est terminée, tu
> installes le paquet Chromium de Debian".

J'ai fait exactement ce que tu préconises.
Je n'ai jamais eu ce type de problèmes avec les ex-distributions Debian,
depuis 20 ans. Ce n'est que depuis Bullseye.
En plus de 20 années, je pense avoir maîtrisé Debian :-)

Un membre de la liste m'a répondu sur ce sujet :
> "A cause de problèmes dont je ne connais pas le détail, 
> mais qui est je crois le cycle de mise-à-jour de Chrome qui est ## 
> avec pas mal de problèmes associés, Ubuntu met chromium/chrome en snap. 
> C'est peut-être un moyen de résoudre ton problème, même si ça oblige à
> installer snap".

Je m'orienterai plus vers cet avis...

Bonne soirée,

A. Valmer

> le code de Chrome est grosso-modo celui de Chromium, auquel Google
> rajoute quelques trucs:
> https://fr.wikipedia.org/wiki/Chromium#Diff%C3%A9rences_entre_Chromium_et_Google_Chrome
> donc c'est normal que Chrome réagisse majoritairement comme Chromium
> Ce n'est vraiment pas pour te contrarier, mais je pense que ton
> installation est bancale et cela occasionne des dysfonctionnements qui
> sont absents d'une installation bien faite.
> j'ai cassé mes Debian toutes fraîches bien avant toi (et ça peut encore
> m'arriver à l'occasion), et avant de finir par comprendre que mes
> configurations et installations de logiciels juste après l'installation
> de base de Debian, cassaient Debian, parce que j'avais lu quelque part
> qu'il fallait absolument paramétrer tel machin de telle manière (source
> obsolète ou non-fiable) ou que j'installais des logiciels sans
> comprendre que parfois il n'y avait pas de conflit d'installation mais
> qu'il y avait un conflit d'utilisation, etc... :-)
> La page en français "ne cassez pas Debian" du wiki Debian mérite d'être
> lue:
> https://wiki.debian.org/fr/DontBreakDebian
> Si tu veux vérifier que Chromium marche bien dans Debian, installe une
> Debian 11 *standard* (avec *un* bureau *fourni par Debian* dans ses
> paquets: Gnome, KDE, LXDE, LXQt, Xfce, Mate, Cinnamon) sans *rien*
> paramétrer, sans rien installer d'autre, tu installes juste les
> firmwares nécessaires et après que l'installation est terminée, tu
> installes le paquet Chromium de Debian.
> Je pense que tu as 99% de chances pour que, aussi bien Chromium que
> Debian séparément, comme la conjuguaison des deux, fonctionnent
> parfaitement
> Une fois que tu auras compris que Debian est globalement fiable et
> fonctionnel et que tu auras admis que tu as des précautions à prendre
> si tu ne veux pas le casser, rien ne t'empêchera de te concocter *ta*
> Debian avec les caractéristiques esthétiques, fonctionnelles et
> autres... que tu souhaites.
> mon but n'est pas de te dire "tu n'as pas le droit de personnaliser ta
> Debian" mais plutôt "apprends à gérer une Debian standard, une fois
> cela maîtrisé, tu pourras la personnaliser à ta guise sans la casser
> puisque tu maîtriseras)
> Amicalement :-)

Re: Future of "his" packages in Debian

[P J]

On Fri, Jan 21, 2022 at 8:05 AM Curt  wrote:

> On 2022-01-21, Andrew M.A. Cater  wrote:
> >>
> >>
> >> Can someone post what Norbert Preining actually wrote without omissions
> and rather frivolous additions by other parties?
> >>
> >> Regards,
> >>
> >
> >>From Norbert's blog, aggregated on Planet Debian:
> >
> > https://www.preining.info/blog/2022/01/future-of-my-packages-in-debian/
> >
> > With every good wish, as ever,
> >
> > Andrew Cater
> >
> >
>
> If only he had the Internet to look these things up.


Information is available and so so many wants to be spoon fed.  People have
to learn to help themselves.

>
>

Re: Bridger deux VLAN avec systemd network

[Luc Novales]

Bonsoir,

Je rajouterai qu'il vaut mieux taguer le VLAN normal. Taguer le VLAN 
invité, c'est obliger les invit·és à utiliser une configuration 
difficile à mettre en place, voire impossible sur certains équipements.


Bonne soirée,

Luc.


Le 21/01/2022 à 16:26, Olivier Lange a écrit :

Bonjour

Je pense que tu as une ereur d'architecture. si tu veux avoir un 
réseau invité dédié et sécurisé, il te faut un vlan dédié, et un 
subnet (/24) dédié. Ce qui va te permettre de mettre en place des 
règles spécifiques, autant au niveau 3/4/6 (via ton subnet et ton 
routeur) que 2 (via ton vlan).


Tenter de bridger tout ca, au mieux ca devient une usine a gaz 
ingérable avec plein de vulnérabilité, au pire ton réseau ne 
fonctionnera pas.


C'est mon avis.
Olivier

Le ven. 21 janv. 2022 à 10:06, Patrick ZAJDA  a écrit :

Bonjour,


Le contexte est le suivant :

J'utilise des TP-Link Deco M5 pour avoir un réseau wifi maillé et
souhaite activé le réseau wifi invité.

La seule chose qui sépare ces réseau c'est un VLAN tagué pour le
réseau invité.

Les adresses IP sont dans le même rang pour les deux réseaux, les
paramètres DHCP sont en tout point similaires pour les réseau
principal et invité. Il n'y a aucun paramètre DHCP séparé pour le
réseau invité.


Sur un Raspberry Pi, j'ai installé Adguard et souhaite donc
l'utiliser comme résolveur au niveau de tout le réseau.

Je pourais très bien spécifier l'adresse IP du Deco principal
comme résolveur et faire en sorte que celui-ci prenne Adguard
comme résolveur mais ça voudrait dire que toutes les requêtes
viendraient de la même adresse IP, ce qui ne convient pas.


Il faudrait donc que ce résolveur soit joignable depuis le réseau
principal comme invité et ce, en utilisant la même adresse IP.


J'espère avoir pu expliquer clairement pourquoi il n'y a pas
d'autre solution qu'une seule IP qui serait joignable sur les deux
VLAN...



Le 21/01/2022 à 14:10, JUPIN Alain a écrit :

Bonjour,

Je comprends pas trop le concept.
Pour moi l’intérêt des VLAN c'est d'isoler les réseaux (en
utilisant les même équipements réseaux, switch par exemple).
En général on relie les VLAN entre eux par du routage, du moins
j'ai toujours pratiqué de cette manière !

Bridger des VLAN, si c'est pour du test/apprentissage pourquoi
pas, mais pour de la prod je me méfierait des effets de bords au
niveau de la sécurité.

Alain JUPIN

Le 20/01/2022 à 14:51, Patrick ZAJDA a écrit :


Bonjour,


Est-il possible de bridger deux VLAN ?


Le but étant d'avoir une adresse IP commune aux deux VLAN pour
que les deux puissent utiliser le même résolveur entre les
réseaux principal et invité.

Si une autre méthode que le bridge est possible, je reste bien
entendu ouvert aux alternatives :)


Pour le moment, j'ai testé ceci (en anglais) sans succès :
https://www.variantweb.net/blog/creating-vlan-bridges-with-systemd-networkd/


Il utilise deux bridges mais le raspberry Pi sur lequel je le
fait ne passe jamais en ligne.

J'ai tenté de n'utiliser qu'un seul bridge, avec le même résultat.


-- 
Patrick ZAJDA


-- 
Patrick ZAJDA

Radicale zegt 404 tegen DAVdroid

[Geert Stappers]

Hoi,

Op een android device staat DAVdroid.
Bij activeren vann "adresboek vernieuwen" is er even soort van
progress bar, daarna niets. Ook geen foutmelding.

Aan server kant is het debian package `radicale`. In de logging
vind o.a.

 [2022-01-21 19:46:32 +0100] [845400/Thread-4] [INFO] Successful login: 
'stappers'
 [2022-01-21 19:46:32 +0100] [845400/Thread-4] [DEBUG] Request content:
 
 
   
 
 
   
 
 [2022-01-21 19:46:32 +0100] [845400/Thread-4] [DEBUG] Response content:
 The requested resource could not be found.
 [2022-01-21 19:46:32 +0100] [845400/Thread-4] [INFO] PROPFIND response status 
for '/user/' with depth '0' in 0.005 seconds: 404 Not Found 

Wat zou er in directory  `/var/lib/radicale/collections/collection-root`
moeten staan zodat "adresboek vernieuwen" wel lukt?

Diezelfde vraag wat specifieker:
  Bij werkende combinatie DAVdroid-Radicale-combinatie,
  wat is dan de output van `sudo find /var/lib/radicale`?


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Chromium security updates

[Andrei POPESCU]

On Jo, 20 ian 22, 00:08:52, Richmond wrote:
> I see debian 10's chromium is currently on version 90.0.4430.212
> (Developer Build), whereas google-chrome is on Version 97.0.4692.99
> (Official Build) (64-bit). Does that mean it is out of date and has
> security vulnerabilities?
> 
> https://chromereleases.googleblog.com/search/label/Stable%20updates

The plan was:

https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#browser-security

Unfortunately both Firefox and Chromium proved to be much more of a 
challenge then expected at the time of releasing Debian 10 "buster" (now 
oldstable).

Firefox appears to be in slightly better shape (updated version 
available in bullseye/stable, still pending for buster/oldstable).

Updated Chromium for bullseye/stable appears to be imminent, hopefully 
buster/oldstable will follow.
 
> Debian 10 is supported until 2024.
>
> https://wiki.debian.org/LTS

As per https://wiki.debian.org/LTS/Using not all packages are supported 
by LTS.


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: User group "users"

[Thomas Hochstein]

Roberto C. Sánchez schrieb:

>>> New users have gid 100 set as their primary group by default.  So, new
>>> users are members of the group without having to be added to the group
>>> in /etc/groups.

That depends on your configuration.

| # /etc/adduser.conf: `adduser' configuration.
| # See adduser(8) and adduser.conf(5) for full documentation.
[...]
| # The USERGROUPS variable can be either "yes" or "no".  If "yes" each
| # created user will be given their own group to use as a default.  If
| # "no", each created user will be placed in the group whose gid is
| # USERS_GID (see below).
| USERGROUPS=yes
| 
| # If USERGROUPS is "no", then USERS_GID should be the GID of the group
| # `users' (or the equivalent group) on your system.
| USERS_GID=100

> Quite right.  It seems that I probably made that change a very long time
> ago, long enough ago so that it just seemed like the standard
> configuration to me.

>From :
|  Debian has been using (creating) user private groups by default almost
|  from the beginning. However, UPGs where not fully enabled on newly
|  installed systems since release 2.2., because the central umask
|  adjustment for UPGs, as configured in /etc/login.defs, was broken with
|  the inclusion of PAM. This feature was only reintroduced with
|  libpam-umask in release 6.0 (Squeeze). 

-thh

Re: chromium , google-chrome : ingérables avec Bullseye

[didier gaumet]

Le vendredi 21 janvier 2022 à 17:57 +0100, ajh-valmer a écrit :
> On Friday 21 January 2022 14:11:21 Luc Novales wrote:
> > C'est la façon dont tu as tourné ta phrase qui peut sous-entendre
> > que 
> > Chromium est moins bon parcequ'il est libre ;)
> > Tu aurais écrit "moins utilisé" à la place de libre, il n'y aurait
> > pas 
> > eu de doute.
> 
> Je félicite les développeurs libristes de Chromium,
> mais sur ma Bullseye, il fonctionne pas du tout, jamais eu ça avant.
> En plus, en bas à droite du navigateur, il m'affiche des pubs
> changeantes,
> impossible de les retirer malgré un clic sur le petite croix, ça
> revient sans cesse.
> 
> Et pourquoi le navigateur Chrome (google) le + utilisé, c'est pareil,
> sauf que les pubs n'apparaissent pas. 
> Serait-ce alors que la version Chrome pour Linux qui créé ces blêmes
> ?
> 
> Tout ceci depuis que j'ai upgradé à Bullseye, avec un système
> entièrement
> réinstallé à neuf.
> 
> > Sinon, par rapport au problème initial, je pense qu'il ne vient pas
> > de 
> > Chromium, mais du contexte particulier sur cette machine, puisque 
> > personne d'autre ne l'a confirmé.
> > Je ne suis pas intervenu car mon navigateur quotidien est Brave
> > (pas 
> > exactement Chromium), c'est la Version 1.34.80 Chromium:
> > 97.0.4692.71 
> > (Build officiel) (64 bits).
> > Aucun problème de fonctionnement sous Gnome (pure Debian), ni sous
> > XFCE 
> > (Debian facile).
> > Par contre, je suis sous X11 (compatibilité de certains logiciels),
> > les 
> > problèmes sont ils sous Wayland ? Les problèmes sont ils identiques
> > en 
> > changeant ce paramètre au login ?
> > Bonne journée,  Luc.
> 
> Mon système graphique a parfois été bancale, malgré, Chromium et
> Chrome,
> ont toujours été fonctionnels.
> 
> Bonne journée également
> 
> A. Valmer
> 
> 

le code de Chrome est grosso-modo celui de Chromium, auquel Google
rajoute quelques trucs:
https://fr.wikipedia.org/wiki/Chromium#Diff%C3%A9rences_entre_Chromium_et_Google_Chrome
donc c'est normal que Chrome réagisse majoritairement comme Chromium

Ce n'est vraiment pas pour te contrarier, mais je pense que ton
installation est bancale et cela occasionne des dysfonctionnements qui
sont absents d'une installation bien faite.

j'ai cassé mes Debian toutes fraîches bien avant toi (et ça peut encore
m'arriver à l'occasion), et avant de finir par comprendre que mes
configurations et installations de logiciels juste après l'installation
de base de Debian, cassaient Debian, parce que j'avais lu quelque part
qu'il fallait absolument paramétrer tel machin de telle manière (source
obsolète ou non-fiable) ou que j'installais des logiciels sans
comprendre que parfois il n'y avait pas de conflit d'installation mais
qu'il y avait un conflit d'utilisation, etc... :-)

La page en français "ne cassez pas Debian" du wiki Debian mérite d'être
lue:
https://wiki.debian.org/fr/DontBreakDebian

Si tu veux vérifier que Chromium marche bien dans Debian, installe une
Debian 11 *standard* (avec *un* bureau *fourni par Debian* dans ses
paquets: Gnome, KDE, LXDE, LXQt, Xfce, Mate, Cinnamon) sans *rien*
paramétrer, sans rien installer d'autre, tu installes juste les
firmwares nécessaires et après que l'installation est terminée, tu
installes le paquet Chromium de Debian.
Je pense que tu as 99% de chances pour que, aussi bien Chromium que
Debian séparément, comme la conjuguaison des deux, fonctionnent
parfaitement

Une fois que tu auras compris que Debian est globalement fiable et
fonctionnel et que tu auras admis que tu as des précautions à prendre
si tu ne veux pas le casser, rien ne t'empêchera de te concocter *ta*
Debian avec les caractéristiques esthétiques, fonctionnelles et
autres... que tu souhaites.

mon but n'est pas de te dire "tu n'as pas le droit de personnaliser ta
Debian" mais plutôt "apprends à gérer une Debian standard, une fois
cela maîtrisé, tu pourras la personnaliser à ta guise sans la casser
puisque tu maîtriseras)

Amicalement :-)

Re: strange file query

[Andrei POPESCU]

On Lu, 17 ian 22, 17:00:48, ghe2001 wrote:
> 
> (I grew up, computer-wise, in the days of the 7" floppy disk -- a 
> megaByte still feels like a lot of disk space.)

You generated more data than that with your first post sent to the 3000+ 
d-u subscribers, not counting replies ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Please take this as constructive

[Nicholas Geovanis]

On Wed, Jan 19, 2022 at 4:06 AM Anssi Saari  wrote:

> Stefan Monnier  writes:
> > Here's another way to attack those chicken/egg problems:
>
> Interesting approach. When I recently installed Debian on a newish
> computer I needed some firmware packages and a newer kernel too from
> debian-backports. I was able to use my phone connected to USB enough to
> complete installation and then install what I needed from
> debian-backports and then get online with built in ethernet.
>
> After that I have bought some cheap Linux-compatible USB ethernet and
> USB wifi adapters, just in case.
>
>
My approach to these problems is to sidestep them entirely:
(1) Create an installable USB key on an existing connected machine
(2) Install it on a new machine

Step 1 is much faster if that connected machine is NOT on wifi, but cabled
to your router instead.
You can even do Step 1 on a Win machine, Debian doc tells you how.
And you can even increase your wifi throughput on the newly-installed
machine by just disabling the
wifi port and plugging that network cable directly into the router all the
time. Wifi issues gone :-)

the

Re: User group "users"

[Andrei POPESCU]

On Vi, 21 ian 22, 14:49:09, Steve Keller wrote:
> I see that on my Debian systems there is a user group "users" with GID 100,
> but by default no user gets added to it.  So what is the purpose or reason
> to have it?
> 
> >From old Unix installations I know the group "users" which every user was
> a member of, by default.
 
According to /usr/share/doc/base-passwd/users-and-groups.txt.gz

   users
  While Debian systems use the user-group system by
  default (each user has their own group), some prefer to
  use a more traditional group system. In that system,
  each user is a member of the 'users' group.


It's probably there to "reserve" GID 100 and preserve compatibility with 
other systems using this system.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Please take this as constructive

[Andrei POPESCU]

On Ma, 18 ian 22, 22:06:33, The Wanderer wrote:
> 
> Unless you mean "e.g., using a wired connection"? It's not clear that
> that's an available option in this case, either, although there are
> probably a lot of cases where it will be. (I've had the misfortune
> recently, in my workplace, of having to image and set up a lot of
> laptops which don't come with a wired Ethernet adapter, and most
> recently with ones that don't come with an external USB-or-similar
> wired-Ethernet adapter dongle either.)

Dongles might require firmware as well :(

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: chromium , google-chrome : ingérables avec Bullseye

[ajh-valmer]

On Friday 21 January 2022 14:11:21 Luc Novales wrote:
> C'est la façon dont tu as tourné ta phrase qui peut sous-entendre que 
> Chromium est moins bon parcequ'il est libre ;)
> Tu aurais écrit "moins utilisé" à la place de libre, il n'y aurait pas 
> eu de doute.

Je félicite les développeurs libristes de Chromium,
mais sur ma Bullseye, il fonctionne pas du tout, jamais eu ça avant.
En plus, en bas à droite du navigateur, il m'affiche des pubs changeantes,
impossible de les retirer malgré un clic sur le petite croix, ça revient sans 
cesse.

Et pourquoi le navigateur Chrome (google) le + utilisé, c'est pareil,
sauf que les pubs n'apparaissent pas. 
Serait-ce alors que la version Chrome pour Linux qui créé ces blêmes ?

Tout ceci depuis que j'ai upgradé à Bullseye, avec un système entièrement
réinstallé à neuf.

> Sinon, par rapport au problème initial, je pense qu'il ne vient pas de 
> Chromium, mais du contexte particulier sur cette machine, puisque 
> personne d'autre ne l'a confirmé.
> Je ne suis pas intervenu car mon navigateur quotidien est Brave (pas 
> exactement Chromium), c'est la Version 1.34.80 Chromium: 97.0.4692.71 
> (Build officiel) (64 bits).
> Aucun problème de fonctionnement sous Gnome (pure Debian), ni sous XFCE 
> (Debian facile).
> Par contre, je suis sous X11 (compatibilité de certains logiciels), les 
> problèmes sont ils sous Wayland ? Les problèmes sont ils identiques en 
> changeant ce paramètre au login ?
> Bonne journée,  Luc.

Mon système graphique a parfois été bancale, malgré, Chromium et Chrome,
ont toujours été fonctionnels.

Bonne journée également

A. Valmer

Re: Special installation issue

[deloptes]

Hans wrote:

> Any ideas? Thanks in advance.

I usually use debootstrap and install to the USB stick (that is to boot
from). So I have a fully bootable system. I use qemu to prepare and test
the basics.
As mentioned those arm beasts are usually with various hardware combinations
and might be needed that you find what hardware specs you have and find the
proper kernel version or even compile your own. Problem are usually the
firmwares and binary blobs

But anyway if you use working bootable USB stick, you will not have to limit
yourself by the installer

-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Re: Ayuda por favor

[Camaleón]

El 2022-01-21 a las 11:23 -0500, NAIRO TORRES escribió:

(reenvío a la lista)

> El 1/21/2022 a las 2:05 a. m., Camaleón escribió:
> > El 2022-01-20 a las 14:40 -0500, NAIRO TORRES escribió:
> > 
> > > Buenas tardes, mi problema es ke estoy empezando a estudair debian y le
> > > habia instalado Debian 10 (buster) en un sony vaio vgn-cr360f, todo iba
> > > bien, hasta ke me dio pore actualizar a Debian 11 y ya no quiso arrancar,
> > > solo sale una raya titilante en la parte superior izquierda de la 
> > > pantalla y
> > > de alli no pasa. Le he vuelto ha instalar la misma version de debian 10
> > > anterior y sigue igual.
> > Si el sistema no arranca normalmente, intenta iniciar en modo de
> > recuperación desde el menú de GRUB, para poder al menos acceder al
> > sistema y ver los registros y trabajar desde ahí.
> > 
> > Según las especificaciones del portátil, lleva una gráfica Intel Mobile
> > Intel® GMA X3100, por lo que en principio no deberías tener problemas
> > con el servidor gráfico ni con el kernel, ya que cargará el modo KMS.
> > 
> > Revisa estas indicaciones por si te estuviera afectando alguno de los
> > pronblemas conocidos para este chipset:
> > 
> > https://wiki.debian.org/KernelModesetting#Intel_GfxCards
> > 
> > Saludos,
> > 
> Gracias por tu respuesta...el problema era ke no le habia instalado el grub,
> ya ke no iba a tener otro sistema operativo junto con debian..pero
> cuando ya le instale el grub, arranco sin problemas con el Debian 11.
> 
> Gracias
> 
> atte
> 
> 
> nairo

Saludos,

-- 
Camaleón 

Re: DHCP and search list for DNS domains

[David Wright]

On Fri 21 Jan 2022 at 13:57:47 (+0100), Steve Keller wrote:

> AFAIK, some of my client hosts have only resolvconf, others use some
> systemd stuff, since the man page for resolvconf is actually the
> man page for resolvectl which also refers to systemd-resolved.

The man page for /package/ resolvconf is   man 8 resolvconf,
not man resolvconf.

$ dpkg -L resolvconf

or whatever the package is, can be useful here.

Cheers,
David.

Re: User group "users"

[David Wright]

On Fri 21 Jan 2022 at 16:11:13 (+0100), Steve Keller wrote:
> "Roberto C. Sánchez"  wrote:
> 
> > New users have gid 100 set as their primary group by default.  So, new
> > users are members of the group without having to be added to the group
> > in /etc/groups.
> 
> Hmm, at least not on two Debian systems (stretch and bullseye), I have
> running here:
> 
> # cat /etc/debian_version 
> 9.13
> # useradd -c Foo foo
> # id foo
> uid=1021(foo) gid=1021(foo) groups=1021(foo)
> 
> 
> # cat /etc/debian_version 
> 11.2
> # useradd -c Foo foo
> # id foo
> uid=1020(foo) gid=1020(foo) groups=1020(foo)

You're encouraged to use adduser rather than useradd. But in
both cases, what they do is configured with, respectively,
/etc/adduser.conf and /etc/default/useradd, q.v.

Cheers,
David.

Re: Special installation issue

[Hans]

Am Freitag, 21. Januar 2022, 16:31:56 CET schrieb Christian Britz:
Hi Christian,

no, no, although I might have asked to this thematics before. Sometimes I let 
things die, and when I have another idea, I pick things up again.

However, the link you gave to me I was not aware. Thanks for it, I will give 
it a close look.

Best regards

Hans 

> Hello Hans,
> 
> didn't you ask this question already three years ago? ;-)
> 
> According to https://openrt.gitbook.io/open-surfacert/ it should be
> possible to run ARM based Linux distributions on Surface RT, but there
> might be inconsistencies, for example regarding power management.
> 
> Regards,
> Christian
> 
> On 2022-01-21 11:01 UTC+0100, Hans wrote:
> > Hello all,
> > 
> > I am stuck with a special installation problem, maybe you can help me.
> > 
> > I want to install debian/armhf onto a tablet "Microsoft Surface RT". This
> > one is UEFI-dongled, can officially not boot from an USB-stick, and can
> > officially not be installed with any other OS than MS Windows ERT.
> > 
> > However I managed to get it booted from USB-Stick with some special
> > tricks, it looks like the kernel is booting, but then I am stuck in the
> > shell of grub.
> > 
> > On my USB-Stick is the debian-installer-iso for arm architecture.
> > 
> > Now my question: When I am in the grub shell, is it possible, to manually
> > mount the iso and get access to the installer routine within the
> > iso-image?
> > 
> > I believe (but I am not experienced enough at the moment), that the
> > hardest
> > thing is already done, whe I am so far, as I am. Maybe, next step will be
> > easier, as soon I can start the installer routine. But here stops my
> > knowledge.
> > 
> > Any ideas? Thanks in advance.
> > 
> > And if my plan is not possible, then please let me know, that I will stopp
> > my efforts.
> > 
> > Best
> > 
> > Hnas

Re: Future of "his" packages in Debian

[Curt]

On 2022-01-21, Andrew M.A. Cater  wrote:
>> 
>> 
>> Can someone post what Norbert Preining actually wrote without omissions and 
>> rather frivolous additions by other parties?
>> 
>> Regards,
>>
>
>>From Norbert's blog, aggregated on Planet Debian:
>
> https://www.preining.info/blog/2022/01/future-of-my-packages-in-debian/
>
> With every good wish, as ever,
>
> Andrew Cater 
>
>

If only he had the Internet to look these things up.

Re: Bridger deux VLAN avec systemd network

[Olivier Lange]

Bonjour

Je pense que tu as une ereur d'architecture. si tu veux avoir un réseau
invité dédié et sécurisé, il te faut un vlan dédié, et un subnet (/24)
dédié. Ce qui va te permettre de mettre en place des règles spécifiques,
autant au niveau 3/4/6 (via ton subnet et ton routeur) que 2 (via ton vlan).

Tenter de bridger tout ca, au mieux ca devient une usine a gaz ingérable
avec plein de vulnérabilité, au pire ton réseau ne fonctionnera pas.

C'est mon avis.
Olivier

Le ven. 21 janv. 2022 à 10:06, Patrick ZAJDA  a écrit :

> Bonjour,
>
>
> Le contexte est le suivant :
>
> J'utilise des TP-Link Deco M5 pour avoir un réseau wifi maillé et souhaite
> activé le réseau wifi invité.
>
> La seule chose qui sépare ces réseau c'est un VLAN tagué pour le réseau
> invité.
>
> Les adresses IP sont dans le même rang pour les deux réseaux, les
> paramètres DHCP sont en tout point similaires pour les réseau principal et
> invité. Il n'y a aucun paramètre DHCP séparé pour le réseau invité.
>
>
> Sur un Raspberry Pi, j'ai installé Adguard et souhaite donc l'utiliser
> comme résolveur au niveau de tout le réseau.
>
> Je pourais très bien spécifier l'adresse IP du Deco principal comme
> résolveur et faire en sorte que celui-ci prenne Adguard comme résolveur
> mais ça voudrait dire que toutes les requêtes viendraient de la même
> adresse IP, ce qui ne convient pas.
>
>
> Il faudrait donc que ce résolveur soit joignable depuis le réseau
> principal comme invité et ce, en utilisant la même adresse IP.
>
>
> J'espère avoir pu expliquer clairement pourquoi il n'y a pas d'autre
> solution qu'une seule IP qui serait joignable sur les deux VLAN...
>
>
>
> Le 21/01/2022 à 14:10, JUPIN Alain a écrit :
>
> Bonjour,
>
> Je comprends pas trop le concept.
> Pour moi l’intérêt des VLAN c'est d'isoler les réseaux (en utilisant les
> même équipements réseaux, switch par exemple).
> En général on relie les VLAN entre eux par du routage, du moins j'ai
> toujours pratiqué de cette manière !
>
> Bridger des VLAN, si c'est pour du test/apprentissage pourquoi pas, mais
> pour de la prod je me méfierait des effets de bords au niveau de la
> sécurité.
>
> Alain JUPIN
>
> Le 20/01/2022 à 14:51, Patrick ZAJDA a écrit :
>
> Bonjour,
>
>
> Est-il possible de bridger deux VLAN ?
>
>
> Le but étant d'avoir une adresse IP commune aux deux VLAN pour que les
> deux puissent utiliser le même résolveur entre les réseaux principal et
> invité.
>
> Si une autre méthode que le bridge est possible, je reste bien entendu
> ouvert aux alternatives :)
>
>
> Pour le moment, j'ai testé ceci (en anglais) sans succès :
> https://www.variantweb.net/blog/creating-vlan-bridges-with-systemd-networkd/
>
>
> Il utilise deux bridges mais le raspberry Pi sur lequel je le fait ne
> passe jamais en ligne.
>
> J'ai tenté de n'utiliser qu'un seul bridge, avec le même résultat.
>
>
> --
> Patrick ZAJDA
>
>
> --
> Patrick ZAJDA
>

Re: Special installation issue

[Christian Britz]

Hello Hans,

didn't you ask this question already three years ago? ;-)

According to https://openrt.gitbook.io/open-surfacert/ it should be
possible to run ARM based Linux distributions on Surface RT, but there
might be inconsistencies, for example regarding power management.

Regards,
Christian

On 2022-01-21 11:01 UTC+0100, Hans wrote:
> Hello all,
> 
> I am stuck with a special installation problem, maybe you can help me.
> 
> I want to install debian/armhf onto a tablet "Microsoft Surface RT". This one 
> is UEFI-dongled, can officially not boot from an USB-stick, and can 
> officially 
> not be installed with any other OS than MS Windows ERT.
> 
> However I managed to get it booted from USB-Stick with some special tricks, 
> it 
> looks like the kernel is booting, but then I am stuck in the shell of grub.
> 
> On my USB-Stick is the debian-installer-iso for arm architecture.
> 
> Now my question: When I am in the grub shell, is it possible, to manually 
> mount the iso and get access to the installer routine within the iso-image?
> 
> I believe (but I am not experienced enough at the moment), that the hardest 
> thing is already done, whe I am so far, as I am. Maybe, next step will be 
> easier, as soon I can start the installer routine. But here stops my 
> knowledge. 
> 
> Any ideas? Thanks in advance.
> 
> And if my plan is not possible, then please let me know, that I will stopp my 
> efforts.
> 
> Best 
> 
> Hnas 
>  
> 
> 
> 
> 
> 
> 

Re: Authentication required message window after nvidia drivers installation.

[Christian Britz]

Hi,

this is certainly very strange behaviour which I never experienced at
the time when I was using the NVDIA closed-source drivers.
It actually sounds a little bit alarming to me.

Regards,
Christian

On 2022-01-21 14:24 UTC+0100, Thanos Katsiolis wrote:
> Hello,
> 
> the title of the post says pretty much everything.
> I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA
> drivers as described in Debian wiki NVIDIA Proprietary Driver
>  for Debian 11.2.
> 
> The message appears when an Application starts or when a window from an
> application opens. Some applications were left with a blank screen
> when launching, but after a restart, when I press escape on the message,
> the application starts normally.
> Any ideas on how to fix it?

Re: User group "users"

[Roberto C . Sánchez]

On Fri, Jan 21, 2022 at 04:08:00PM +0100, Jerome BENOIT wrote:
> 
> 
> On 21/01/2022 15:59, Roberto C. Sánchez wrote:
> > On Fri, Jan 21, 2022 at 02:49:09PM +0100, Steve Keller wrote:
> > > I see that on my Debian systems there is a user group "users" with GID 
> > > 100,
> > > but by default no user gets added to it.  So what is the purpose or reason
> > > to have it?
> > > 
> > > >From old Unix installations I know the group "users" which every user was
> > > a member of, by default.
> > > 
> > New users have gid 100 set as their primary group by default.  So, new
> > users are members of the group without having to be added to the group
> > in /etc/groups.
> 
> This might be specific to your installation.
> Usually users have by default their own group.
> 
Quite right.  It seems that I probably made that change a very long time
ago, long enough ago so that it just seemed like the standard
configuration to me.  Apologies for the misinformation.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: User group "users"

[Steve Keller]

"Roberto C. Sánchez"  wrote:

> New users have gid 100 set as their primary group by default.  So, new
> users are members of the group without having to be added to the group
> in /etc/groups.

Hmm, at least not on two Debian systems (stretch and bullseye), I have
running here:

# cat /etc/debian_version 
9.13
# useradd -c Foo foo
# id foo
uid=1021(foo) gid=1021(foo) groups=1021(foo)


# cat /etc/debian_version 
11.2
# useradd -c Foo foo
# id foo
uid=1020(foo) gid=1020(foo) groups=1020(foo)


Steve

Re: User group "users"

[Jerome BENOIT]

On 21/01/2022 15:59, Roberto C. Sánchez wrote:

On Fri, Jan 21, 2022 at 02:49:09PM +0100, Steve Keller wrote:

I see that on my Debian systems there is a user group "users" with GID 100,
but by default no user gets added to it.  So what is the purpose or reason
to have it?

>From old Unix installations I know the group "users" which every user was
a member of, by default.


New users have gid 100 set as their primary group by default.  So, new
users are members of the group without having to be added to the group
in /etc/groups.


This might be specific to your installation.
Usually users have by default their own group.

Cheers,
Jerome




Regards,

-Roberto

Re: DHCP and search list for DNS domains

[Steve Keller]

"Markus Schönhaber"  wrote:

> > AFAICS, there is no option in DHCP to provide the search list.
> 
>  From dhcp-options(5):
> 
> >option domain-search domain-list;
> > 
> >  The domain-search option specifies a  ´search  list´  of  Domain
> >  Names to be used by the client to locate not-fully-qualified do‐
> >  main names.  The difference between this option and historic use
> >  of  the domain-name option for the same ends is that this option
> >  is encoded in RFC1035 compressed labels on the wire.  For  exam‐
> >  ple:
> > 
> >option domain-search "example.com", "sales.example.com",
> > "eng.example.com";

Oops, I must have overseen it.  I've read the man pages but probably I only
read dhcpd(8) and dhcpd.conf(5), but missed dhcp-options(5).

Thanks,
Steve

Re: Bridger deux VLAN avec systemd network

[Patrick ZAJDA]

Bonjour,


Le contexte est le suivant :

J'utilise des TP-Link Deco M5 pour avoir un réseau wifi maillé et 
souhaite activé le réseau wifi invité.


La seule chose qui sépare ces réseau c'est un VLAN tagué pour le réseau 
invité.


Les adresses IP sont dans le même rang pour les deux réseaux, les 
paramètres DHCP sont en tout point similaires pour les réseau principal 
et invité. Il n'y a aucun paramètre DHCP séparé pour le réseau invité.



Sur un Raspberry Pi, j'ai installé Adguard et souhaite donc l'utiliser 
comme résolveur au niveau de tout le réseau.


Je pourais très bien spécifier l'adresse IP du Deco principal comme 
résolveur et faire en sorte que celui-ci prenne Adguard comme résolveur 
mais ça voudrait dire que toutes les requêtes viendraient de la même 
adresse IP, ce qui ne convient pas.



Il faudrait donc que ce résolveur soit joignable depuis le réseau 
principal comme invité et ce, en utilisant la même adresse IP.



J'espère avoir pu expliquer clairement pourquoi il n'y a pas d'autre 
solution qu'une seule IP qui serait joignable sur les deux VLAN...




Le 21/01/2022 à 14:10, JUPIN Alain a écrit :

Bonjour,

Je comprends pas trop le concept.
Pour moi l’intérêt des VLAN c'est d'isoler les réseaux (en utilisant 
les même équipements réseaux, switch par exemple).
En général on relie les VLAN entre eux par du routage, du moins j'ai 
toujours pratiqué de cette manière !


Bridger des VLAN, si c'est pour du test/apprentissage pourquoi pas, 
mais pour de la prod je me méfierait des effets de bords au niveau de 
la sécurité.


Alain JUPIN

Le 20/01/2022 à 14:51, Patrick ZAJDA a écrit :


Bonjour,


Est-il possible de bridger deux VLAN ?


Le but étant d'avoir une adresse IP commune aux deux VLAN pour que 
les deux puissent utiliser le même résolveur entre les réseaux 
principal et invité.


Si une autre méthode que le bridge est possible, je reste bien 
entendu ouvert aux alternatives :)



Pour le moment, j'ai testé ceci (en anglais) sans succès : 
https://www.variantweb.net/blog/creating-vlan-bridges-with-systemd-networkd/



Il utilise deux bridges mais le raspberry Pi sur lequel je le fait ne 
passe jamais en ligne.


J'ai tenté de n'utiliser qu'un seul bridge, avec le même résultat.


--
Patrick ZAJDA



--
Patrick ZAJDA

Re: User group "users"

[Roberto C . Sánchez]

On Fri, Jan 21, 2022 at 02:49:09PM +0100, Steve Keller wrote:
> I see that on my Debian systems there is a user group "users" with GID 100,
> but by default no user gets added to it.  So what is the purpose or reason
> to have it?
> 
> >From old Unix installations I know the group "users" which every user was
> a member of, by default.
> 
New users have gid 100 set as their primary group by default.  So, new
users are members of the group without having to be added to the group
in /etc/groups.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: DHCP and search list for DNS domains

[Charles Curley]

On Fri, 21 Jan 2022 13:57:47 +0100
Steve Keller  wrote:

> With DHCP I can tell a host the DNS server and the domain name of the
> network, which is then stored to /etc/resolv.conf.  But how can I add
> a list a domain names that should be searched when resolving a host
> name?

root@chaffee:~# grep -i search /etc/dhcp/dhcpd.conf
option domain-search "domain0", "domain1", "domain2";
root@chaffee:~# 

-- 
Does anybody read signatures any more?

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

Re: DHCP and search list for DNS domains

[Markus Schönhaber]

21.01.22, 13:57 +0100, Steve Keller:


With DHCP I can tell a host the DNS server and the domain name of the
network, which is then stored to /etc/resolv.conf.  But how can I add
a list a domain names that should be searched when resolving a host
name?

AFAICS, there is no option in DHCP to provide the search list.


From dhcp-options(5):


   option domain-search domain-list;

 The domain-search option specifies a  ´search  list´  of  Domain
 Names to be used by the client to locate not-fully-qualified do‐
 main names.  The difference between this option and historic use
 of  the domain-name option for the same ends is that this option
 is encoded in RFC1035 compressed labels on the wire.  For  exam‐
 ple:

   option domain-search "example.com", "sales.example.com",
"eng.example.com";


--
Regards
  mks

Re: Bridger deux VLAN avec systemd network

[JUPIN Alain]

Bonjour,

Je comprends pas trop le concept.
Pour moi l’intérêt des VLAN c'est d'isoler les réseaux (en utilisant les 
même équipements réseaux, switch par exemple).
En général on relie les VLAN entre eux par du routage, du moins j'ai 
toujours pratiqué de cette manière !


Bridger des VLAN, si c'est pour du test/apprentissage pourquoi pas, mais 
pour de la prod je me méfierait des effets de bords au niveau de la 
sécurité.


Alain JUPIN

Le 20/01/2022 à 14:51, Patrick ZAJDA a écrit :


Bonjour,


Est-il possible de bridger deux VLAN ?


Le but étant d'avoir une adresse IP commune aux deux VLAN pour que les 
deux puissent utiliser le même résolveur entre les réseaux principal 
et invité.


Si une autre méthode que le bridge est possible, je reste bien entendu 
ouvert aux alternatives :)



Pour le moment, j'ai testé ceci (en anglais) sans succès : 
https://www.variantweb.net/blog/creating-vlan-bridges-with-systemd-networkd/



Il utilise deux bridges mais le raspberry Pi sur lequel je le fait ne 
passe jamais en ligne.


J'ai tenté de n'utiliser qu'un seul bridge, avec le même résultat.


--
Patrick ZAJDA

User group "users"

[Steve Keller]

I see that on my Debian systems there is a user group "users" with GID 100,
but by default no user gets added to it.  So what is the purpose or reason
to have it?

>From old Unix installations I know the group "users" which every user was
a member of, by default.

Steve

Re: ** Ceci est peut etre un SPAM IMSS:Bridger deux VLAN avec systemd network

[Luc Novales]

Bonjour,

Le 20/01/2022 à 14:51, Patrick ZAJDA a écrit :


Bonjour,


Est-il possible de bridger deux VLAN ?


Le but étant d'avoir une adresse IP commune aux deux VLAN pour que les 
deux puissent utiliser le même résolveur entre les réseaux principal 
et invité.


Si une autre méthode que le bridge est possible, je reste bien entendu 
ouvert aux alternatives :)


C'est le concept même de bridger des VLAN qu'il faut peut-être 
questionner. Je ne comprends pas trop le besoin car on fait d'habitude 
des VLAN pour avoir des réseaux étanches et si des informations doivent 
passer de l'un à l'autre, c'est par du routage et pas par du partage 
d'adresse qu'on le gère.


Sans plus d'information sur le besoin (un croquis ?), on ne peut pas 
suggérer de solution plus classique.


Bonne journée,

Luc.

Authentication required message window after nvidia drivers installation.

[Thanos Katsiolis]

Hello,

the title of the post says pretty much everything.
I have the NVIDIA Quadro P400 graphics card and installed the NVIDIA
drivers as described in Debian wiki NVIDIA Proprietary Driver
 for Debian 11.2.

The message appears when an Application starts or when a window from an
application opens. Some applications were left with a blank screen
when launching, but after a restart, when I press escape on the message,
the application starts normally.
Any ideas on how to fix it?

DHCP and search list for DNS domains

[Steve Keller]

With DHCP I can tell a host the DNS server and the domain name of the
network, which is then stored to /etc/resolv.conf.  But how can I add
a list a domain names that should be searched when resolving a host
name?

AFAICS, there is no option in DHCP to provide the search list.  So the
questions is, is there a way to configure locally in the client host a
search list that is added to /etc/resolv.conf?

Say, for example, my domain domain is foo.bar.org and the DHCP server
configuration has

option domain-name "foo.bar.org";
option domain-name-servers ns.foo.bar.org;

but I want bar.org also in the DNS domain search list, so I can

ping host

to get host.bar.org.  That is, in /etc/resolv.conf there should be

domain foo.bar.org
search foo.bar.org bar.org
nameserver 

AFAIK, some of my client hosts have only resolvconf, others use some
systemd stuff, since the man page for resolvconf is actually the
man page for resolvectl which also refers to systemd-resolved.

Steve

Re: chromium , google-chrome : ingérables avec Bullseye

[Luc Novales]

Re,

Le 21/01/2022 à 12:03, ajh-valmer a écrit :

On Friday 21 January 2022 11:28:36 Luc Novales wrote:

Le 21/01/2022 à 11:18, ajh-valmer a écrit :

Encore Chromium (Libre) je peux comprendre des bugs,
mais le navigateur Google-Chrome créé par la richissime Google,

Les nouveaux savent que vendredi est jour de troll ?

Pige pas, Google-Chrome est bien le navigateur le plus utilisé...
(Windows, Mac, GNU/Linux...)


C'est la façon dont tu as tourné ta phrase qui peut sous-entendre que 
Chromium est moins bon parcequ'il est libre ;)
Tu aurais écrit "moins utilisé" à la place de libre, il n'y aurait pas 
eu de doute.


Sinon, par rapport au problème initial, je pense qu'il ne vient pas de 
Chromium, mais du contexte particulier sur cette machine, puisque 
personne d'autre ne l'a confirmé.


Je ne suis pas intervenu car mon navigateur quotidien est Brave (pas 
exactement Chromium), c'est la Version 1.34.80 Chromium: 97.0.4692.71 
(Build officiel) (64 bits).
Aucun problème de fonctionnement sous Gnome (pure Debian), ni sous XFCE 
(Debian facile).


Par contre, je suis sous X11 (compatibilité de certains logiciels), les 
problèmes sont ils sous Wayland ? Les problèmes sont ils identiques en 
changeant ce paramètre au login ?


Bonne journée,
Luc.

Re: TDE File Manager options

[Махно]

Hello.  You can try a good old file manager Dolphin (from TDE project).

2022-01-20, kt, 18:36 c. marlow  rašė:
>
> Hi,
>
> Yes, I know that in previous emails I was using LXDE, but I thought that I
> would nuke and pave give TDE a try since I had never tried TDE  before.
>
> And I am wondering what other file managers work with TDE 14 besides
> Konqueror,  which ain't worth a dang!
>
> Thanks,
> Chris
>

Re: Suggestions for tesseract

[Siard]

On Thu, 20 Jan 2022, Curt wrote:
> On 2022-01-20, Siard  wrote:
> > Bob Bernstein wrote:
> > > Executing 'apt-cache search tesseract' brings up a multitude of 
> > > packages.
> > >
> > > My need is simple enough, I think: I like to scan (using an 
> > > Epson scanner) pages of printed books -- almost one hundred per 
> > > cent text -- and then use OCR to produce pages from which I can 
> > > copy 'n paste snippets of text for note-taking purposes.
> > >
> > > What do the assembled multitudes suggest for a tesseract package 
> > > (that's the OCR I've been encouraged to use) on my bullseye 
> > > system, ...
> >
> > Once you have a PDF containing the images (img2pdf may be used for
> > that), I think the cleverest way is to use ocrmypdf.
> > It adds an OCR text layer to the PDF file, so the PDF text becomes
> > selectable and can be copied.
> > It uses the Tesseract OCR engine.
> >
> > $ ocrmypdf -f inputfile.pdf outputfile.pdf
>
> ocrmypdf has quite a few dependencies on my machine.
> 
> The  multitude of packages corresponds more or less to the multiple
> languages of the human multitude. I guess the OP's working in English
> ('tesseract-ocr-eng', pulled in with all the others here when installing
> the above).

With tesseract and one tesseract language package already installed,
installing ocrmypdf does not pull in more of them. At least, that's what
I see on my machine.

Re: Bridger deux VLAN avec systemd network

[Patrick ZAJDA]

Bonjour,



Le 20/01/2022 à 19:05, didier gaumet a écrit :


1) tu as redémarré le servive après les modifs?
# systemctl restart systemd-networkd


Oui, et juste après le Raspberry Pi passe hors ligne.



2) le wiki Debian avertit d'une particularité qui peut poser problème:
"Hint: in Debian Buster (probably also previous versions) systemd-
networkd may assign a different MAC-Address to the bridge than your
physical interface has. This may cause connection issues if your
service provider uses some kind of MAC-filtering when routing your
traffic. To circumvent such problems you may assign a MAC-address to
your bridge (probably the same as your physical device, replace the
'xx' with valid MAC): "
https://wiki.debian.org/SystemdNetworkd




Pas de filtrage particulier au niveau adresse MAC, tout au plus un bail DHCP 
statique assigné à la MAC de l'interface réseau.


J'essayerais d'assigner la MAC au bridge au cas où...


Merci beaucoup pour les pistes :)

--
Patrick ZAJDA

Re: Future of "his" packages in Debian

[local10]

Jan 21, 2022, 10:09 by b...@fineby.me.uk:

> Can be found here;
>
> https://www.preining.info/blog/2022/01/future-of-my-packages-in-debian/
>


As a KDE user I find the news regretful. Really puzzled as to what he actually 
said to warrant this kind of reaction (assuming it was warranted) and why 
people would be so eager to demote a long time contributor like that. Anyhow, 
hope everything will work out for the best for all parties involved.

Thanks to everyone who responded.

Re: chromium , google-chrome : ingérables avec Bullseye

[ajh-valmer]

On Friday 21 January 2022 11:28:36 Luc Novales wrote:
> Le 21/01/2022 à 11:18, ajh-valmer a écrit :
> > Encore Chromium (Libre) je peux comprendre des bugs,
> > mais le navigateur Google-Chrome créé par la richissime Google,
> Les nouveaux savent que vendredi est jour de troll ?

Pige pas, Google-Chrome est bien le navigateur le plus utilisé...
(Windows, Mac, GNU/Linux...)

On Wednesday 19 January 2022 14:00:56 Haricophile wrote:
> A cause de problèmes dont je ne connais pas le détail, mais
> qui est je crois le cycle de mise-à-jour de Chrome qui est ## avec
> pas mal de problèmes associés, Ubuntu met chromium/chrome en snap. C'est
> peut-être un moyen de résoudre ton problème, même si ça oblige à
> installer snap.

Re: Problème de lecture vidéo (trop rapide)

[BERTRAND Joël]

didier gaumet a écrit :
> 
> 
> Le jeudi 20 janvier 2022 à 21:36 +0100, BERTRAND Joël a écrit :
>>> Bon, je vais commencer par virer l'intrus que je n'ai
>>> jamais installé à
>>> la main. Je serais assez curieux de voir par quel dépendance
>>> miraculeuse
>>> il est arrivé jusque là...
>>
>> Mauvaise pioche.
>>
>> Le résultat est toujours le même. En plein écran, plus aucun
>> son. Mais
>> si je bascule la sortie sur l'interface casque, analogique, toute
>> bête,
>> ça fonctionne. Le problème est donc plus autour du pilote HDMI que du
>> son lui-même.
> 
> - tu peux éventuellement envisager la piste du mauvauis contact dans le
> câble HDMI (essayer un autre câble si tu en as un), verifier les specs
> HDMI des 2 ports (PC et l'appareil à l'autre bout, et tester d'autres
> prises HDMI si tu en as plusieurs sur le PC ou l'appareil)

Je n'y crois pas, c'est beaucoup trop reproductible. Ça fonctionne, je
passe n plein écran, ça ne fonctionne plus. Le câble n'a aucune raison
de se synchroniser sur mes actions.

> - en ligne de commande tu peux exécuter pa-info (pas en root, en simple
> utilisateur), qui va donner pas mal d'infos sur le fonctionnement et la
> configuration de Pulseaudio et alsa sur ton système

Là non plus, pulseaudio n'est pas en cause, c'est après pulseaudio que
ça merdoie. Pulseaudio envoie des trames à la sortie matérielle qui gère
la chose n'importe comment.

JKB

Re: Where is Debian 11 installer for amd64 that works please ?

[Andrew M.A. Cater]

On Fri, Jan 21, 2022 at 09:10:01PM +1300, C.T.F. Jansen wrote:
> Greetings
> 
> I have been trying to install Debian 11 on an Asus from 2018 with i5 using
> amd64 install DVD's  with 11.1.0 and 11.2.0 and a net install CD with 11.2.0
> . All three have fallen over because of installer bugs.
> 
>   There is currently a Debian 9 system on the laptop that went on without
> difficulty.
> 

If you have already got a laptop that is running Debian: 

a. You can upgrade it in place to Debian 10 and Debian 11.

or

b. You can install Debian 11 over the top of 9 - this is a destructive
process but will give you an absolutely clean install.

This is a fairly regular topic on this list: I prefer to do a) but the
advice of others may vary.

First things first - copy off any data that you really must have - which 
is always a good plan. Also, note things that you may have changed / third
party .deb packages and so on - so that you have a head start if anything
goes wrong. [Network connection passwords, mail settings are always useful
and it's hard to remember and recreate them when they're wiped :) ]

If you do decide to upgrade in place: make sure that your Debian 9 installation
is up to date and fully patched first. Follow the release notes for Debian 10.
Upgrade to 10, reboot, then follow the release notes for 11 and upgrade.
You are bringing your machine forwards five years or so - so things will
change.

11.2 non-free network install should "just work" to install from scratch.
Installing to an external disk is possbile but not done as often as 
other install methods - you'd need to look very carefully at where and
how the grub bootloader is installed.

Some details of the erors you're seeing would be useful.

All the very best,

Andrew Cater

> Am trying to install it to an external hard disk so it can be tested and
> debugged without much damage to the running Debian 9 system.
> 
> The Debian 11.2.0 net install CD is the unofficial one with non free
> firmware. Good to have all the drivers in one go.
> It comes straight off the Debian website, is unmodified and is on a CD.
> 
> Where/how do I get one that works please ?
> 
> An alternate plan is to install from a Debian 10 net inst CD, non free,
> amd64. This one went on to another machine without difficulty . Then wait
> and see whether the Debian 12 installer is any better.
> 
> Thanks.
> 
> C.T.F. Jansen, ZL2TTS
> 

Re: chromium , google-chrome : ingérables avec Bullseye

[Luc Novales]

Bonjour,

Le 21/01/2022 à 11:18, ajh-valmer a écrit :

Hello,

Encore Chromium (Libre) je peux comprendre des bugs,
mais le navigateur Google-Chrome créé par la richissime Google,

Les nouveaux savent que vendredi est jour de troll ?

Bonne journée,
Luc.

Re: chromium , google-chrome : ingérables avec Bullseye

[ajh-valmer]

On Wednesday 19 January 2022 14:00:56 Haricophile wrote:
> Le Tue, 18 Jan 2022 22:15:49 +0100,
> "ajh-valmer"  a écrit :
> > rien n'y fait, j'ai toujours chromium ingérable.
> > Je ne vois pas pourquoi.

> A cause de problèmes dont je ne connais pas le détail, mais
> qui est je crois le cycle de mise-à-jour de Chrome qui est ## avec
> pas mal de problèmes associés, Ubuntu met chromium/chrome en snap. C'est
> peut-être un moyen de résoudre ton problème, même si ça oblige à
> installer snap.

Hello,

Encore Chromium (Libre) je peux comprendre des bugs,
mais le navigateur Google-Chrome créé par la richissime Google,
c'est bizarre.
Il reste Firefox avec aussi pas de problèmes.

Re: Future of "his" packages in Debian

[Andrew M.A. Cater]

On Fri, Jan 21, 2022 at 10:58:15AM +0100, local10 wrote:
> Jan 20, 2022, 22:09 by pior...@gmx.com:
> 
> > On 20/01/2022 18:17, Marco Valli wrote:
> >
> >>> by Norbert Preining · 2022/01/14
> >>>
> >>> After having been (again) demoted (blah)
> >>> based on flimsy arguments, I have been forced to rethink the level
> >>> of contribution I want to do for Debian. Blah blah blah blah
> >>> [...]
> >>>
> 
> 
> Can someone post what Norbert Preining actually wrote without omissions and 
> rather frivolous additions by other parties?
> 
> Regards,
>

>From Norbert's blog, aggregated on Planet Debian:

https://www.preining.info/blog/2022/01/future-of-my-packages-in-debian/

With every good wish, as ever,

Andrew Cater 

Re: Future of "his" packages in Debian

[Brad Rogers]

On Fri, 21 Jan 2022 10:58:15 +0100 (CET)
local10  wrote:

Hello local10,

>Jan 20, 2022, 22:09 by pior...@gmx.com:
>Can someone post what Norbert Preining actually wrote without omissions
>and rather frivolous additions by other parties?

Can be found here;

https://www.preining.info/blog/2022/01/future-of-my-packages-in-debian/

-- 
 Regards  _
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Do you want to play?
Play With Me - Extreme


pgpSRDcqPhhu0.pgp
Description: OpenPGP digital signature

Special installation issue

[Hans]

Hello all,

I am stuck with a special installation problem, maybe you can help me.

I want to install debian/armhf onto a tablet "Microsoft Surface RT". This one 
is UEFI-dongled, can officially not boot from an USB-stick, and can officially 
not be installed with any other OS than MS Windows ERT.

However I managed to get it booted from USB-Stick with some special tricks, it 
looks like the kernel is booting, but then I am stuck in the shell of grub.

On my USB-Stick is the debian-installer-iso for arm architecture.

Now my question: When I am in the grub shell, is it possible, to manually 
mount the iso and get access to the installer routine within the iso-image?

I believe (but I am not experienced enough at the moment), that the hardest 
thing is already done, whe I am so far, as I am. Maybe, next step will be 
easier, as soon I can start the installer routine. But here stops my 
knowledge. 

Any ideas? Thanks in advance.

And if my plan is not possible, then please let me know, that I will stopp my 
efforts.

Best 

Hnas 
 

Re: Future of "his" packages in Debian

[local10]

Jan 20, 2022, 22:09 by pior...@gmx.com:

> On 20/01/2022 18:17, Marco Valli wrote:
>
>>> by Norbert Preining · 2022/01/14
>>>
>>> After having been (again) demoted (blah)
>>> based on flimsy arguments, I have been forced to rethink the level
>>> of contribution I want to do for Debian. Blah blah blah blah
>>> [...]
>>>


Can someone post what Norbert Preining actually wrote without omissions and 
rather frivolous additions by other parties?

Regards,

Re: Firefox PDF download - strange behaviour.

[Andrei POPESCU]

On Ma, 18 ian 22, 11:35:04, The Wanderer wrote:
> 
> Looking at that example, I note that it starts with the variable name
> "currentDirHandle". I think it's intended, although not explicitly
> stated, that the directory path specified in that function call is
> *relative*; that would let the API be used to create subdirectory trees
> underneath the user-chosen directory, but not outside of there.
> 
> So this could potentially be dangerous if the user chooses a directory
> location that's high enough in the directory tree to have important
> files already underneath it, but not if the user chooses e.g. a
> dedicated Downloads directory.
> 
> I can still envision scenarios in which this could be dangerous, but
> unless there are ways to get access to a file-handle variable that don't
> rely on something directly user-interactive (the ones described in that
> page are file-picker dialogs and "drag and drop a file into (a specific
> area of?) the browser window"), I don't think it can plausibly do so in
> a way that's invisible to the user.

This reminds me of 

https://arstechnica.com/gadgets/2021/07/separate-eop-flaws-let-hackers-gain-full-control-of-windows-and-linux-systems/

(the second part, with the Linux vulnerability)

Letting some random site have access to local storage seems like a Very 
Bad Idea.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: chromium , google-chrome : ingérables avec Bullseye

[Haricophile]

Le Wed, 19 Jan 2022 20:56:11 +0100,
didier gaumet  a écrit :

> Arf, l' histoire du chat c'est vraiment le truc auquel j'aurais jamais
> pensé :-)

Je ne sais plus sur quel liste, quelqu'un a avoué avoir fait un poisson
d'avril qui a mal tourné : Il a échangé les clavier et souris
bluetooth dans un bureau de compta. Grosse erreur, comme ça bougeait
sur les écrans et ils ne comprenaient pas pourquoi, ils ont
immédiatement coupé tout le système et contacté la DSI qui a envoyé
quelqu'un sur place... bref il y a des bonnes idées qu'il faut garder
pour soi, et la morale c'est que les clavier bluetooth dans un bureau,
c'est pas sécurisé ;-)

Re: Where is Debian 11 installer for amd64 that works please ?

[Joe]

On Fri, 21 Jan 2022 21:10:01 +1300
"C.T.F. Jansen"  wrote:

> Greetings
> 
> I have been trying to install Debian 11 on an Asus from 2018 with i5 
> using amd64 install DVD's  with 11.1.0 and 11.2.0 and a net install
> CD with 11.2.0 . All three have fallen over because of installer bugs.
> 
>There is currently a Debian 9 system on the laptop that went on 
> without difficulty.
> 
> Am trying to install it to an external hard disk so it can be tested
> and debugged without much damage to the running Debian 9 system.
> 
> The Debian 11.2.0 net install CD is the unofficial one with non free 
> firmware. Good to have all the drivers in one go.
> It comes straight off the Debian website, is unmodified and is on a
> CD.
> 
> Where/how do I get one that works please ?
> 
> An alternate plan is to install from a Debian 10 net inst CD, non
> free, amd64. This one went on to another machine without difficulty .
> Then wait and see whether the Debian 12 installer is any better.
> 

Are you willing to release the secret of what is going wrong with the
installer? Because it certainly Works For Me (tm).

Now, there may be issues with your particular hardware, but we'll only
be able to troubleshoot that if you tell us what the issues are.

I note you tell us how old the laptop is, but not the age of the
external drive. I mention this because I have, not unreasonably, had
trouble trying to install to a 12-year-old drive which turned out to
be a bit dodgy...

-- 
Joe

Re: Hyper-typematic and Firefox responsiveness in Weston.

[Andrei POPESCU]

On Ma, 18 ian 22, 08:10:30, pe...@easthope.ca wrote:
> 
> Thanks.  Revised version.
> 
> fire () { case "$#" in
>   0) firefox-esr --display=:0 file:///home/peter/MY/Peter.html#Links & ;;
>   1) firefox-esr --display=:0 "$1" & ;;
>   *) echo "Too many arguments." ;; esac
> }

According to the manpage '--display' is an X11 option.

Could it be that it actually forces Firefox to run via XWayland or so?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Problème de lecture vidéo (trop rapide)

[didier gaumet]

Le jeudi 20 janvier 2022 à 21:36 +0100, BERTRAND Joël a écrit :
> > Bon, je vais commencer par virer l'intrus que je n'ai
> > jamais installé à
> > la main. Je serais assez curieux de voir par quel dépendance
> > miraculeuse
> > il est arrivé jusque là...
> 
> Mauvaise pioche.
> 
> Le résultat est toujours le même. En plein écran, plus aucun
> son. Mais
> si je bascule la sortie sur l'interface casque, analogique, toute
> bête,
> ça fonctionne. Le problème est donc plus autour du pilote HDMI que du
> son lui-même.

- tu peux éventuellement envisager la piste du mauvauis contact dans le
câble HDMI (essayer un autre câble si tu en as un), verifier les specs
HDMI des 2 ports (PC et l'appareil à l'autre bout, et tester d'autres
prises HDMI si tu en as plusieurs sur le PC ou l'appareil)

- en ligne de commande tu peux exécuter pa-info (pas en root, en simple
utilisateur), qui va donner pas mal d'infos sur le fonctionnement et la
configuration de Pulseaudio et alsa sur ton système

Re: TDE File Manager options

[Hans]

Am Donnerstag, 20. Januar 2022, 23:20:58 CET schrieb deloptes:
Yes, you are correct. It is just too long ago, my fault.
But almost 25 years with linux is also a rather long time, and as I came from 
DOS I am Norton Commander contaminated.

Sorry for my mistake.

Happy hacking!

Hans 

> Hans wrote:
> > Reading these, and I am also very old school, with my first linux
> > installation of SuSE 6.0 in 1986, I am asking myself: What is better,
> > working fast or working with nice tools?
> 
> according to this article https://en.wikipedia.org/wiki/SUSE_Linux
> SuSE Linux 6.0  was released on 1998-12-21
> 
> AFAIR October 4, 1985 was founded the free software foundation

Where is Debian 11 installer for amd64 that works please ?

[C.T.F. Jansen]

Greetings

I have been trying to install Debian 11 on an Asus from 2018 with i5 
using amd64 install DVD's  with 11.1.0 and 11.2.0 and a net install CD 
with 11.2.0 . All three have fallen over because of installer bugs.


  There is currently a Debian 9 system on the laptop that went on 
without difficulty.


Am trying to install it to an external hard disk so it can be tested and 
debugged without much damage to the running Debian 9 system.


The Debian 11.2.0 net install CD is the unofficial one with non free 
firmware. Good to have all the drivers in one go.

It comes straight off the Debian website, is unmodified and is on a CD.

Where/how do I get one that works please ?

An alternate plan is to install from a Debian 10 net inst CD, non free, 
amd64. This one went on to another machine without difficulty . Then 
wait and see whether the Debian 12 installer is any better.


Thanks.

C.T.F. Jansen, ZL2TTS