Re: Mate: mouse too sensitive
Am Thu, Mar 14, 2024 at 04:33:56PM + schrieb Ottavio Caruso: > My Logitech wireless mouse has always been a bot over-sensitive, but now, > going into its 7th years of life, has become even more erratic. I am not > complaining about the speed, just the sensitivity. I have to be very careful > not moving the mouse too much in order not to close/open windows, > accidentally removing text, etc. > > I have configured "mate-mouse-properties" to the lowest possible sensitivity > (changing the acceleration doesn't make much difference), but it is still > too sensitive. > > This the output from xinput: > > $ xinput list-props 'Logitech Wireless Mouse' > Device 'Logitech Wireless Mouse': > Device Enabled (177): 1 > Coordinate Transformation Matrix (179): 1.00, 0.00, 0.00, > 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 > libinput Natural Scrolling Enabled (316): 0 [...] > Any clue? I have slowed down a mouse by the following line in my .xinitrc: xinput set-prop "Logitech USB Optical Mouse" "Coordinate Transformation Matrix" 0.5 0 0 0 0.5 0 0 0 2 Adjusting the coordinate transformation matrix might be one way to go. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: lists
Am Wed, Dec 20, 2023 at 04:14:57PM +0100 schrieb Marco Moock: > Am 20.12.2023 um 16:11:05 Uhr schrieb Christoph Brinkhaus: > > > I have heard that there is a countermeasure against spam run be big > > mail providers by rejecting the first contact by SMTP and accepting > > the next contact. Most spammers seem to try just once. > > Do they reject with 5xx or 4xx? > Honestly I do not know. Kind regards, Christoph signature.asc Description: PGP signature
Re: lists
Am Wed, Dec 20, 2023 at 08:13:12AM -0500 schrieb Pocket: > > On 12/20/23 07:59, Andy Smith wrote: [...] > Every 60 days I get kicked from this list which I receive an email stating > my kick value is 2%. I receive this mails, too. The first impression is scary, but in the body there is an explanation. The statement is that there are some bounces but your account will be deleted if the kick rate exceeds a limit much higher than 2%. AFAIR the limit is 80% so so. I have heard that there is a countermeasure against spam run be big mail providers by rejecting the first contact by SMTP and accepting the next contact. Most spammers seem to try just once. I am not sure if this is 100% true or related to your situation. Please verify the content of the kick rate mail. I am quite sure that it is not as serious as it sounds on the first impression. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Non-delivery reports from postmas...@ewetel.de
Am Fri, Dec 01, 2023 at 11:02:47PM + schrieb Andy Smith: > Hi, > > Is anyone else receiving non-delivery report emails from > postmas...@ewetel.de for every email they post to debian-user? They > look like this: > > From: postmas...@ewetel.de > To: a...@strugglers.net > Subject: E-Mail Abweisungsbenachrichtigung / email bounce notification > > It goes on to state that the message wasn't delivered because the > recipient's mailbox is full. > > I've received one for every email I've sent to debian-user over the > last 4 days. Anyone else? If so, can you let > listmas...@lists.debian.org know? Hello Andy, I have received one mail like that when posting to the l10 list. The mail appeared in the list in spite of that message. With further mails everything has been back to normal. > > Naturally, ewetel.de should be rejecting these messages inside the > SMTP connection if they can't be delivered to their user. > > Failing that, they should be sending NDRs to the envelope sender, > which is the Debian mailing list software, which would then take > care of unsubscribing the undeliverable address. > > It seems to have done the very broken thing of sending an NDR to the > from address. If that assessment is correct, Debian listmasters will > need to disable delivery to this subscriber manually. > > But, possibly whatever problem it was has fixed itself by now. If > ewetel were ALSO sending an NDR to the envelope sender then the > subscriber would have been disabled eventually. Kind regards, Christoph signature.asc Description: PGP signature
Re: in Debian bookworm /var/log/syslog is empty
Am Tue, Nov 21, 2023 at 05:15:24AM -0500 schrieb John Covici: > hmmm, I looked at the release notes, but it does not say how to > restore the old behavior, it just says many files are no longer > necessary and lists them. I am using logwatch and that program seems > to be effected, I would be OK, if I could get logwatch to work > properly. I have searched a little bit. The question is if rsyslog is really properly up and running. https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#changes-to-system-logging https://www.server-world.info/en/note?os=Debian_12&p=rsyslog If journalctl does not show any issues related to rsyslog it boils down to the question raised by Marco. > > On Tue, 21 Nov 2023 04:32:35 -0500, > Christoph Brinkhaus wrote: > > > > [1 ] > > Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici: > > > Hi. I am using bookworm with latest updates and /var/log/syslog is > > > empty, even though rsyslog is runniing. I am also using logwatch and > > > not getting at least some responses I should get such as fail2ban. > > > These may be separate problems, but any help on those would be > > > appreciated. I saw a previous thread, but it does not seem to apply > > > to my situation. > > > > Hi John, > > from Bookworm on the default log system has been changed to the > > systemd-mechanism only. In the Bookworm release notes is a section about > > logging. It describes how to re-enable the conventional logging > > facilities. I hope this pointer is helpful. > > > > > Your life is like a penny. You're going to lose it. The question is: > > > How do > > > you spend it? > > > > > > John Covici wb2una > > > cov...@ccs.covici.com > > > > > This is a very wise statement. Mine is just a joke in German. > > > > Kind regards, > > Christoph > > -- > > Ist die Katze gesund > > schmeckt sie dem Hund. > > [2 signature.asc ] > > Verifying... > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > cov...@ccs.covici.com > signature.asc Description: PGP signature
Re: in Debian bookworm /var/log/syslog is empty
Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici: > Hi. I am using bookworm with latest updates and /var/log/syslog is > empty, even though rsyslog is runniing. I am also using logwatch and > not getting at least some responses I should get such as fail2ban. > These may be separate problems, but any help on those would be > appreciated. I saw a previous thread, but it does not seem to apply > to my situation. Hi John, from Bookworm on the default log system has been changed to the systemd-mechanism only. In the Bookworm release notes is a section about logging. It describes how to re-enable the conventional logging facilities. I hope this pointer is helpful. > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > cov...@ccs.covici.com > This is a very wise statement. Mine is just a joke in German. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Fetching local mail
Am Sat, Nov 18, 2023 at 10:15:42AM -0500 schrieb Paul M Foster: > On Sat, Nov 18, 2023 at 09:29:02AM -0500, Dan Ritter wrote: > > > Paul M Foster wrote: > > > After using claws-mail for a number of years, I'm testing the idea of > > > going > > > back to mutt and fetchmail. One problem I've encountered is how to get > > > local mail in /var/mail/paulf into mutt's inbox at /home/paulf/Mail/in. > > > > > > I could run a POP server, and have fetchmail query it like any other > > > smarthost, but I'd rather not add another daemon. Does anyone know a way > > > to > > > have mutt and/or fetchmail grab mail from /var/mail/paulf to > > > /home/paulf/Mail/in? > > > > Options: > > > > 1. tell mutt your spool is /var/mail/paulf: > > > > set spoolfile="/var/mail/paulf" > > This would be okay if all my mail was delivered to that spool file, but it > isn't. Fetchmail hands off (internet) mail to maildrop, which puts in my > spool file at /home/paulf/Mail/in. That's where mutt thinks my spool file > is. Only mail generated by the system or cron jobs is delivered to > /var/mail/paulf. And I'd like that mail to end up instead in > /home/paulf/Mail/in. > > Also worth noting that I have exim installed, which handles the cron job > emails, and puts them, by default into the standard location, > /var/mail/paulf. > > > > > (if that's a Maildir, end it with a /) > > > > 2. tell fetchmail to deliver via a local agent that will put > > things where you want them, like procmail or mailfilter or... > > anyway, use the 'mda' config in fetchmail's config file to > > specify that. > > > > Fetchmail already hands off to maildrop, which puts all (internet) mail in > /home/paulf/Mail/in. But it appears that fetchmail only queries servers, > and then passes off the mail to an mda. I can't get it to simply copy mail > (and delete it) from a spool file and deliver it to the mda. If you configure fetchmail not to use an MDA as maildrop, fetchmail will deliver incomming mails to exim. May be this is an option. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: how to bring up message and prevent user login when not connected to a particular VLAN? (was: how to force mounting an entry in fstab on boot?)
Am Mon, Oct 23, 2023 at 05:57:28PM +0200 schrieb hw: > On Mon, 2023-10-23 at 17:40 +0200, hw wrote: > > On Mon, 2023-10-23 at 16:53 +0200, Christoph Brinkhaus wrote: > > > Am Mon, Oct 23, 2023 at 04:17:11PM +0200 schrieb hw: > > > > Hi, > > > > > > > > I have an entry in the fstab to mount an NFS share via IPv6. For > > > > unknown reasons, the entry is being ignored on boot, so after booting, > > > > I have to log in as root and do a 'mount -a' which mounts the share > > > > without problems. > > > > > > > > The entry in the fstab looks like this: > > > > > > > > > > > > [fd53::11]:/srv/example /home/example/foo nfs > > > > _netdev 0 0 > > Ok, it seems to work with: > > > ... nfs defaults,_netdev,x-systemd.after=network-online.target 0 0 > > > So the '_netdev' option is broken. I'll have to see if this reboot > was an exception, but there's no good reason to assume that it won't > work next time, too. > > So the next question remains: > > > [...] > > > > So how do I force it that the entries in fstab are not being silently > > > > ignored? I want these shares either mounted, like through like 3 > > > > retries, or booting to stop when they can't be mounted. > > > > > > > I have never tried to implement things as 3x retries or so. > > > > Well, the retries are not so relevant; I'd expect that to happen > > anyway. But how can I stop the booting when a mount fails? > > > > Alternatively, how can I prevent booting or have the machine becoming > > inaccessible when it's not connected to a particular VLAN? Like the > > users can't log in and instead get a message that the computer is > > incorrectly connected ... > > Let me add that the machines are currently unaware that they are > connected to a VLAN because the switch ports are configured untagged. > I could change that to tagged but I don't see how that would solve > anything. > > Unless maybe I could intervene before starting gdm by pinging a server > and bringing up a message instead of starting gdm when the server > can't be reached. That should be possible, but how would I bring up a > message instead of gdm? It doesn't even have to be a GUI that's > starting, just a message would suffice. After that, automatically > shut down after a 2 minutes or so ... > I have digged a little bit because this is an interesting task. I have tried to use the crontab of root but the messages are not printed to the console but send by mail. For that test I have not been logged in which seems to be your use case. Then I have had a look at gdm. I think one option to display stuff is to use gdm itself. The message of the greeting screen can be configured. A restart of gdm should be enough to update the content of the screen. I do not use gdm to try that. But I think that is at least an option. Kind regards, Christoph signature.asc Description: PGP signature
Re: how to force mounting an entry in fstab on boot?
Am Mon, Oct 23, 2023 at 05:40:54PM +0200 schrieb hw: > On Mon, 2023-10-23 at 16:53 +0200, Christoph Brinkhaus wrote: > > Am Mon, Oct 23, 2023 at 04:17:11PM +0200 schrieb hw: > > > Hi, > > > > > > I have an entry in the fstab to mount an NFS share via IPv6. For > > > unknown reasons, the entry is being ignored on boot, so after booting, > > > I have to log in as root and do a 'mount -a' which mounts the share > > > without problems. > > > > > > The entry in the fstab looks like this: > > > > > > > > > [fd53::11]:/srv/example /home/example/foo nfs > > > _netdev 0 0 > > > > > > > > > I have another case in which machines need to be connected to a > > > particular VLAN to mount home directories. In case they are not > > > connected to that VLAN, I don't want the boot process to proceed at > > > all because the home directories won't be available. > > > > You might need the "late" option of mount. Its purpose is to mount when > > prerequisites as the network are available already. > > There doesn't seem to a 'late' option in the man pages. Having > '_netdev' is supposed to make sure that the network is up before > mounting ... Ups, that has been in my mind. It exists in FreeBSD but not in Debian. > > I found this, though: > https://unix.stackexchange.com/questions/349264/fstab-mount-wait-for-network > > I'll try that, plus 'defaults'. > > > > So how do I force it that the entries in fstab are not being silently > > > ignored? I want these shares either mounted, like through like 3 > > > retries, or booting to stop when they can't be mounted. > > > > > I have never tried to implement things as 3x retries or so. > > Well, the retries are not so relevant; I'd expect that to happen > anyway. But how can I stop the booting when a mount fails? > > Alternatively, how can I prevent booting or have the machine becoming > inaccessible when it's not connected to a particular VLAN? Like the > users can't log in and instead get a message that the computer is > incorrectly connected ... > You could start a crontab job to check the status some time after boot or create a systemd unit after almost everything has been finished. Kind regards, Christoph signature.asc Description: PGP signature
Re: how to force mounting an entry in fstab on boot?
Am Mon, Oct 23, 2023 at 04:17:11PM +0200 schrieb hw: > Hi, > > I have an entry in the fstab to mount an NFS share via IPv6. For > unknown reasons, the entry is being ignored on boot, so after booting, > I have to log in as root and do a 'mount -a' which mounts the share > without problems. > > The entry in the fstab looks like this: > > > [fd53::11]:/srv/example /home/example/foo nfs > _netdev 0 0 > > > I have another case in which machines need to be connected to a > particular VLAN to mount home directories. In case they are not > connected to that VLAN, I don't want the boot process to proceed at > all because the home directories won't be available. You might need the "late" option of mount. Its purpose is to mount when prerequisites as the network are available already. > > So how do I force it that the entries in fstab are not being silently > ignored? I want these shares either mounted, like through like 3 > retries, or booting to stop when they can't be mounted. > I have never tried to implement things as 3x retries or so. Kind regards, Christoph signature.asc Description: PGP signature
Re: Bookworm: NetworkManager
Am Sat, Oct 21, 2023 at 02:40:49PM -0400 schrieb Pocket:
>
> On 10/21/23 14:32, Stefan Monnier wrote:
> > > > > I want NetworkManager to not over write /etc/resolv.conf
> > [...]
> > > My setup is that I was a dhcp server to give out IPs and DNS info.
> > > That way I can control those things without having to do so on every
> > > system.
> > Populating `/etc/resolv.conf` from the DHCP-provided info is a useful
> > part of "control those things without having to do so on every system",
> > so I don't see why you "want NetworkManager to not over write
> > /etc/resolv.conf".
> >
> >
> > Stefan
> >
> I agree about that on most machines, but the machine in question has bind
> running so nameserver needs to be set to 127.0.0.1 and the domain to
> example.org in the resolv.conf file.
>
> This is my problem in a nutshell
I am not 100% sure if I fully understood your setup. My system gets its
network settings via DHCP. I also run a nameserver on 127.0.0.1. My
external interface is bond0. I have the following configuration:
#v+
ris@lenovo ~> cat /etc/dhcp/dhclient.conf|grep -v "^#"
option rfc3442-classless-static-routes code 121 = array of unsigned
integer 8;
send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn,
dhcp6.sntp-servers,
netbios-name-servers, netbios-scope,
interface-mtu,
rfc3442-classless-static-routes,
ntp-servers;
interface "bond0" {
supersede domain-name-servers 127.0.0.1;
}
#v-
The last block prevents my local resolv.conf to be overwritten.
I am not sure if that measure could help in your setup.
Kind regards,
Christoph
--
Ist die Katze gesund
schmeckt sie dem Hund.
signature.asc
Description: PGP signature
Re: Problem with libreoffice and localisation - LO hangs
Am Fri, Sep 01, 2023 at 02:57:29PM +0200 schrieb Hans: Hello Hans, [...] > It might be, that I installed the localisation from 7.5 on LO-7.4, as both > are > in the repo. At the moment, I can not recheck it. Just as reference: I run Bookworm and I have installed the metapackage. I have no issues running libreoffice. dpkg -l lists almost everything as ii liblibreoffice-java 4:7.4.7-1 all LibreOffice UNO runtime environment -- Java library ii libreoffice 4:7.4.7-1 amd64office productivity suite (metapackage) ii libreoffice-base 4:7.4.7-1 amd64office productivity suite -- database ii libreoffice-help-de 4:7.4.7-1 all office productivity suite -- German help ii libreoffice-l10n-de 4:7.4.7-1 all office productivity suite -- German language package ... Just two parts look different ii libreoffice-nlpsolver 4:0.9+LibO7.4.7-1all "Solver for Nonlinear Programming" extension for LibreOffice ii libreoffice-wiki-publisher 4:1.2.0+LibO7.4.7-1 all LibreOffice extension for working with MediaWiki articles I hope it helps at least a little bit. Viele Grüße, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: git setup
Am Tue, Aug 22, 2023 at 03:00:33AM + schrieb Russell L. Harris: Hello Russel, I cannot answer your question directly but show what I am doing now. > After much searching and reading, I have not discovered how to set up > a pair of git repositories to work together. > > I write articles for publication. I typically spend anywhere from > several hours to many days on each article. It is frustrating to work > for an hour or two on a paragraph or a page and then accidentally to > erase what I have written. > > In the past, I have found git to be a very good solution. But now I > am moving to a new computer, and I an having difficulty replicating > the previous setup. > > My needs are simple. I need two git repositories. > > The first is my work space, into which periodically I commit the > article on which I am working. > > The second repository is my backup; it resides on another machine. > Several times a day, I SSH into the backup machine and pull the > working repository. It would be nice to be able to push from WORKING > to BACKUP, eliminating the need to SSH. I have almost the same setup and use local git repositories. Instead of syncing them by the git tools I use rsync to update the backup from time to time. This is a dumb method but it works. > I cloned the WORKING repository from the old host, and the WORKING > repository appears to function correctly. But I do not know how to > configure the BACKUP repository. I tried the BARE option, but I am not > able to push from WORKING to BACKUP. To dig that is on my todo list as well. But as an additional backup I would run the dump method in parallel, just in case I manage to screw up the git repository. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: /etc/resolv.conf changes every booting time
Am Sun, Aug 06, 2023 at 05:17:23PM +0800 schrieb Jon Smart:
Hi Jon,
> It's a VPS provided by a local ISP. The VPS has a static IPv4.
> Do you know how to know if /etc/resolv.conf is modified by dhcp?
>
I am not sure about the details. But with DHCP a bunch of network
configuration items can be send from the server to the client. The
nameserver configuration is one of the items.
Kind regards,
Christoph
>
> >
> > Hi Jon,
> >
> >> I have removed the default systemd-resolved local dns service following
> >> the link below,
> >>
> >> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
> >>
> >> And I have unbound installed and enabled as local DNS server.
> >>
> >> But every time I reboot the server, the configuration file
> >> /etc/resolv.conf changes to a default one. So every time I have to
> >> update
> >> its content to:
> >>
> >> nameserver 127.0.0.1
> >>
> >> (points to unbound)
> >>
> >> How to stop the auto-changes to /etc/resolv.conf after rebooting?
> >
> > In case you get the configuration overwritten by DHCP you can avoid that
> > by the following lines in /etc/dhcp/dhclient.conf.
> >
> > interface "bond0" {
> > supersede domain-name-servers 127.0.0.1;
> > }
> >
> > Just replace the interface name with yours.
> >
> > Kind regards,
> > Christoph
> > --
> > Ist die Katze gesund
> > schmeckt sie dem Hund.
> >
>
>
--
Ist die Katze gesund
schmeckt sie dem Hund.
signature.asc
Description: PGP signature
Re: /etc/resolv.conf changes every booting time
Am Sun, Aug 06, 2023 at 09:28:55AM +0800 schrieb Jon Smart:
Hi Jon,
> I have removed the default systemd-resolved local dns service following
> the link below,
>
> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
>
> And I have unbound installed and enabled as local DNS server.
>
> But every time I reboot the server, the configuration file
> /etc/resolv.conf changes to a default one. So every time I have to update
> its content to:
>
> nameserver 127.0.0.1
>
> (points to unbound)
>
> How to stop the auto-changes to /etc/resolv.conf after rebooting?
In case you get the configuration overwritten by DHCP you can avoid that
by the following lines in /etc/dhcp/dhclient.conf.
interface "bond0" {
supersede domain-name-servers 127.0.0.1;
}
Just replace the interface name with yours.
Kind regards,
Christoph
--
Ist die Katze gesund
schmeckt sie dem Hund.
signature.asc
Description: PGP signature
Re: Pulseaudio - Daemon.conf
Am Wed, Jul 19, 2023 at 01:24:06AM +0200 schrieb Stefan Schumacher: Hello Stefan, > Debian 11 had Pulseaudio as default, which had a > /etc/pulse/daemon.conf where you could set the bit- and sample > rate.There was even a very comprehensive manual page for it. > (pulse-daemon.conf(5)) > In my case I used 24bit and 192kHz in order to get the best possible > audio output of my Fiio K7. > I noticed that pulseaudio is not part of Debian Bookworm anymore. How > and where do I have to make these settings now? My system runs Bookworm and it is still running pulseaudio. As far as I remember the default has changed for a desktop environment, I think it has been gnome. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: getmail problem
Am Thu, Jul 13, 2023 at 08:18:07PM +0200 schrieb Pierre Frenkiel: Hi Pierre, > hi, > > the problem with getmail is that it ignores my .getmailrc file: > it is configured with gmail: > > server = imap.gmail.com > ... > poll imap.gmail.com with proto IMAP auth password > > but the getmail command gives: > SimpleIMAPRetriever:p.frenk...@imap.laposte.net:143: > > getmailrc: credential/login error (LOGIN command error: BAD [b'invalid > command']) > > ( my config is in ~.getmailrc and .getmail/getmailrc ) > > has anybody an explanation? Just a short in the dark - can it be that gmail does not accept imap on port 143 anymore? Instead of imap please try imaps on port 993. Kind regards, Christoph signature.asc Description: PGP signature
Re: fetchamil / procmail as non root : unable to call script
Am Tue, Jun 20, 2023 at 07:52:24AM +0200 schrieb BASSAGET Cédric: Bonjour Cédric, > Hello > I'm using fetchamil / procmail to fetch mails from an POP server and parse > it then launch a script or system call : [...] > This work fine when calling fetchamil as root with "fetchamil -f > .fetchmailrc". But when calling fetchmail from a dedicated user, the > external script in procmail is not called. It's written in the logfile that > : > > procmail: [25332] Mon Jun 19 16:20:28 2023 > procmail: Assigning "MATCH=" > procmail: Matched "<9088600d-446a-96b4-4043-29ecd0d5a...@dom.tld>" > procmail: Match on "^Message-ID: \/.*" > procmail: Assigning "LASTFOLDER= echo "whoami" > test.txt" > Subject: test > Folder: echo "whoami" > test.txt > 1824 > procmail: Executing " echo "whoami" > test.txt" I have faced a problem which is not exactly the same. I run fetchmail followed by maildrop which is a procmail replacement. I have had the issue that I have had to run fetchmail as a normal user (my account) when I wanted to invoke maildrop by fetchmail directly. I wanted to run fetchmail as the unprivileged user fetchmail. The workaround has been to delete maildrop from fetchmailrc. By doing so fetchmail forwards all mail to the mailserver on my machine. In my case I run opensmtpd. Opensmtpd is configured do forward mails for local addresses to maildrop. This resolved the conflict of the different accounts which run fetchmail and maildrop. Now fetchmail runs as the user fetchmail and maildrop by my account. I think that this method could be a workaround in your situation as well. I think so because it seems to be an issue related to privileges, too. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: [SOLVED] Re: Mouse trouble on sid
Am Wed, May 17, 2023 at 07:01:30PM +0100 schrieb Joe: Hello Joe, > > Oh dear, oh dear... > > Very sorry for the wasted time. This has been no wasted time. You have found an additional root cause for some unexpected behaviour all of us will be aware of from now on. > > When I tried the wired mouse I did not actually unplug the wireless > mouse receiver, so it was still generating scroll events every 200ms > while over a window (presumably being ignored by the kernel when it was > over unscrollable things like the background and panels. > > Quick removal and replacement of mouse battery and problem solved. And again we can blame the hardware :-). > > As partial reparation, could I recommend evemu-tools to anyone who > doesn't know about it? Cleans up that nasty raw output from cat > /dev/input/mouseX and adds times. Problem solved immediately with its > help. This is good to know. > > OK, I can't explain why Knoppix didn't also do it, the mouse was still > generating masses of scroll events. That really messed up the > troubleshooting. Knoppix doesn't have evemu-tools, but the raw mouse > events were enough by that time. It can be that the xinput of Knoppix is configured to do more de-bouncing of scroll events than the Debian system. You reported that Knoppix has been very slow. It could also be that Knoppix could not handle all the mouse events and did the de-bouncing by unintended throttling :-). Thank you for reporting about the fix and for the recommendation! Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Mouse trouble on sid
Am Tue, May 16, 2023 at 07:26:41PM +0100 schrieb Joe: Hello Joe, > On Tue, 16 May 2023 12:29:02 +0200 > Christoph Brinkhaus wrote: > > > Am Tue, May 16, 2023 at 11:02:50AM +0100 schrieb Joe: > > > > Hello Joe, > > > > [...deleted a lot...] > > > On Tue, 16 May 2023 10:44:03 +0100 > > > Joe wrote: > > > > > > > > One idea is to try a minimalistic window manager as twm to find > > > > > out if the issue is related to xfce. > > > > > > > > OK, tried twm and fvvm. Both unusable, as a left-click brings up a > > > > menu for a fraction of a second. Couldn't log out of either, had > > > > to switch to console and uninstall them. But they confirm the > > > > mouse problem. It's obviously fairly fundamental. > > > > > > > > Just tried previous kernel, but also bad. I can assume by now that > > > > nobody else has seen this problem. > > > > > > Just as a sanity check, I booted Knoppix, and of course there's no > > > problem, it's just an order of magnitude too slow from USB to do > > > anything useful. > > > > Now it seems as if the issue is related to X or the driver stuff. > > I have three ideas. > > > > 1. Do you have any xorg.conf things in /etc or the related > > directories? Nowadays X is not so bad in guessing the hardware which > > makes xorg.conf and such obsolete. If there are X config files it > > might be worth to move them to a safe place and to try without them. > > I can't find anything. This is a relatively new sid (installed on new > hardware, opportunity to get rid of some junk) and I have never needed > to mess about with X. > > > > 2. It is unlikely, but it might be that some of the xinput related > > programs or libraries have been corrupted. It might help to reinstall > > them. > > I have nothing in the apt cache, so I'll need to locate debs. I > eventually gave up and copied out the (possibly) offending upgrade log > and added newlines so it was actually readable. What jumped out then > were three xserver packages (from a total of 118). I located previous > versions in the cache, installed them, rebooted and confirmed they were > now running, and... just the same. My only remaining idea is that packages have been corrupted during download. This is not likely but can have multiple root causes. I do not know if apt or dpkg check the integrity of the packages before installation. I also do not know by heart how to check them manually. If this does not help I am running out of ideas. I do not think that it is a hardware issue because Knoppix works. I do not think that it is a general issue of sid because then the same issue would have been seen by other users. It should be related to "something" on your machine. > > > > 3. The comparison of Xorg.log of Debian and Knoppix may give some > > indication. > > They look broadly similar, although it is easy to miss things among > that much output. I wish you will find the issue. In case I will have new ideas or so I will chime in again. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Mouse trouble on sid
Am Tue, May 16, 2023 at 11:02:50AM +0100 schrieb Joe: Hello Joe, [...deleted a lot...] > On Tue, 16 May 2023 10:44:03 +0100 > Joe wrote: > > > > One idea is to try a minimalistic window manager as twm to find out > > > if the issue is related to xfce. > > > > OK, tried twm and fvvm. Both unusable, as a left-click brings up a > > menu for a fraction of a second. Couldn't log out of either, had to > > switch to console and uninstall them. But they confirm the mouse > > problem. It's obviously fairly fundamental. > > > > Just tried previous kernel, but also bad. I can assume by now that > > nobody else has seen this problem. > > Just as a sanity check, I booted Knoppix, and of course there's no > problem, it's just an order of magnitude too slow from USB to do > anything useful. Now it seems as if the issue is related to X or the driver stuff. I have three ideas. 1. Do you have any xorg.conf things in /etc or the related directories? Nowadays X is not so bad in guessing the hardware which makes xorg.conf and such obsolete. If there are X config files it might be worth to move them to a safe place and to try without them. 2. It is unlikely, but it might be that some of the xinput related programs or libraries have been corrupted. It might help to reinstall them. 3. The comparison of Xorg.log of Debian and Knoppix may give some indication. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Mouse trouble on sid
Am Mon, May 15, 2023 at 08:57:38PM +0100 schrieb Joe: Hello Joe, > On Mon, 15 May 2023 19:35:23 + > "Andrew M.A. Cater" wrote: > > > On Mon, May 15, 2023 at 08:15:42PM +0100, Joe wrote: > > > On Mon, 15 May 2023 13:26:06 -0500 > > > Kent West wrote: > > > > > > > On 5/15/23 11:57, Joe wrote: > > > > > Hi, > > > > > > > > > > > > > Then go from there. > > > > > > > Not much to go on so far. Thanks for your suggestions. This looks > > > like a bug in an upgrade, but I can't see evidence of anyone else > > > seeing it. > > > > > > This is the real problem with running sid: not that things break, > > > but that they only break for me. > > > > > > > If you run sid, you are absolutely expected to be able to resolve any > > problems you encounter. If it breaks, you get to keep both pieces. > > That's the contract with sid, more than with the other tranches of > > Debian (which comes with no overall warranty). > > > > If you want increased stability and less shiny new stuff, you run > > stable or, if you feel able to help debug and develop it, testing. > > > > Them's the breaks: and, as ever, DontBreakDebian by mixing different > > suites. > > > > Yes, I know all that, I've been running sid since sarge was stable, and > only had to reinstall twice in that time. One idea is to try a minimalistic window manager as twm to find out if the issue is related to xfce. The second idea could be to run apt-get autoremove - but I am not sure if this is a good idea for a non standard Debian installation. For the standard installations it is recommended to get rid of outdated libraries. But since you seem to be a long time Debian user I do not tell you anything new. > It's just the problems I get don't seem to happen to anyone else. But > then I suppose, like Land Rovers, there's no two identical sid > installations anywhere. I like that image. Land Rovers are the world best car for their purpose! They are legends forever. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: How to run a command / script on startup automatically in linux?
Am Mon, May 15, 2023 at 10:44:37PM +0530 schrieb Susmita/Rajib: Hello Rajib, > My dear illustrious List members and leaders of the Debian-users group: > I used the contents in the following webpages: > https://www.tutorialspoint.com/run-a-script-on-startup-in-linux > https://www.baeldung.com/linux/run-command-start-up > > I saved a file at "/etc/systemd/system/" named "rc-local.service" with > the following lines: > > [Unit] > Description=/etc/rc.local Compatibility > ConditionPathExists=/etc/rc.local > Description=Screensaver > > [Service] > Type=forking > ExecStart=/etc/rc.local start > TimeoutSec=0 > StandardOutput=tty > RemainAfterExit=yes > SysVStartPriority=99 > ExecStart=mousepad > Restart=always > User=root > Group=root > Type=simple > > [Install] > WantedBy=multi-user.target > > > I also added the line in the file /etc/rc.local: > mousepad > > But the program doesn't launch at startup. Where I am going wrong? > Does it fail to start because the command is run before the GUI starts > up? > > I don't want to use cron by editing crontab -e. I tried @reboot > mousepad, but doesn't work. > > Please advise. Have you already enabled your script with the systemd command? This is from the first link you have provided: Enable the service by running the following command "sudo systemctl enable yourscriptname.service" Start the service by running the following command "sudo systemctl start yourscriptname.service" If the service enabled and started please check the output of systemctl --failed. The command systemctl status yourscriptname.service should give information even if the service is running. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Wi-Fi broken on Dell E6520, Intel Centrino Advanced-N 6205 AGN, Debian 11.7 Xfce
Am Thu, May 04, 2023 at 01:14:12PM -0700 schrieb David Christensen: Hello David, [...] > Ethernet and Wi-Fi have both worked in the past; both separately and > simultaneously. > > > After failing to start Wi-Fi three times, I see: > > 2023-05-04 12:37:39 root@laalaa ~ > # dmesg | grep -i wifi > [ 79.953085] Intel(R) Wireless WiFi driver for Linux > [ 79.953314] iwlwifi :03:00.0: can't disable ASPM; OS doesn't have > ASPM control > [ 79.960679] iwlwifi :03:00.0: firmware: direct-loading firmware > iwlwifi-6000g2a-6.ucode > [ 79.960863] iwlwifi :03:00.0: loaded firmware version 18.168.6.1 > 6000g2a-6.ucode op_mode iwldvm > [ 79.960889] iwlwifi :03:00.0: firmware: failed to load > iwl-debug-yoyo.bin (-2) I see the same message with a different Intel chip, too. And I also seen docs which state that this is ok. > [ 80.057548] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUG disabled > [ 80.057551] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled > [ 80.057552] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled > [ 80.057553] iwlwifi :03:00.0: Detected Intel(R) Centrino(R) > Advanced-N 6205 AGN, REV=0xB0 > [ 80.070510] iwlwifi :03:00.0: reporting RF_KILL (radio disabled) > [ 80.070571] iwlwifi :03:00.0: RF_KILL bit toggled to disable radio. > [ 80.095718] iwlwifi :03:00.0 wlp3s0: renamed from wlan0 > > Comments or suggestions for gathering information and/or getting Wi-Fi > working? In the past I have had regular issues due to my fat fingers which touched the Wi-Fi off button on my keyboard. At that time I have not noticed that the issue has been me :-). There is a directory /var/lib/systemd/rfkill/ which holds a file named by the Wi-Fi device. Here it is pci-:04:00.0:wlan. The content is just a 0 for normal operation or 1 for Wi-Fi off which means RF_Kill. Please check that file on your system and replace a possible 1 by a 0. There might be a better method involving systemd to achieve the same. But I am not aware of that. There is also a configuration bit whether to enable Wi-Fi after reboot or to keep the previous setting. But I do not remember the details right now. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]
Am Tue, Apr 25, 2023 at 07:07:07AM -0400 schrieb Greg Wooledge: Hello Greg, > On Tue, Apr 25, 2023 at 12:39:45AM -0700, dmacdoug wrote: > > There are a large number of ways to read messages from the list. I happen > > to use Mutt and so I see a list of senders, subject lines, etc. Once I > > highlight a certain line and hit enter, I see the message, and 99% of the > > time I read a coherent message or question, but occasionally it I might read > > something like "i always use stable, Thanks!" and I wonder what that means. > > The subject line is now buried among about 8 or 10 header lines at the top > > and I need to search through them if, per chance, the real question might be > > there. > > Yes, this is exactly my experience also. Mutt has a "thread view" > screen, and a "message view" screen. The "thread view" screen shows > you the sender, date, and Subject (truncated). Once you select the > first unread message from the "thread view" screen, you go into the > "message view" screen, where you see a selected subset of the headers, > and then the body. You might or might not remember the Subject that > was shown on the previous screen. You might or might not pay attention > to the Subject header among all the other headers that are shown. Yes, I think in http://www.mutt.org/doc/manual/#concept-screens-and-menus the "thread view" is called "index" and the "message view" is called "pager". Your naming is more clear :-). > > But then the interesting bit happens once you've read that first message. > When you mark it for deletion, you immediately move to the next message. > You DON'T go back to the "thread view" screen. You just see the next > message, and you can read that and mark it for deletion, and then you see > the third message, and so on. Yes, this is annoying. There are two things to countermeasure that by configuration in the users muttrc file. 1. Do not hide the "thread view" when being in the "message view". set pager_index_lines=6 On your installation it seems to be 0. In the example you will see five lines of the "thread view" plus a header line. On my installation the tiny "thread view" appears on top of the bigger "message view". 2. Include the Subject in the output of the shown message You can include or ignore fields of the header to the information shown at the top of the message. Example lines are below. ignore Content-Type User-Agent X-Mailer unignore From Subject Message-Id May be the suggestions are useful. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: is nft running? how do I get info?
Am Tue, Apr 25, 2023 at 07:58:56AM + schrieb Bonno Bloksma: Hi Bonno, > Hi Anssi, > > >> There is nothing in the journal about nft > >> linbookwormtest:~#journalctl -t nft -- Journal begins at Mon > >> 2023-03-27 13:07:50 CEST, ends at Mon 2023-04-24 12:18:07 CEST. > >> -- -- No entries -- > > > Debian's nftables package includes a systemd service to run > > nftables. You might want to run systemctl status nftables first > > and then enable and to start the service. > Unfortunately nft is not a service. Trying the service command with > nft gives an error. linbookwormtest:~# service nft status Unit > nft.service could not be found. linbookwormtest:~# The service is named nftables. This is the name which must be applied to enable the service and for digging in the logs. nft is used to manage the filter. Please see https://www.debian.org/doc/manuals/debian-handbook/sect.firewall-packet-filtering.en.html Just as a reference the output from my system: # systemctl status nftables ● nftables.service - nftables Loaded: loaded (/lib/systemd/system/nftables.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2023-04-25 10:28:37 CEST; 26min ago Docs: man:nft(8) http://wiki.nftables.org Process: 226 ExecStart=/usr/sbin/nft -f /etc/nftables.conf (code=exited, status=0/SUCCESS) Main PID: 226 (code=exited, status=0/SUCCESS) CPU: 11ms Apr 25 10:28:37 lenovo systemd[1]: Finished nftables. Warning: journal has been rotated since unit was started, output may be incomplete. > Also trying command completion with the nft, or even nf, show no > results. Using just the n for completion gives just the networking > service. > > > I wonder how you used iptables? I always used a script for that > > but I had to run it too for changes... > I allways had a script too. I had it hooked in > /etc/network/interfaces via either a pre-up or post-up rule > depending if there was a fixed ip or a dhcp line in the interfaces > file. > > A default Debian install has an executable /etc/nftables.conf file. This configuration is started by systemd with nft -f /etc/nftables.conf. The default file does no filtering at all. > If nothing is looking at that file then what is the "normal" wat to > start the firewall? Do I hook it up via one of the old /etc/init.d/ > scripts? Do I create a script in one of the /etc/rc?.d/ directories? > I am pretty sure they don't expect every novice to start writing > systemd service files? I don't even know where they are, I never > touch them, too much can go wrong by not understanding how it all > connects. If I install dhcp it comes with default config files. If > I change them then THAT config gets loaded. > > If Debian does NOTHING with that nft config file then why is it > there? Is this a bug? Please enable the firewall by # systemctl enable nftables.service. Then it should work. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: how to change default nameserver?
Am Sun, Apr 09, 2023 at 04:20:49PM +0800 schrieb cor...@free.fr:
> greetings,
>
> I know I can edit the entries in /etc/resolv.conf, but it will be
> overwritten by DHCP server.
> I searched the internet and got one of the answers:
>
> apt install resolvconf
> echo "nameserver 127.0.0.1" >> /etc/resolvconf/resolv.conf.d/head
>
> what's the difference for /etc/resolv.conf and the method above?
There is a thrid method I use. I have add the following lines to
/etc/dhcp/dhclient.conf:
interface "bond0" {
supersede domain-name-servers 127.0.0.1;
}
My interface is bond0. Yours might be different.
Kind regards,
Christoph
--
Ist die Katze gesund
schmeckt sie dem Hund.
Re: Bullseye and hplip install
Am Wed, Apr 05, 2023 at 07:07:28AM -0600 schrieb Tjm: Hi Tony, I have deleted things below because my answer is related to the block below. > Christoph, thanks for the reply. Autoremove was run successfully. The > bullseye version was installed with no errors but wouldn't run. I tried > several other versions from the repository, both debian and generic versions > each built with different configs. No luck. The very latest hplip version > added to the repo this week doesn't give the 'wrong debian version' notice > during the configuration and compiles and installs with no errors but still > won't run. I'll try again using the static lib configs. I was thinking > maybe a QT3/4/5 issue but the hp utilities won't run in non gui mode either. > If I uninstall the bullseye version and just reinstall it I'll get different > errors for missing files that don't exist in the bullseye repos. I suspect > there's something that prevents those missing files from being configured and > compiled by the installer. Lastly, I installed the bullseye hplip version to > a clean bullseye installation and it still didn't work for me. > I have run hp-check just for curiosity. It reports a lot of missing stuff. For me it is ok because I do not really need hplip. Does hp-check runs on your system? May be it gives some useful debug information. If not I am running out of ideas. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Bullseye and hplip install
Am Tue, Apr 04, 2023 at 05:08:29PM -0600 schrieb tony mollica: Hi Tony, > Here's the deal! I've upgraded from buster to bullseye with no real issues, > overall, with the exception of only one app so far. hplip didn't run after > the upgrade and I've uninstalled and re-installed hplip from the bullseye > repo and it does install but doesn't work. No warnings on the install but > it won't run from the gui and launching from a terminal gives numerous > errors. I won't post those yet but a couple questions to start: > Has anyone installed hplip successfully and had it run properly? and > > Other than a normal install, what did you do to get it up and running? > > On my system, CUPS printing works perfectly and I also have python 2 and 3 > installed but configured to use python3, 3.9 to be exact. It appears that > hplip is centered around python2.x and it's possible this is the problem. I have installed Bullseye a few month ago together with cups and hplip. Python2.x is not present on my system. > Any info would be appreciated. I only use hplip to clean the printheads and > to check the ink levels. Did you run apt-get autoremove? This could clean up the system and helps to remove outdated stuff. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: auto restarting in crontab
Am Thu, Mar 16, 2023 at 07:27:22AM -0400 schrieb Greg Wooledge: > On Thu, Mar 16, 2023 at 12:24:10PM +0100, Christoph Brinkhaus wrote: > > The environments of login shells and crontab can be different. This > > includes the path where to seek executables. Therefore it is good > > practice not to write just the name of the executable as nc but the > > name with the path as /usr/bin/nc. Here I took nc as an example. > > It's better to set the PATH variable to whatever you need it to be. > Then you don't have to hard-code the execution path of every single > command in the script. (Which means your script breaks when you move > it to a system where nc is in /bin instead of /usr/bin, and so on.) > I think you are right. The only remaining argument for specifying the complete path I have read about is as below. There might be the situation with different binaries but similar names. For example /usr/bin/nc is different to /bin/nc. But such a system should be a nightmare and I doubt if you can find such an installation in the wild. I have a few scripts which should run at Linux and FreeBSD. In the past I have used uname to distinguish the platforms. This works but it is bulky and ugly. Things will be fine if I concat the PATH required for both systems and follow your advise. Thank you and kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: auto restarting in crontab
Am Thu, Mar 16, 2023 at 08:55:54AM +0800 schrieb cor...@free.fr: > Greetings, > > My script for monitoring Node.js app as follows. I put it in crontab for > auto-check and restart if failure. > > #!/bin/bash > > # scan the port > nc -z 127.0.0.1 3000 > > if [ $? -eq 0 ];then > exit > else > killall node > sleep 1 > nohup serve -s /home/myUsername/workspace/xxx-frontend/build & > fi > > > I can run the script by manual, but in crontab it won't work. that means, > when node.js dies, it will not get restarted by this script automatically. > The environments of login shells and crontab can be different. This includes the path where to seek executables. Therefore it is good practice not to write just the name of the executable as nc but the name with the path as /usr/bin/nc. Here I took nc as an example. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: question about rc.local
Am Fri, Mar 10, 2023 at 04:29:34PM +0100 schrieb Vincent Lefevre: Bonjour Vincent, > On 2023-03-10 09:58:55 -0500, Greg Wooledge wrote: > > On Fri, Mar 10, 2023 at 04:55:03PM +0200, Anssi Saari wrote: > > > Nicolas George writes: [snip - almost everything] > > The man pages are most likely from upstream, and don't include the > > changes provided by Debian (in debian.conf). > > It would be useful to have the man page patched (as sometimes done), > otherwise the user could be surprised. I assume you read the man pages in French language? I have observed a lag between the English man pages and the localised ones. To compare just read for example man LANG=en interfaces May be you know that already :-) Then forget the post. It has been a surprise for me. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: how to activate my wireless card? nmtui only shows wireless connections . . .
Am Fri, Mar 03, 2023 at 05:01:49PM + schrieb Albretch Mueller: > On 3/3/23, Timothy M Butterworth wrote: > > Just run `ip link` or `ip address` and it will show you the name. In addition what Tim suggests: You could run dmesg and search for ath, wifi, wlan, wlp or so. In my case the output with a different driver is as below. # dmesg|grep iwlwifi [2.635994] iwlwifi :04:00.0: enabling device ( -> 0002) [2.648283] iwlwifi :04:00.0: firmware: direct-loading firmware iwlwifi-8265-36.ucode [2.649024] iwlwifi :04:00.0: loaded firmware version 36.ad812ee0.0 8265-36.ucode op_mode iwlmvm [2.649050] iwlwifi :04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [2.802163] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 [2.862957] iwlwifi :04:00.0: base HW address: 00:e1:8c:eb:ce:bd [3.048206] iwlwifi :04:00.0 wlp4s0: renamed from wlan0 Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')
Am Fri, Mar 03, 2023 at 10:09:42PM +0700 schrieb Max Nikulin: > On 02/03/2023 22:27, Christoph Brinkhaus wrote: > > Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin: > > > On 28/02/2023 17:25, Christoph Brinkhaus wrote: > > > > I will just inform about the status. Everything is fine now. A word > > > > about systemd-networkd-wait-online: With this service running there > > > > has been even a delay of 1-2 seconds when switching from one console > > > > to a different one (the consoles when X is not running). I have no > > > > idea about that side effect. > > > Does it happen each time or it is getty startup time? In the latter case > > > you > > > may try (for various console numbers) > > > > > > systemd-analyze critical-chaingetty@tty1.service > > > > > It is happening each time when changing the console. I just remember that systemd-networkd-wait-online has been introduced just by the unbound fix as proposed in https://github.com/NLnetLabs/unbound/issues/773. I do now know about any systemd service which make use of that. But the certainly is at least one. > I have no idea which way it may be related to network configuration in > general and to 169.254.x.y link local addresses in particular. It is better > to start a new thread. > > - Does journalctl -f show some messages during such delay? > - Do you mean that each of [Ctrl+Alt+F3], [Ctrl+Alt+F4], [Ctrl+Alt+F3] hit > in sequence cause delay? Here it is [Alt+F1], [ALT+F2]. CTRL is just required when coming from a X11 screen. But even without X11 this delay happened without any indication in the log files. > - Policy Kit may need to adjust permissions to some devices (video, audio, > etc.), but 2 seconds is unreasonably long delay. I agree, especially when the trigger as switching the console is totally unrelated. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')
Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin: > On 28/02/2023 17:25, Christoph Brinkhaus wrote: > > I will just inform about the status. Everything is fine now. A word > > about systemd-networkd-wait-online: With this service running there > > has been even a delay of 1-2 seconds when switching from one console > > to a different one (the consoles when X is not running). I have no > > idea about that side effect. > > Does it happen each time or it is getty startup time? In the latter case you > may try (for various console numbers) > > systemd-analyze critical-chain getty@tty1.service > It is happening each time when changing the console. > > Now I have disabled systemd-networkd-wait-online and I have add a > > comment in the last line of > > /usr/lib/systemd/system//systemd-networkd.service > > which is now > > # 28.2.2023 Also=systemd-networkd-wait-online.service > > Ideally the root cause of strange behavior should be debugged. Perhaps some > dependency should be removed from e.g. multi-user.target or > network-online.target. Probably "systemd-analyze critical-chain" may give > some hints. Ok, it is no problem to include the service again. It is just strange that it is not referenced anywhere. But I will try systemd-analyze. I have not been aware about such a tool before. But it should be worth to learn how to use it. Thank you for the information! > > Any case I would not touch files in /usr/lib/systemd. It should confuse > tools like systemd-delta. It is possible to override specific properties by > creating of drop-in snippets in > /etc/systemd/system/systemd-networkd.service.d/. See systemd.unit(5), e.g. > run > >systemctl edit systemd-networkd.service > > [Install] > # Clear > Also= > # Add other values from the original file > Also=systemd-networkd.socket > > Check result > >systemd-analyze verify systemd-networkd.service > > I hope, it is a better way to apply your workaround. I can not suggest a > better solution for tty delay issue, but I think it exists. "Also=" should > affect "systemctl enable systemd-networkd.service" and "disable" commands, > so I puzzled why it helps at all. I will try that, too. I have /etc under version control using git. That makes it easy to get informed about changes. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')
Am Sun, Feb 26, 2023 at 01:21:07PM -0600 schrieb David Wright: Hello David and Max, > On Sun 26 Feb 2023 at 19:08:01 (+0100), Christoph Brinkhaus wrote: > > Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > > > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > > > Now there are no messages reported by journald as above. [snip] > > I have tried that and found the next issue. > > systemd-networkd-wait-online runs into a time out after the default > > timeout of 2 minutes. [snip] > A couple of pages I turned up were: > > https://systemd.io/NETWORK_ONLINE/ > https://github.com/NLnetLabs/unbound/issues/773 I will just inform about the status. Everything is fine now. A word about systemd-networkd-wait-online: With this service running there has been even a delay of 1-2 seconds when switching from one console to a different one (the consoles when X is not running). I have no idea about that side effect. Now I have disabled systemd-networkd-wait-online and I have add a comment in the last line of /usr/lib/systemd/system//systemd-networkd.service which is now # 28.2.2023 Also=systemd-networkd-wait-online.service The network works as desired and the strange delay when switching the console is history as well. Thank you both for all the support, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')
Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > Now there are no messages reported by journald as above. > > I am curious if fixing unbound and so network-online.target helped to avoid > 169.254.x.y address in your case. Can fetchmail work without a kludge you > added to achieve some delay? My expectation is that unbound.service may be > dropped from Requires= and After= in fetchmail.service, but both fields > should have network-online.target. > > I forgot that debugging of such issues should be started with "systemctl > --failed". I have tried that and found the next issue. systemd-networkd-wait-online runs into a time out after the default timeout of 2 minutes. # systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2023-02-26 17:10:28 CET; 1h 47min ago Docs: man:systemd-networkd-wait-online.service(8) Process: 472 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE) Main PID: 472 (code=exited, status=1/FAILURE) CPU: 25ms Feb 26 17:08:28 lenovo systemd[1]: Starting Wait for Network to be Configured... Feb 26 17:10:28 lenovo systemd-networkd-wait-online[472]: Event loop failed: Connection timed out Feb 26 17:10:28 lenovo systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Feb 26 17:10:28 lenovo systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Feb 26 17:10:28 lenovo systemd[1]: Failed to start Wait for Network to be Configured. Strange, I will have a look. But I think further discussion would exceed the topic of the thread. I will have to read a lot of man pages the next days. You have helped my already a lot :-), thanks for that kind support! Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')
Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > Now there are no messages reported by journald as above. > > I am curious if fixing unbound and so network-online.target helped to avoid > 169.254.x.y address in your case. I am not sure because I have disabled/deinstalled stuff which triggered the assignment of the 149.254.x.y address. > Can fetchmail work without a kludge you > added to achieve some delay? My expectation is that unbound.service may be > dropped from Requires= and After= in fetchmail.service, but both fields > should have network-online.target. You are right, there is no need anymore to check if the mail server can be resolved before starting fetchmail. Nevertheless I still have the unbound.service and the opensmtpd.service in the Requires= and After= sections. The reason is that incoming mails are routed via opensmtpd because fetchmail runs as an unprivileged user. Additionally the setup is indemendent of the mail server. Then the mails are sorted by maildrop. As far as I remember forwarding the mails from an unprivileged fetchmail to maildrop running as my user did not work. Now incoming mails appear in /var/log/mail.log, too which is also nice. > I forgot that debugging of such issues should be started with "systemctl > --failed". I have still a lot to learn. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Fri, Feb 24, 2023 at 07:41:26PM +0100 schrieb Christoph Brinkhaus: I reply to myself thanking Max. > Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin: > > On 22/02/2023 23:45, Christoph Brinkhaus wrote: > > > Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin: > > > > On 22/02/2023 01:26, Christoph Brinkhaus wrote: [snip] > > I have no experience with unbound and I am not sure at which moment it > > notifies systemd that the service is ready. However I have found a recent > > bug > > https://github.com/NLnetLabs/unbound/issues/773 > > "When used with systemd-networkd, unbound does not start until > > systemd-networkd-wait-online.service times out" > > > > Perhaps the package in Debian has an older version of the unbound.service > > file and so is not affected. > > > Hi Max, > > I have observed lines below in journald: > > Feb 22 15:41:44 lenovo systemd[1]: Reached target Network is Online. > Feb 22 15:41:44 lenovo systemd[1]: Failed to start Wait for Network to be > Configured. > Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: > Failed with result 'exit-code'. > Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: Main > process exited, code=exited, status=1/FAILURE > Feb 22 15:41:44 lenovo systemd-networkd-wait-online[362]: Event loop failed: > Connection timed out > Feb 22 15:41:25 lenovo systemd[1]: anacron.service: Succeeded. > Feb 22 15:41:25 lenovo anacron[3261]: Normal exit (0 jobs run) > Feb 22 15:41:25 lenovo anacron[3261]: Anacron 2.3 started on 2023-02-22 > Feb 22 15:41:25 lenovo systemd[1]: Started Run anacron jobs. > > This looks related, thank you very much! > I will have a look at the link. Dear Max, the method descriped in the link above helped to fix the issue. Now there are no messages reported by journald as above. Thank you very much for the kind help! [snip] Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin: > On 22/02/2023 23:45, Christoph Brinkhaus wrote: > > Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin: > > > On 22/02/2023 01:26, Christoph Brinkhaus wrote: > > > > [Unit] > > > > Description=A remote mail retrieval and forwarding utility > > > > After=network-online.target opensmtpd.service unbound.service > > > > Requires=opensmtpd.service unbound.service > ... > > In case of my fetchmail setup the culprit is unbound. At the startup > > of unbound it takes some time to exchange keys and so on. > > I have no experience with unbound and I am not sure at which moment it > notifies systemd that the service is ready. However I have found a recent > bug > https://github.com/NLnetLabs/unbound/issues/773 > "When used with systemd-networkd, unbound does not start until > systemd-networkd-wait-online.service times out" > > Perhaps the package in Debian has an older version of the unbound.service > file and so is not affected. > Hi Max, I have observed lines below in journald: Feb 22 15:41:44 lenovo systemd[1]: Reached target Network is Online. Feb 22 15:41:44 lenovo systemd[1]: Failed to start Wait for Network to be Configured. Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Feb 22 15:41:44 lenovo systemd-networkd-wait-online[362]: Event loop failed: Connection timed out Feb 22 15:41:25 lenovo systemd[1]: anacron.service: Succeeded. Feb 22 15:41:25 lenovo anacron[3261]: Normal exit (0 jobs run) Feb 22 15:41:25 lenovo anacron[3261]: Anacron 2.3 started on 2023-02-22 Feb 22 15:41:25 lenovo systemd[1]: Started Run anacron jobs. This looks related, thank you very much! I will have a look at the link. > ... > > > However avahi-autoipd should be started concurrently > > > with network configuration to assign link-local address in the case of > > > failure. > > > > In a different thread - it was about IPv6 which has mutated > > slightly - several users claimed that the avahi-autoip is useful for > > their business. > > I mean IPv4 link local addresses 169.254.x.y. My impression is that > avahi-autoipd was created for the cases when there is no point to setup > centralized DHCP server. On the other hand I agree that a router (and so > DHCP out of the box) is more wide spread configuration than connecting a > couple of devices directly or through a switch. I think so, too. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable
Am Wed, Feb 22, 2023 at 06:12:29PM +0100 schrieb daven...@tuxfamily.org:
>
> = context =
> For the context, I use a Debian 11 laptop for work. When I work remotely
> from home, I have to use a cisco VPN. Good thing is there is openconnect,
> which does work, and in teh case of ym work's VPN, it does wor. cisco's
> spyware/downloaded binry, namely using the --csd-wrapper
> /usr/libexec/openconnect/"
[snip]
> = end of context =
> What I want is: setting up /etc/resolv.conf ONLY
> - at system startup/initial network connexion.
> - when openconnect is executed and connects to work's VPN
> - when openconnect is ^C-ed and disconnects from the works VPN (cleaning
> it's mess in the routing table, interfaces, /etc/resolv's and other netwwork
> stuff it might have modified, makes sense)
>
> Here's what I know:
> - Whatever process does that seems does what I highly suspect to be DHCP [1]
> requests every now and then. Home's router answers giving it's own address
> as both gateway and DNS resolver. And said process thinks it's OK to delete
> and recreate resolv.conf with the wrong content… breaking everything work's
> related while the VPN is still active
If it is DHCP: You might do a countermeasure in
/etc/dhcp/dhclient.conf. On my system I have an entry as below.
interface "wlp4s0" {
supersede domain-name-servers 127.0.0.1;
}
I run unbound as a resolver. The entry in dhcclient.conf prevents that
the entry in /etc/resolv.conf is overwritten.
[snip]
My setup is stoneage like compared to your context.
Anyhow, I hope this is at least useful as a pointer :-).
Kind regards,
Christoph
--
Ist die Katze gesund
schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin: > On 22/02/2023 01:26, Christoph Brinkhaus wrote: > > > > I have no idea if it is possible to estimate a DHCP response > > > > time. > > Since static IP address is assigned, it does not matter. I expected DHCP > configuration and that delay may be noticed in `journalctl -b 0` logs. > > > [Unit] > > Description=A remote mail retrieval and forwarding utility > > After=network-online.target opensmtpd.service unbound.service > > Requires=opensmtpd.service unbound.service > > > > But fetchmail starts before the dependencies have been finished. > > I can not say that I fully understand interaction of After and > Requires/Wants options. I would try additional Wants=network-online.target As far as I remeber correctly I have tried the Wants option without success. In case of my fetchmail setup the culprit is unbound. At the startup of unbound it takes some time to exchange keys and so on. During that period names cannot be resolved. Now I call fetchmail after the mailserver name can be resolved to an IP. This is done in a tiny wrapper script. It keeps the log files clean. That workaround is fine for me. > > [Match] > > Name=w* > > > > [Network] > > DHCP=no > > Address=192.168.0.62/24 > > Gateway=192.168.0.32 > > DNS=127.0.0.1 > > There are options like RequiredForOnline, see systemd.network(5), but likely > default value is yes. However avahi-autoipd should be started concurrently > with network configuration to assign link-local address in the case of > failure. In a different thread - it was about IPv6 which has mutated slightly - several users claimed that the avahi-autoip is useful for their business. I am only a hobbyist, I trust the guys who do IT in their regular job. May be it is ok as it is implemented in Debian. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Tue, Feb 21, 2023 at 01:06:01PM -0500 schrieb Jeffrey Walton: > On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus > wrote: > > Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin: > > > On 20/02/2023 21:44, Christoph Brinkhaus wrote: > > > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max > > > > Perhaps to > > > > get rid of 169.254.x.y addresses, it is enough to properly > > > > > configure network interface, either to ensure that DHCP server is > > > > > available > > > > > or to assign a static address. After that you may forget about > > > > > existence of > > > > > avahi-autoipd. > > > > > > > > On my system it did not help. One "issue" might be, that systemd > > > > starts services in some sequence. But it does not wait for a service > > > > to complete. At least in case of stuff I have observed on my system. > > > > > > Out of curiosity, is link-local IP address assigned during boot or later > > > when e.g. WiFi connection is temporary lost? How long does it take to get > > > response from DHCP server? Which way network is configured (ifupdown, > > > NetworkManager, systemd-networkd) in your case? > > > > The 169.254.x.y has been assigned during boot. I have not used DHCP. > > The configuration has been static. The ping to the router takes about > > 4ms. I have no idea if it is possible to estimate a DHCP response > > time. The network has been configured via systemd-networking. > > You have to supply a static ip address or a DHCP server. This is correct. > > Since you supplied a static ip address, then the fact that you are > getting an APIPA is a bug. You should file a bug report with the > package (Avahi? Systemd?) that is providing the APIPA. I assume that there might be a timing issue with systemd-networking. A comparable happened with fetchmail started by systemd. The head of the description is [Unit] Description=A remote mail retrieval and forwarding utility After=network-online.target opensmtpd.service unbound.service Requires=opensmtpd.service unbound.service But fetchmail starts before the dependencies have been finished. I am not sure if systemd monitors the services to finish or if it just starts them in a specific order. > But backing up... I suspect there's something wrong with your static > ip address assignment. The address is already taken, the netmask is > wrong, or the gateway is wrong. > > Looking back through this thread, I did not see where you showed your > static ip configuration. Maybe you should start with that. If it is > bad, then the APIPA is just a symptom of the [static ip address] > problem. This is the systemd-networkd configuration: [Match] Name=w* [Network] DHCP=no Address=192.168.0.62/24 Gateway=192.168.0.32 DNS=127.0.0.1 I have unbound as a DNS listening at localhost. But with DNS=192.168.0.32 the behaviour has been similar. I have not yet checked the address assignment using systemd-networkd. For doing so I have to reinstall some packages. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin: > On 20/02/2023 21:44, Christoph Brinkhaus wrote: > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin: Hello Max, > > > Perhaps to get rid of 169.254.x.y addresses, it is enough to properly > > > configure network interface, either to ensure that DHCP server is > > > available > > > or to assign a static address. After that you may forget about existence > > > of > > > avahi-autoipd. > > > > On my system it did not help. One "issue" might be, that systemd > > starts services in some sequence. But it does not wait for a service > > to complete. At least in case of stuff I have observed on my system. > > Out of curiosity, is link-local IP address assigned during boot or later > when e.g. WiFi connection is temporary lost? How long does it take to get > response from DHCP server? Which way network is configured (ifupdown, > NetworkManager, systemd-networkd) in your case? The 169.254.x.y has been assigned during boot. I have not used DHCP. The configuration has been static. The ping to the router takes about 4ms. I have no idea if it is possible to estimate a DHCP response time. The network has been configured via systemd-networking. In the current setup I have removed a lot of packages I did not make use of. Additionally I have switched to systemd-networkd. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin: Hi Max, > On 19/02/2023 23:35, Christoph Brinkhaus wrote: > > Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers: > > > Having installed package openvswitch-switch and doing `ip route` I do get > > >169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004 > > > > Please have a look at https://wiki.debian.org/Avahi. [deleted 20 lines] > Perhaps to get rid of 169.254.x.y addresses, it is enough to properly > configure network interface, either to ensure that DHCP server is available > or to assign a static address. After that you may forget about existence of > avahi-autoipd. On my system it did not help. One "issue" might be, that systemd starts services in some sequence. But it does not wait for a service to complete. At least in case of stuff I have observed on my system. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Sun, Feb 19, 2023 at 07:57:56PM +0100 schrieb Geert Stappers: Hi Geert, > On Sun, Feb 19, 2023 at 12:21:36PM -0500, Stefan Monnier wrote: > > >> Having installed package openvswitch-switch and doing `ip route` I do get > > >> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004 > > >> > > >> What can be done to prevent that "zeroconf" > > >> configures interface `ovs-system`? Deleted almost everything. > > But Avahi provides more functionality (e.g. mdns) than merely > > configuring network interfaces, > > so disabling it altogether may be undesired. > > Yes, may. And by disabling it I will find out what I miss :-) > Disabling avahi did not prevent route set on device ovs-system. > My guess is that other compoments ( network-manager, systemd-networkd ) > are involved. This is quite likely. I have disabled and deleted a low of stuff to keep the installation as lean as possible. But I have started with xfce to see if Debian works on my laptop and switched to awesome later. Therefore a lot of tools are not required anymore compared to a more complex desktop environment. I hope that users chime in with experience on systemd and its toolchain. Kind regards to the lovely Netherlands, Christoph All the rest deleted. -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers: Hello Geert, > Having installed package openvswitch-switch and doing `ip route` I do get > 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004 > > What can be done to prevent that "zeroconf" > configures interface `ovs-system`? Please have a look at https://wiki.debian.org/Avahi. According to the section "Disabling avahi-daemon" the following commands should work: For permenant disablement (surviving a machine reboot): systemctl mask avahi-daemon.service avahi-daemon.socket systemctl disable avahi-daemon.service avahi-daemon.socket systemctl stop avahi-daemon.service avahi-daemon.socket On my system I have deinstalled the avahi stuff before testing the commands. I have found the link for searching infos for the thread "ipv6 may be has arrived". Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: ipv6 maybe has arrived.
Am Tue, Feb 14, 2023 at 01:41:41PM -0500 schrieb gene heskett: Hello Gene and Dave,, > On 2/14/23 10:49, David Wright wrote: > > Wisely done: we don't need it twice … and logs can be lengthy. [...] > Alright guys, I may have an existing system here that shows a 169, but not > as default. Running Armbian bullseye AND xfce4, in fact I have 2 of them > that show an ip r of: > > gene@bpi54:~$ ip r > > default via 192.168.71.1 dev eth0 proto static metric 100 > 169.254.0.0/16 dev eth0 scope link metric 1000 > 192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12 metric > 100 > > Probably have 4 of them, but only two are powered ATM, and the other is busy > running klipper and a 3d printer. > And networking is running fine on all 4 despite its being present as it is > not the default. And all are using xfce4, because the gnome screen blanker > is an instant crash and burn, requiring a power down reset to recover from. > The xfce4 blanker Just Works. > > The reason you've never seen any logs etc is that if its the default. there > is no way in hell to get you those logs or other info because there is no > network to get it to you. We could take screen pix, but my camera makes 5 > meg jpegs the server won't take. > > So maybe we can figure out whats different about Armbian that makes it work. > Give me some troubleshooting commands to see if we can figure out whats > different about armbian that makes it work when there's no way in hell to > make it work with a debian install of bullseye and going clear back at least > to stretch, maybe further? Except nuking avahi and rebooting. > > Maybe this is your chance to come up with a fix that doesn't get us a > sermon, questioning our intelligence for doing it. I am not sure about difference between Armbian and Debian. But I have found https://wiki.debian.org/Avahi with lots of information. There is a section for what Avahi is intended, about temporary disabling and permanent disabling. Disabling can be done without deleting files or packages. I think we can rely on this documentation. There should be no need for me to reproduce that by installing xfce4. [...] I did not meant to be offensive. Please excuse me if this was your impression. English is not my first language. > Take care & stay well, everybody. My best wishes for you as well, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: ipv6 maybe has arrived.
Am Tue, Feb 14, 2023 at 09:48:11AM -0600 schrieb David Wright: Hello David, > On Mon 13 Feb 2023 at 11:39:31 (+0100), Christoph Brinkhaus wrote: > > Am Sat, Feb 11, 2023 at 09:29:16PM -0600 schrieb David Wright: > > > On Fri 10 Feb 2023 at 06:40:42 (+0100), to...@tuxteam.de wrote: > > > > On Thu, Feb 09, 2023 at 03:32:46PM -0500, gene heskett wrote: > > > > > On 2/9/23 07:53, to...@tuxteam.de wrote: > > > > > > On Thu, Feb 09, 2023 at 07:32:18AM -0500, Greg Wooledge wrote: > > > > > > > > > > > > [...] > > > > > > > > > > > > > (I have no idea what mdns4_minimal is, but Debian put it there, > > > > > > > and it > > > > > > > hasn't caused a problem yet so I left it alone.) > > > > > > > > > > > > This is a zeroconf thingy. My box hasn't that, because I banned > > > > > > Avahi > > > > > > and its ilk long ago. > > > > > > > > > > > > Just out of curiosity: does your box have one of those funny > > > > > > link-local > > > > > > IPv4 169.254.xxx.yyy addresses? > > > > [deleted almost everything] > > Wisely done: we don't need it twice … and logs can be lengthy. > > > I have seen the 169.254.xxx.yyy on my system, too. > > It is a Debian Bullseye. To check if Debian works on this hardware I > > have simply select the xfce4 option in the installer. Either the avahi > > stuff or xfce4 triggered the setup of the 169.254.xxx.yyy adress. > > Disabling the start of the avahi-daemon did not change the situation. > > Deinstall of avahi-daemon did not help, too. > > > > Today I have deleted almost everything of avahi and xfce4. After a > > reboot the 169.254.xxx.yyy is no more configured. > > Yes, and that's a problem for anyone trying to replicate the > configuration of these addresses: we usually never see files > and logs from offending systems, but just reports of package > deletion or, even less helpful, so-called nuking of random files. Ok, this is true. Fortunately I have a git repository of /etc. The diff is as below: X11/Xsession.d/55xfce4-session (gone) alternatives/lightdm-greeter (gone) alternatives/x-session-manager (gone) alternatives/x-session-manager.1.gz (gone) alternatives/x-terminal-emulator alternatives/x-terminal-emulator.1.gz avahi/avahi-autoipd.action (gone) avahi/avahi-daemon.conf (gone) avahi/hosts (gone) dbus-1/system.d/avahi-dbus.conf (gone) default/avahi-daemon (gone) dhcp/dhclient-enter-hooks.d/avahi-autoipd (gone) .../dhclient-exit-hooks.d/zzz_avahi-autoipd (gone) group group- gshadow gshadow- init.d/avahi-daemon (gone) ipp-usb/ipp-usb.conf (gone) ld.so.cache mailcap network/if-down.d/avahi-autoipd (gone) network/if-up.d/avahi-autoipd (gone) nsswitch.conf passwd passwd- rc0.d/K01avahi-daemon (gone) rc1.d/K01avahi-daemon (gone) rc2.d/K01avahi-daemon (gone) rc3.d/K01avahi-daemon (gone) rc4.d/K01avahi-daemon (gone) rc5.d/K01avahi-daemon (gone) rc6.d/K01avahi-daemon (gone) shadow shadow- xdg/autostart/xscreensaver.desktop (gone) xdg/xfce4/Xft.xrdb (gone) .../xfce-perchannel-xml/xfce4-session.xml (gone) xdg/xfce4/xinitrc (gone) xfce4/defaults.list (gone) 40 files changed, 6 insertions(+), 841 deletions(-) May be this gives some information. If not I can reproduce the issue and provide logs as required. Now there is no 169.254.xxx.yyy in any file of /etc. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: ipv6 maybe has arrived.
Am Sat, Feb 11, 2023 at 09:29:16PM -0600 schrieb David Wright: Hi David, please excuse the late reply. I have had a side discussion with Tomas in German about the issue I observed, too. > On Fri 10 Feb 2023 at 06:40:42 (+0100), to...@tuxteam.de wrote: > > On Thu, Feb 09, 2023 at 03:32:46PM -0500, gene heskett wrote: > > > On 2/9/23 07:53, to...@tuxteam.de wrote: > > > > On Thu, Feb 09, 2023 at 07:32:18AM -0500, Greg Wooledge wrote: > > > > > > > > [...] > > > > > > > > > (I have no idea what mdns4_minimal is, but Debian put it there, and it > > > > > hasn't caused a problem yet so I left it alone.) > > > > > > > > This is a zeroconf thingy. My box hasn't that, because I banned Avahi > > > > and its ilk long ago. > > > > > > > > Just out of curiosity: does your box have one of those funny link-local > > > > IPv4 169.254.xxx.yyy addresses? [deleted almost everything] I have seen the 169.254.xxx.yyy on my system, too. It is a Debian Bullseye. To check if Debian works on this hardware I have simply select the xfce4 option in the installer. Either the avahi stuff or xfce4 triggered the setup of the 169.254.xxx.yyy adress. Disabling the start of the avahi-daemon did not change the situation. Deinstall of avahi-daemon did not help, too. Today I have deleted almost everything of avahi and xfce4. After a reboot the 169.254.xxx.yyy is no more configured. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Postfix fails after upgrade from bullseye to bookworm
Am Fri, Jan 20, 2023 at 08:28:10PM +0100 schrieb Sven Joachim: > On 2023-01-20 13:39 -0500, Greg Wooledge wrote: > > > On Fri, Jan 20, 2023 at 07:17:37PM +0100, Sven Joachim wrote: Hello Community, > >> It seems that postfix's startup time has greatly regressed, on my laptop > >> there are very long delays both at boot: > >> > >> , > >> | $ systemd-analyze blame | head -n1 > >> | 33.340s postfix@-.service > >> ` > > > > A delay that's a multiple of 30 seconds is very often a DNS lookup > > failure. I would imagine your postfix configuration is trying to > > perform a DNS lookup on some hostname or other, and that this is > > happening before you're actually "online", for whatever definition of > > "online" is relevant here. > > That should be NetworkManager-wait-online.service. In the logs I see > that systemd starts the postfix service directly after reaching > network-online.target, as it is supposed to do. The mystery is why it > takes another 30+ seconds before any messages from postfix itself appear > in the logs. > > > That's a total guess, though. Find your logfiles and read them to see > > what's actually going on. > > Here is what I see in the journal when I restart postfix.service: > > , > | Jan 20 20:16:06 myhost postfix/postfix-script[1470]: stopping the Postfix > mail system > | Jan 20 20:16:06 myhost postfix/master[1307]: terminating on signal 15 > | Jan 20 20:16:06 myhost systemd[1]: postfix@-.service: Deactivated > successfully. > | Jan 20 20:16:06 myhost systemd[1]: Stopped Postfix Mail Transport Agent > (instance -). > | Jan 20 20:16:06 myhost systemd[1]: postfix@-.service: Consumed 36.372s CPU > time. > | Jan 20 20:16:06 myhost systemd[1]: Starting Postfix Mail Transport Agent > (instance -)... > | Jan 20 20:16:41 myhost postfix[1800]: Postfix is using backwards-compatible > default settings > | Jan 20 20:16:41 myhost postfix[1800]: See > http://www.postfix.org/COMPATIBILITY_README.html for details > | Jan 20 20:16:41 myhost postfix[1800]: To disable backwards compatibility > use "postconf compatibility_level=3.6" and "pos\ > | tfix reload" > | Jan 20 20:16:42 myhost postfix/postfix-script[2026]: starting the Postfix > mail system > | Jan 20 20:16:42 myhost postfix/master[2028]: daemon started -- version > 3.7.3, configuration /etc/postfix > | Jan 20 20:16:42 myhost systemd[1]: Started Postfix Mail Transport Agent > (instance -). > | Jan 20 20:16:42 myhost systemd[1]: Starting Postfix Mail Transport Agent... > | Jan 20 20:16:42 myhost systemd[1]: Finished Postfix Mail Transport Agent. > ` I have observed something comparable, but with fetchmail for email and unbound as a dns resover. Both are started by systemd at almost the same time. But it takes some time for unbound to fetch keys and so on. Before unbound is really ready fetchmail has started its first poll, but without success because the mail servers ip could not be resolved. I am only a hobbyist. But may be something similar is happening in the discussed issue. May be it is worth to have a look how the dns lookup is set up and how it is starting. Please just ignore be if this proposal makes no sense. At work I am no admin :-). > I have left nothing out, so WTH is postfix waiting for in these 35 > seconds? > > Cheers, >Sven BTW: I have resolved my issue by starting fetchmail via systemd by a wrapper script which probes the dns resolution of the mail server before starting fetchmail. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: OpenSolaris Boot Environements equivalent
Am Fri, Jan 20, 2023 at 02:16:57PM +0100 schrieb Mario Marietto: Hi Mario, > I still do not understand why,when I remove files on a ZFS disk using > commands like (rm and rm -r),the left space does not increase,but it > decreases. I would like to know what I can do to free some space if > removing files does not work. If you have snapshots in a data set and rm files they still can be accessed in the hidden .zfs directories. Therefore the free space should remain almost the same until you delete the snapshos. > And I don't understand why a ZFS disk goes > fast out of space. This does not happen with an UFS disk. I have not observed that on my systems, but I have not stressed them a lot. > From what I've > understood every snapshot created with the ZFS mechanisms contains a full > FreeBSD system. Am I right ? Do you confirm this ? If this is true,ZFS is > too much space consuming and it will explain why the space will end very > fast on the disk. That's not good for sure. A snapshot contains the references to files. Beside of management overhead a snapshot does not consume any space. If you modify or delete files on the data set where the snapshot has been taken off the original files at the time of the snapshot claim their required space in the snapshots hidden directory instead of the original data set. > Recently I've found a Linux > distro called "NixOS" which uses another method to create snapshots. It is > based on a large use of sim/soft and hard links to backup different > versions of the system libraries. This method is useful when the system is > upgraded. I would like to ask you if you would like to see this kind of > solution also on FreeBSD. I really want to see the zfs boot menu suggested > by Anssi on FreeBSD ! I like it very much ! Do you think it is hard to > implement it there ? That sounds a little bit like the software "time machine". Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: OpenSolaris Boot Environements equivalent
Am Thu, Jan 19, 2023 at 12:18:53PM +0100 schrieb Yassine Chaouche: Hello Yassine, > Hello all, > > I was wondering if there was anyone working on an equivalent of OpenSolaris > BE? > Basically, > It automatically creates ZFS snapshots of the whole system each time you do a > system upgrade. > Next time you boot, > you'll have the choice of running the new system > or the old one. > Pretty handy to roll back in case anything goes wrong during the system > update. That sounds that you are familiar with FreeBSD. I am not familiar with ZFS on Linux but more or less to ZFS on FreeBSD. > > If nothing like it is avaiable for linux, > what would be the necessary steps to achieve something similar? > (even manually) Searching for Vermadens docs about boot environments I have stumped over the link below. https://ramsdenj.com/2020/03/18/zectl-zfs-boot-environment-manager-for-linux.html I am not sure if this is useful for production. But it is at least a pointer. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: reportbug: don't know: bug in apt [list] or in grep
Am Thu, Jan 19, 2023 at 11:40:50AM +0100 schrieb to...@tuxteam.de: Hello Tomas, > On Thu, Jan 19, 2023 at 11:31:23AM +0100, Christoph Brinkhaus wrote: > > Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de: > > > > Hello Julian, > > > > > Hello together, > > > listing packages in apt with ”sudo“ in the title returns different output > > > (bash commands at the end of the email). I would fill a bug report, but > > > I'm not sure whether to address it to grep or apt. How do you see this? > > > > > > Kind regards > > > Julian Schreck > > > -- > > > $ apt list sudo* vs. $ apt list | grep "^sudo[a-z-]" > > > $ apt list *sudo vs. $ apt list | grep "[a-z-]sudo/" > > > $ apt list *sudo* vs. $ apt list | grep "sudo" > > > > It seems to be more a shell topic or how man 7 glob is handled. > > Please try the first patterns with "" signs as > > apt-list "sudo*" instead of apt-list sudo* and so on. > > It made the difference for me using the fish shell. > > Doing "apt list sudo*" without any quoting is asking for trouble anyway, > regardless of the shell you use. Yes, quoting is the correct term. And it is of superior improtance, especially if the input is not perdefined in terms of the structure. E.g. existance of special signs as the asterisk *, white spaces and so on. > > What the command apt will ultimately see will depend on what files are > in your current directory. For curiosity If have done a small test as below. Unfortunately there are a few outputs in German. For this comparisons the exact meanings of the German text has no importance at all. 1. The first command of the original poster: chris@lenovo ~> apt list sudo* fish: No matches for wildcard 'sudo*'. See `help expand`. apt list sudo* ^ 2. Create an empty file to see the effect: chris@lenovo ~> touch sudo 3. The first command of the original poster: chris@lenovo ~> apt list sudo* Auflistung… Fertig sudo/stable-security,now 1.9.5p2-3+deb11u1 amd64 [Installiert,automatisch] N: Es gibt 1 zusätzliche Version. Bitte verwenden Sie die Option »-a«, um sie anzuzeigen. 4. Run apt list sudo The result is the same as 3. 5. Delete the original empty file and create a modified one: mv sudo sudolala 6. The first command of the original poster: chris@lenovo ~> apt list sudo* Auflistung… Fertig There is no sudolala. > Don't do that. It will drive you crazy. Sure. Thanks for triggering me to do the small tests. I did not want to hijack the thread. But I think it makes sense to show the effect of missing quoting. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: reportbug: don't know: bug in apt [list] or in grep
Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de: Hello Julian, > Hello together, > listing packages in apt with ”sudo“ in the title returns different output > (bash commands at the end of the email). I would fill a bug report, but I'm > not sure whether to address it to grep or apt. How do you see this? > > Kind regards > Julian Schreck > -- > $ apt list sudo* vs. $ apt list | grep "^sudo[a-z-]" > $ apt list *sudo vs. $ apt list | grep "[a-z-]sudo/" > $ apt list *sudo* vs. $ apt list | grep "sudo" It seems to be more a shell topic or how man 7 glob is handled. Please try the first patterns with "" signs as apt-list "sudo*" instead of apt-list sudo* and so on. It made the difference for me using the fish shell. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Missing links of libraries (*.so) on Debian 11
Am Mon, Jan 16, 2023 at 08:28:59PM +0800 schrieb Ruiyang Peng: > On 2023/1/16 18:33, Avtansh Gupta wrote: > > Hello All, Hello, > > I recently noticed that some of the library soft links on my Debian 11 > > system are missing which were there in the previous versions. I have a > > program loading one of these shared objects dynamically but is > > failing as it is unable to locate the file. > > > > */usr/lib/x86_64-linux-gnu/libaudit.so* > > > > This is the missing .so file in debian11. This file was present on the > > previous versions of Debian and other Linux distros as well. > > > > A similar pattern is observed with the other files(*.so) in the same > > folder. > > > > Could someone let me know what the change is and what is the new > > convention being used? > > -- > > *Regards,* > > > > *Avtansh Gupta* > > *+91 8743068185* > What about trying pkg-config? Maybe it can tell you where it is. Please excuse the late reply, I think I have missed the first post(s). apt-cache search libaudit|grep ^libaudit libaudit-common - Dynamische Bibliothek für Sicherheitsprüfungen - gemeinsame Dateien libaudit1 - Dynamische Bibliothek für Sicherheitsprüfungen libaudit-dev - Header files and static library for security auditing I guess you have to install some or all of the packages. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: no sound after installing pulseaudio
Am Fri, Dec 23, 2022 at 06:08:01PM +0800 schrieb lou: > Thank Jude and Christoph! Hi Lou. > i run "pactl list": > > Connection failure: Connection refused > pa_context_connect() failed: Connection refused I have no idea why the message comes from but also how pulseaudio communicates with the rest of the system. Please check if pulseaudio is really running by checking with ps. If the communication is running via dbus check if dbus is running. If the communication is via TCP or UPD and localhost please check if there is no firewall rule which blocks the traffic. > but in stretch, pulseaudio works after i install it For me its has been working using Bullseye out fo the box, too. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: no sound after installing pulseaudio
Am Fri, Dec 23, 2022 at 09:12:28AM +0800 schrieb lou: Hello Lou, > i am running buster and install pulseaudio > to let pulseaudio take effect i have to reboot > but there's no sound though pavucontrol seems ok > (pavucontrol shows sound is playing properly) > to get sound back, i have to remove pulseaudio and reboot With "pactl list" or "pcctl list short" you can identify some cryptic address of your sound card. With something as (taken from my system) "pactl set-sink-volume alsa_output.pci-_00_14.2.analog-stereo +2%" you can adjust the volume. Or you simple try alsamixer which comes with some ncurses looking GUI. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Wifi won't work under debian 11.6, please heeeeelp😣
Am Wed, Dec 21, 2022 at 04:01:25PM +0100 schrieb hede: Hi Mansour, > Am 21.12.2022 15:19, schrieb Mansour zermello: > > I have the model: Intel AX201NGW and downloaded the files from the > > official website of Intel, i extracted the folder in /Downloads, then > > i copied all the files into /lib/firmware but still not work. > > I do also have a device with Intel AX201 and for me it was sufficient to > install the firmware-iwlwifi package. You might want to enable the non-free packages as below. ~$ grep non /etc/apt/sources.list|sort deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free deb http://ftp.de.debian.org/debian/ bullseye-updates main contrib non-free deb http://security.debian.org/debian-security bullseye-security main contrib non-free deb-src http://ftp.de.debian.org/debian/ bullseye main contrib non-free deb-src http://ftp.de.debian.org/debian/ bullseye-updates main contrib non-free deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free The Intel drivers are in the non-free packages. BTW: I am not sure if the deb-src are really necessary. I have taken the default sources.list and added the non-free stuff as above. If things work it might be better do delete the stuff which you have copied from elsewhere. > What's the output of the following command? > > dmesg | grep iwlwifi > > regards > hede Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: nftables transparent proxy for outbound connections on a server
Am Sun, Dec 11, 2022 at 06:27:53AM + schrieb Andre Rodier:
> Good morning, all.
Good Morning Andre,
>
> Is there anyone around to help me to setup a transparent proxy on Debian,
> please ?
>
> I have tinyproxy running on my server, and I would like, with nftables,
> to intercept any outbound web traffic (tcp ipv4.ipv6),
> and to redirect to the proxy on 127.0.0.1:.
>
> So far, I have seen these examples online:
>
> > ...
> > chain prerouting {
> > type nat hook prerouting priority dstnat; policy accept;
> > tcp dport { 80, 443 } counter dnat ip to 127.0.0.1:
> > tcp dport { 80, 443 } counter dnat ip6 to [::1]:
> > }
> > ...
>
> Or sometimes, I see using redirect or even tproxy
If you want to interecpt encrypted traffic it might be helpful to
study how privoxy is doing that. In the past privoxy has been fine for
filtering http traffic. Nowadays it is extended to https, too. It
needs a self certified key stuff. I have not tried it so far, but it
does decryption of the incomming traffic for filtering and it does
encryption of the filtered traffic to the browser side.
>
> What is the best nftables approach, please ?
>
> Can you copy and paste what you are using ?
Unfortunately I have no idea about that approaches.
Kind regards,
Christoph
Re: hard disk and sub flash disk issues
Am Thu, Dec 08, 2022 at 04:38:55PM +0300 schrieb Semih Ozlem: Hello Semith, I have deleted (i), (ii) and (iv) because I can not contribute to that questions. Please tell me if this is not ok in this mailing list. > (iii) I have an external hard drive seagate that appears in lsusb command > but the disk does not mount or appear under blkid or lsblk even with sudo. > Can I recover that device external hard disk I have also an external hard drive which behaves similar. It is an Intenso "something" with 250 GB or 500 GB. The external disk works well if connected by a cheap USB hub with an external 5V supply. This is not mch feedback but I hope it helps. Kind regards, Christoph
Re: else or Debian (Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?))
Am Thu, Nov 10, 2022 at 04:46:12AM +0100 schrieb hw: > On Wed, 2022-11-09 at 18:26 +0100, Christoph Brinkhaus wrote: > > Am Wed, Nov 09, 2022 at 06:11:34PM +0100 schrieb hw: > > [...] > > > FreeBSD has ZFS but can't even configure the disk controllers, so that > > > won't > > > work. > > > > If I understand you right you mean RAID controllers? > > yes > > > According to my knowledge ZFS should be used without any RAID > > controllers. Disks or better partions are fine. > > I know, but it's what I have. JBOD controllers are difficult to find. And it > doesn't really matter because I can configure each disk as a single disk --- > still RAID though. It may even be an advantage because the controllers have > 1GB > cache each and the computers CPU doesn't need to do command queuing. > > And I've been reading that when using ZFS, you shouldn't make volumes with > more > than 8 disks. That's very inconvenient. > > Why would partitions be better than the block device itself? They're like an > additional layer and what could be faster and easier than directly using the > block devices? Using the block device is no issue until you have a mirror or so. In case of a mirror ZFS will use the capacity of the smallest drive. I have read that a for example 100GB disk might be slightly larger then 100GB. When you want to replace a 100GB disk with a spare one which is less larger than the original one the pool will not fit on the disk and the replacement fails. With partitions you can specify the space. It does not hurt if there are a few MB unallocated. But then the partitions of the diks have exactly the same size. Kind regards, Christoph
Re: else or Debian (Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?))
Am Wed, Nov 09, 2022 at 06:11:34PM +0100 schrieb hw: Hi hw, > On Wed, 2022-11-09 at 14:29 +0100, didier gaumet wrote: > > Le 09/11/2022 à 12:41, hw a écrit : > > [...] > > > In any case, I'm currently tending to think that putting FreeBSD with ZFS > > > on > > > my > > > server might be the best option. But then, apparently I won't be able to > > > configure the controller cards, so that won't really work. And ZFS with > > > Linux > > > isn't so great because it keeps fuse in between. > > > > I am really not so well aware of ZFS state but my impression was that: > > - FUSE implementation of ZoL (ZFS on Linux) is deprecated and that, > > Ubuntu excepted (classic module?), ZFS is now integrated by a DKMS module > > Hm that could be. Debian doesn't seem to have it as a module. > > > - *BSDs integrate directly ZFS because there are no licences conflicts > > - *BSDs nowadays have departed from old ZFS code and use the same source > > code stack as Linux (OpenZFS) > > - Linux distros don't directly integrate ZFS because they generally > > consider there are licences conflicts. The notable exception being > > Ubuntu that considers that after legal review the situation is clear and > > there is no licence conflicts. > > Well, I'm not touching Ubuntu. I want to get away from Fedora because of > their > hostility and that includes Centos since that has become a derivative of it. > FreeBSD has ZFS but can't even configure the disk controllers, so that won't > work. If I understand you right you mean RAID controllers? According to my knowledge ZFS should be used without any RAID controllers. Disks or better partions are fine. > I don't want to go with Gentoo because updating is a nightmare to the > point where you suddenly find yourself unable to update at all because they > broke something. Arch is apparently for machosists, and I don't want > derivatives, especially not Ubuntu, and that leaves only Debian. I don't want > Debian either because when they introduced their brokenarch, they managed to > make it so that NVIDIA drivers didn't work anymore with no fix in sight and > broke other stuff as well, and you can't let your users down like that. But > what's the alternative? > > However, Debian has apparently bad ZFS support (apparently still only Gentoo > actually supports it), so I'd go with btrfs. I have no knowledge about the status of ZFS on Linux distributions, just about FreeBSD. > Now that's gona suck because I'd > have to use mdadm to create a RAID5 (or use the hardware RAID but that isn't > fun > after I've seen the hardware RAID refusing to rebuild a volume after a failed > disk was replaced) and put btrfs on that because btrfs doesn't even support > RAID5. > > Or what else? > Kind regards, Christoph
