Re: Firefox complaint
Am Freitag, 4. Oktober 2024, 14:24:47 CEST schrieb Mindaugas: > Hello. > > https://www.bobevans.com/ Looks like this site is blocked. Tested with Firefox-esr, Opera, Chromium and Konqueror - all same results (Access denied). I am using OpenDNS as DNS. Best Hans
Re: Reading an old HDD
Am Freitag, 4. Oktober 2024, 04:57:19 CEST schrieb Will Mengarini: > I have a freshly installed Debian stable and I'm trying to read an > HDD from a previous machine. I put it into a disk enclosure that > connects to the new machine by USB and powered everything up, but the > stable Debian doesn't see the new disk that is connected by USB. Is > there some driver or package that I need to install to make this work? You say, it is connected by USB. You then should see the device with the command lsusb when the usb-connector is plugged in. However, I have to precice it: You see the controller of the case, you put your HDD in, not the hdd itself! But, if you can see it, first step is done. For further examinations I suggest, to do the following commmand as root tail -f /var/log/syslog in console and then watch its output by pluggin in and pluggin off the usb- case with the built in hdd. It should be detected. If you still can not see the reason, I suggest, for copying the old date using a livefile system like Knoppix, Debian-Live, Kali-Linux, TRK or whatever. With those you might also be able, to check, if you can mount the usb-device at all. If this fails, it looks just like your usb-case is incompatrible, try another one if available. There are some USB3 cases, which can not well switch to USB2-mode. I suppose, it is an IDE-drive, and your controller of the mainboard does have no more IDE-port, does it? For more hints, i need more information., but that is, what comes in my mind at the moment. Hope, it helps though. Best regards and good luck! Hans
Re: [SOLVED] Re: How add key of 3rd party repo?
Hi David, this is a very good and value hint! What you are telling is very reasonable and makes fully sense. Yes, in the past I olayed aroud mith umask, and it can really happen, that I messed up things by doing so. I will recheck my settings and if there are any missettings, of course correct them to debian's actual default settings. Besides, i am still concerned about the default umask settings, but this I already mentioned and will not be reopened again. Again: Thank you very much for pointing me to this! Made me happy! Best regards Hans > From the clues left dotted around, my bet is that you've messed up > your system with the way you become root, affecting its umask. > > A couple of months ago (and back in 2020), you were exhorting Debian > to set a mask for users of at least 027, and I'm wondering whether, > in your case, it might have been changed to 077 since around one of > those times. > > Back in 2014, you had the permissions on dpkg set to -rwxr-x---, > which would correspond to a umask of 027, so perhaps you had already > tightened your system from the Debian default, 022, to 027 by then. > > So it now comes down to why system components are getting the user's > umask applied to them. For that, I looked back to 2014 when you seemed > to be a bit more forthcoming with pasting prompts into your posts. > > Your first post in the thread¹ starts with: > | Ok, so let’s start as root: > | > | su -p > | root@protheus2:~# LANG=C mediathekview > > Well, three cases of su are: > > ~$ umask > 0027← the securer default was set for this user. > ~$ su > Password: > /home/auser# umask > 0022← correct > /home/auser# > exit > ~$ su - > Password: > ~# umask > 0022← correct > ~# > logout > ~$ su -p > Password: > ~# umask > 0027← wrong for root > ~# > exit > ~$ > > So I'm guessing that you've been installing things after having become > root with -p. I don't know whether APT and dpkg can themselves modify > any excessively restrictive umask, and I'm unwilling to test that here. > > ¹ https://lists.debian.org/debian-user/2014/07/msg00053.html > > Cheers, > David.
[SOLVED] Re: How add key of 3rd party repo?
> > curl -fsSL https://download.jitsi.org/jitsi-key.gpg.key | gpg -o > > /usr/share/keyrings/jitsy-key.gpg --dearmor > > No error messages! > > I notice that this is not the same filename as the one in the quote > further above. The original had 'jitsi-keyring.gpg', and this one has > 'jitsy-key.gpg' - that's two differences. > > (Also, this command line isn't 'including the prompt'.) > This might be an error by me, as there are several names in the different documentations. I rechecked and the names are identical. Maybe a typo here in this mail. > > > > And the entry in /etc/apt/sources.list.d/jitsi-stable.list is this: > > deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] > > https://download.jitsi.org stable > This is referencing the original filename, not the one you used in your > "no error messages" command. > Yes, this is the required entry of one of the documentations in the web. As I mentioned before: There are several different instructions, and they are different, as one is for Ubuntu, Ubuntu+Debian and Debian. > Does that file exist? If so, what contents does it have? Are they the > same as the one in the other filename? Yes, it does exist. > > > Should be all ok, but it isn't. > > If the file named in the sources.list entry doesn't exist (or has the > wrong contents), then I think that would explain it. Yes, you are correct, but I rechecked. There is "jitsi-keyring.gpg.key", which is from the original jitsi-site, and there is also "jitsi-key.gpg", which is from the jitsi-*keyring*.deb (on the original jitsi-meet website), which I testwise downloaded manually and installed using dpkg. At the moment, there is only one key existent: jitsi-keyring.gpg.key, which is acually resides in /usr/share/keyrings/. But I found the reason! The eys are set "rw- --- ---", so they could not read. This adds another problem: Looks like gpg or sq is setting wrong rights. Several minutes ago I discovered another issue: /usr/bin/dpkg was set to "rwx r-- r--", what is also wrong. As I did not change this, it must have been changed by some upgrade. Had this issue already in 2014 (with a mediathekview problem, same reason), I suppose, we can safely close this. Thanks for your help, again laerned something. Best regards Hans
Re: How add key of 3rd party repo?
Am Sonntag, 22. September 2024, 19:05:35 CEST schrieb Charles Curley: > On Sun, 22 Sep 2024 18:44:04 +0200 > > Hans wrote: > > I want to install jitsi-meet in Debian 12, but whatever I do, the > > system does not accept the key for the repo. > > > > There are several ways documented, but none of them is working. And > > some of them are mixed with Ubuntu. But Ubuntu is not debian! This is > > what I tried: > > > > 1. What the jitsi-site says: > > curl https://download.jitsi.org/jitsi-key.gpg.key | sudo sh -c 'gpg > > --dearmor > /usr/share/ keyrings/jitsi-keyring.gpg' > > When you do these things, *exactly* what results do you get? Copy and > paste the entire command line, including the prompt, the results, and > the next command line prompt. > > In the line above, is there a typo: should there be a space between > "/share/" and "keyrings"? This is an eample: curl -fsSL https://download.jitsi.org/jitsi-key.gpg.key | gpg -o /usr/share/keyrings/jitsy-key.gpg --de armor No error messages! Then LANG=C apt-get update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org/debian-security bookworm-security InRelease Hit:3 http://dl.winehq.org/wine-builds/debian bookworm InRelease Hit:4 http://downloads.metasploit.com/data/releases/metasploit-framework/apt lucid InRelease Hit:5 http://deb.debian.org/debian bookworm-updates InRelease Hit:6 http://download.opensuse.org/repositories/home:/cabelo/Debian_12 InRelease Hit:7 http://deb.debian.org/debian bookworm-backports InRelease Hit:8 https://linux.teamviewer.com/deb stable InRelease Hit:9 http://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.3:/stable/Debian_12 InRelease Hit:10 https://fasttrack.debian.net/debian-fasttrack bookworm-fasttrack InRelease Hit:11 https://updates.signal.org/desktop/apt xenial InRelease Hit:12 https://fasttrack.debian.net/debian-fasttrack bookworm-backports-staging InRelease Hit:13 https://deb.opera.com/opera-stable stable InRelease Get:14 https://download.jitsi.org stable/ InRelease [1682 B] Err:14 https://download.jitsi.org stable/ InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4D2D216F1FD7806 Output directory /var/lib/debtags/ does not exist Reading package lists... Done W: GPG error: https://download.jitsi.org stable/ InRelease: The following signatures couldn't be verified because the pub lic key is not available: NO_PUBKEY B4D2D216F1FD7806 E: The repository 'https://download.jitsi.org stable/ InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. No key recognized. And the entry in /etc/apt/sources.list.d/jitsi-stable.list is this: deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org stable Should be all ok, but it isn't. Best Hans
How add key of 3rd party repo?
Dear list, I want to install jitsi-meet in Debian 12, but whatever I do, the system does not accept the key for the repo. There are several ways documented, but none of them is working. And some of them are mixed with Ubuntu. But Ubuntu is not debian! This is what I tried: 1. What the jitsi-site says: curl https://download.jitsi.org/jitsi-key.gpg.key | sudo sh -c 'gpg --dearmor > /usr/share/ keyrings/jitsi-keyring.gpg' 2. What debian says: curl -fsSL https://download.jitsi.org/jitsi-key.gpg.key | sq -o /usr/share/keyrings/jitsy- key.gpg.key dearmor alternatively curl -fsSL https://download.jitsi.org/jitsi-key.gpg.key | gpg -o /usr/share/keyrings/jitsy-key.gpg --dearmor 3.What I also did: Copied the key to /usr/share/keyrings/ No success. Copied the key to /etc/apt/trusted.gpg.d/ No success. 4. Full of despair tried "apt-key add" - deprecated! No success. What did I wrong? I also downloaded the key from the repository with a browser and copied them (not using curl or wget in the commandline). No I am lost, as there are several ways told in th eweb, but mostly Ubuntu based and maybe not tested for debian. And: all are doing different! Did I miss something else? Sadly apt-key is gone Best Hans
Re: Lost internet access on Trixie this morning.
Am Montag, 16. September 2024, 19:59:44 CEST schrieb Frank McCormick: > I am faced with a strange problem. I have no internet access on Trixie > on one of two partitions on my ssd. > I was attempting to solve a problem I am having with Vivaldi by > installing Seahorse. Apt quit halfway through downloading the necessary > files complaining it could not resolve a bunch of Debian repositories. > Ever since that I have no internet access in Trixie. It's not a hardware > problem as I have full access on the other partition which runs Opensuse > Tumbleweed. Earlier today I did an update of Trixie and it went fine. > > Can someone help me diagnose the problem ? > > This is my apt sources list > > deb http://deb.debian.org/debian trixie main contrib non-free > non-free-firmware > deb-src http://deb.debian.org/debian trixie main contrib non-free > deb http://deb.debian.org/debian trixie-updates main contrib non-free > non-free-firmware > deb-src http://deb.debian.org/debian trixie-updates main contrib non-free > > deb http://deb.debian.org/debian trixie-backports main contrib non-free > non-free-firmware > deb-src http://deb.debian.org/debian trixie-backports main contrib non-free > deb http://deb.debian.org/debian trixie-proposed-updates > non-free-firmware main contrib non-free > > Thanks What does ifconfig -a (eecute as root) tell? Is it really enp0 or enp0s25? Second question: If you give the network interface a hard ip, does it work? In /etc/network/interfaces edit these lines like the example -- auto lo enp0s10 iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 iface enp0s10 inet static address 192.168.3.2 netmask 255.255.255.0 broadcast 192.168.178.255 gateway 192.168.3.2 Check the correct name of your ethernet device! See above. Also create (if not eistent) a file /etc/resolv.conf and enter DNS IPs like this example. # Generated by NetworkManager nameserver 208.67.222.222 nameserver 208.67.220.220 nameserver fd00::de39:6fff:fe2a:6101 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 2a02:560:58ad:b300:de39:6fff:fe2a:6101 --- PLEASE NOTE: This is only for testing purposes! If you are using networ-manager, it will wuse its own configuration files. If this above is working, check, what is the difference to networ-manager. If you now the ethernet device name (like enp0s10 in my eample), you can also try dhclient enp0s10 as root. Of course you have to use the name of your ethernet device. (Besides, these names are called "predicted names", but I think, you now this already). Good luck! Hans
Re: Circumventing keyboard problem on Lenovo R64
Hi Richard, exchanging the keyboard yourself might be not a great thing. If it is not an apple computer, where you have to strip the whole computer, most keyboards are very simple to echange. There are often some videos on youtube, which show, how to do it. On most, there are 1 - 3 screws to loosen, then (but not always), some clamps to press aside, and you can lift up the whole keyboard. On my Lenovo T520 (and I suppose most Lenovos are made like mine), you have to loosen 2 screws on the bottom, then push the whole keyboard into the mousepad direction, and then lift it up. Easy to do. If done, you can loosen the flat cable as usual and exchage the keyboard. It is just a hint, if you want to save money. The keyboards are all about 30 - 50 € (about 40 $) and the exchange by a commercial should not cost much. It is done within 10 minutes (maybe a few dollars more) Hope this helps! Best Hans
Re: Circumventing keyboard problem on Lenovo R64
> Didn't seem to work on 2 machines using different flavors of Debian. > Where is that documented so I can run a verifiable test? You are right. I rechecked this and it does not work correctly, because of a bug in KDE. The problem is, when starting another session, your former session is locking. But you can not unlock your session again, even with the correct password. I know about this for more than 3 years and reported the bug long time ago. It is still not fied, but this is not the point here. Apart from this, check it. I am running KDE (plasma) and you get the option "change user" from the K-menu. Do this, and you start with the windowmanager you preset in your favourite login manager (I am using lightdm, but sddm or gdm might work as well, too). When both windowmanagers are started, you can click every time to "change user" and then get the option, to chose, to which you want to switch. But as I said before: The former one has a locked screen and can not be unlocked. I suppose, this is a rights problem and the locking mechanism is set by root and rooit must unloc it. But as you want to unlock the screen as normal user, it will not work. Maybe sometimes this will be fixed. However, it does not harm the function of starting a second window managers for another user. If someone might also confirm of this little bug I mentioned here and knows better than me, he may just file a little bugreport to the developers of KDE. Maybe he also nows a little workaround??? Hope this helps and makes things clearer. Best regards Hans
Re: Circumventing keyboard problem on Lenovo R64
> Solves wrong problem ;} > I couldn't log in as "Richard" at power-up. > But Stefan hints at solution to that problem. Ah, ok, you are in X. Do you now, you can start a second windowmanager as root without logoff as the other user? If doing so, you can switch between both with "CTL + ALT + F7" (standard graphical terminalport in debian for first user) and "CTL + ALT + F8" (next graphical port for secon user). This might becoming handy, when often switch between root and normal user. Just an idea. Nice, that your problem is solved! Have a nice day! Hans
Re: Circumventing keyboard problem on Lenovo R64
I have a Lenovo T520. From time to time (but very seldom), the whole keyboard is no more working (just hangs). It is a problem with X, maybe related to the NVidia driver. In these rare cases I connect a wireless keyboard to the notebook (put the dongle into an usb port) and can go on on typing. Restarting X initilalises the inbuild keyboard again and then BOTH keyboards are working. The do not interfere. Same behaviour with a cabled usb-keyboard. Best Hans
Re: Circumventing keyboard problem on Lenovo R64
Hi Richard, Am Donnerstag, 12. September 2024, 13:43:49 CEST schrieb Richard Owlett: > I have a Lenovo R61 running 64 bit Buster. > It has a keyboard failure - the "h" key is intermittent and my primary > account is "Richard" ;/ > > I have no problem logging in as root. > > Two primary questions: > 1. is there someway that I can use a USB connected keyboard > as workaround while root? I am not sure, what you mean. If you connect an USB-keyboard into a notebook, then both should work. > 2. is there some way to switch from "root" to "Richard" without > having to type to the pop-up that shows when using > System->Logout... ? > You can login as Richard, then do "su -" and become root. After this, type "CTRL + d" and you are Richard again. In X (i.e. in konsole or term or any other terminal), started as normal user Richard, you can type "su -p", then start any graphical programm you nee fro this console. It will run with root rights. After it just close the terminal or type in "CTRL + d" and you arte back to Richard again. This is handy, when you need only few applications as root. For eample, when you need to edit a *.conf file as root and you might want edit with "kwrite" for eample. So you need not to logoff and logon as root, just do as described above: start terminal, su -p, start kwrite, CTL + d = finished. Does this help? > TIA Best Hans
Re: Just a simple question.
Am Mittwoch, 11. September 2024, 02:18:03 CEST schrieb Maureen L Thomas: > My old HP is not working right and it is very old. I am looking at > laser printers and have always favored HP. But, in saying that I am > open to any brand. I always get an all in one model since it does come > in handy. Any advice is welcome. Thanks in advance. > > Maureen Hi Maureen, I am great friend of "Brother" printers. They are cheap and reliable and they are well supported by linux. Brother is offering deb packages for installing or a linu script, which is downloading and installing these packages automatically. I also had some eperience with printers from Epson. They are also offering installation packages, but sometimes they are outdated. I believe, Epson is not so much intereested in customers using linux as Brother is. Before you buy: Be sure, the manufacturer is sopporting linux. Hope, this helps. Best Hans P.S. Oh, and before you buy, check and compare prices of printer cartridges, they often differ much.
Re: OT: Question to shell script
What I am exactly want to do: I have 5 live-build directories. In each I am starting my own script, which is setting variables and so on for the individual build and does some other things (rennamin and copying the resulted ISO and so on). As each build must be started within the live-build directory, I would have to wait, if the first build is ready, then cd into the net live-buil and so on, until all five are ready. This is lasting much too long, so I would like, to run all 5 scripts in parallel, and this should be started from a master script, which I can execute from anywhere, i.e. from the home of root or /usr/sbin. You certain have recognized: All these scripts must be run as root, but this is another case and does not matter here. If bash does not offer this option, I will find another way, but I hope, someone more experienced with shellscripts or bash might have a quick solution. If not, no problem, it does not harm anyone. Best Hans
OT: Question to shell script
Dear list, I am stuck with a little problem and know no one, whom I can ask. So I allow me to ask here. I have several directories, and in each directory there is a shell script, which MUST be started within and from its path. Now I want to edit a "master-shell-script", which I can start from anywhere and which shall start each single shellscripts simultaniously, but within its path. The structure looks like this: /directory-one/application_1/my-shell-1.sh /directory-two/application_2/my-shell-2.sh /directory-three/application_3/my-shell-3.sh Of course, I could mae my master-shell-script so, that I first go into the first one, execute, then cd to the second one, execute and last cd to the third one, execute, but I suppose, there is an easier way. Or does my idea not work at all? Thanks fo a short advice. Best Hans
Re: Usage: "debian ... amd64-netinst.iso"
> That sounds like really bad hardware. Mind to share manufacturer name > and model name ? > > (I have a 2 GB Intenso model "USB", a 4 GB SanDisk Cruzer, > a 8 GB Corsair Flash Voyager, and a 128 GB Intenso Ultra Line. > They all are more than 5 years old. I use them rarely, except for the > Corsair, which has a sturdy rubber coating and serves me as encrypted > pocket backup medium.) > > I believe, it is no problem to share with which usb-sticks I ran into the problem. The sticks are from Intenso. They are silver, and you can buy it in a double pack to a very cheap price here in Germany at a well known market place with a big "M" starting its name. At the moment I am using "SanDisk Ultra USB 3.0" with 64Gb and had no issues with these. These are black and made of plastic, shape is tapering to its end and you can push the contacts out of the case. At the moment I am testing a new one also from SanDisk. This is itsy bity tiny (only 3 cm long, 1cm wide and 3mm high) with 128GB. I am using it as my "prepared-for-the-issue"-stick. I am using YUMI on it (exFAT) and it has now 27 bootable livefilesystems on it (like KALI, GRML, DRBL-Live, clonezilla, TRK, UBCD4WIN, F4BCD usw. usw.). I think, you can imagine. Among these are also my own Version of KALI-Life (built with bootcdwrite, about 25GB) and bigger ones like security-onion (7GB) or TAILS (6,6GB) and smaller ones like Super-grub-disk, TRK, gparted-live and of course, Debian-Install-iso. Collection of proven software for many years. We will see, how well this stick does, as all of these images are regularly upgraded by me. Best Hans
Re: Usage: "debian ... amd64-netinst.iso"
> I've had some thumb drives die and that might be the cause. Have you noticed > any patterns? > > -- > Your pretended fear lest error might step in is like the man who > would keep all wine out of the country lest men should be drunk. >-- Oliver Cromwell No, nothing special. Some IO-errors and one does not boot any more (kernel crash, due to copy errors, but the ISO itself is ok. Working perfrectly on another stick and after several copies, this stick is booting, also. However, too unsecure for my productive systems). Best Hans
Re: Usage: "debian ... amd64-netinst.iso"
Hi Thomas, > That's the actual topic of that wiki page. > Just scroll up and read it from start. maybe I did not express myself well enough. What I meant is more a desciption, why xorriso-dd-target is better than dd or dcfldd. Just a little comparision, which advantages your way got or disadvantages compared to the other. This does not affect, that your wiki is detailed enough for everyone. Just a suggestion from me, what I personally would have expected to read. Please note I say "personally". :) > > > The debian manual suggests using the "dd" command and claims, not to use > > Rufus, as it might not work. > You got me! It was not Rufus, it was Unetbootin. I confused both. My fault. > > How often do you experience bad copy runs ? The last times I would say, every 2nd or 3rd run I got copy errors. Thisis because the stick itself. I had several from the same manufacturer, all failed after a while. Other sticks, older and other manufacturer, did not fail at all. All sticks were 16GB and newly bought. (say: about 1 year old) > > A good USB stick's firmware will care for wear leveling, so that > frequently overwritten logical blocks get written to different physical > blocks. > https://en.wikipedia.org/wiki/Wear_leveling No no, they are defective. Hardware issue in the bootloader. When reformatting to vfat, they are still working and (as far as I could ses) no errors. However, three of my five sticks are completly unusabla. One could no more be recognized, one only has 128MB writable, and the third one got randomly read/ write errors. Guess, the reformat is not intended for it. But this is crystal clear: usb-sticks are made for Windows, for Windows and only for Windows. Hey, are ther other OS in the world :) > > > Have a nice day :) > > Thomas Have fun! Hans
Re: Usage: "debian ... amd64-netinst.iso"
Am Montag, 2. September 2024, 13:01:43 CEST schrieb Thomas Schmitt: > Hi, > > i added a new section > https://wiki.debian.org/XorrisoDdTarget#How_to_verify_the_result > instead of a mere link because i deem the Debian instructions too > scattered for being suitable for already puzzled and stressed users. > > I would appreciate checkreading of this new section by interested > bystanders. > > > Have a nice day :) > > Thomas Hi Thomas, nice tutorial, you wrote, very impressiv! Maybe you might want to add a suggestion for readers, which might be the best way, to get an ISO to an usb-stick? The debian manual suggests using the "dd" command and claims, not to use Rufus, as it might not work. I myself made good eperiences with dcfldd instead of using dd. In my case i am creating an ISO-Livefile of a running system with bootcdwrite and then copy it to an usb-stick using dcfldd. As these are large files (greater than 25GB), the danger, something gets lost during copy, is high. And in the past, dd worked not as good as dcfldd. With dd I got more errors. I already mentioned: dcfldd is testing very copied segment with a hashsum, that is correct, which dd does not. As I am doing this builds regularly, I already did about 60-70 copies in the last, so I think, meanwhile I know, what I am talking about. A little side effect of this was, that some manufacturers obviously do not like ext2/3/4 format (to which the usb-stick were reformatted). After about 10th to 15th time of reformate, they died (memory segments got lost). Others I already during years are reformatted about 50 times or more and are still in best health. Anyway, just some ideas and maybe you or someone else finds it usefull. Best wishes Hans
Re: Laptop screen dim on battery power
Soe Windowmagaers got theire own powermanagement, i.e. KDE is susing powerdevil. Do not know, if its settings also effect the konsole without X. You could also check acpi settings, maybe you will find something there. Just an idea Best Hans
Re: Usage: "debian ... amd64-netinst.iso"
> So your command line would read … > > # … … > > Cheers, > David. I believe, instead of using dd for copying to the usb-stick, one might want to use dcfldd for it. dcfldd is en enhanced version of dd with hashsum check during copy. It was created for forensic matters, where no data may have gone lost. Best Hans
Re: printer paused: filter not avaiable
Hi, just an idea: take a look at /var/log/cups/errors.log. Had the same problem, here it was a missing lib. The log file might tell you more. Hope this helps. Best Hans
Which tool for upgrade in commandline?
Dear list, over the many years we got different tools for upgrading debian in the commandline. These tools behave differently and also we get different results, when eecuting. First, we have the oldest, whcih is apt-get. apt-get update, apt-get upgrade or apt-get full-upgrade does a good job. However, we also have aptitude, but aptitude update, aptitude upgrade and aptitude full-upgrade are doing also a good job, but not the same as apt-get does. Also it looks, aptitude update loads its own list and is not using the list from apt-get (otherwise it could not explain, why aptitude and apt-get every time reloads the new list, when one of the other was eecuted before). Also the dependencies in both tools are handled different. And at last, we have apt, which (as far as I now), soemtimes is calling apt- get, and sometimes is calling aptitude. This is somehow rather irritating! So, my question is: Which one is recommended, when updating and upgrading is used in a script, so that it causes as little as possible pain? It means: When the script is not eecuted daily, but let us say, every two weeks, and we have lots of packages. At the moment I am using aptitude, this works great in short periods, but after al longer time, it crashes, because some dependencies could not resolve. Independent of my personal use: Which one is recommended? Thanks for reading. Short answer will be ok. Best Hans
Re: Laptop keeps powering off
Am Samstag, 24. August 2024, 18:08:00 CEST schrieb Max Nikulin: > On 24/08/2024 05:11, Joe B wrote: > > i've been having an issue where my laptop powers off randomly when > > not connected to power. This has been happening since stable and > > currently i'm on unstable. I would like to use my laptop without > > power. Check temperature! If it shuts down due to overheating, check /var/log/syslog or /var/log/kern.log. There should be an entry for it. There are also tools, which check sensors and show its actual state. Look for gkrellm or others. Most problems with notebooks, is the air release ist often full of dust. Relating to the processor use, it may overheat or not. Check the air flow is good. Hope this helps. Best Hans
Re: nvidia package 340xx
Am Freitag, 23. August 2024, 15:55:40 CEST schrieb Richmond: > I tried something similar, but it didn't work, although... > > Hans writes: > > 1. Install module-assistant > > I didn't do this. > > > 2. Enter the line for sid into your /etc/apt/sources.list > > > > deb http://deb.debian.org/debian/[1] sid main contrib non-free > > non-free- firmware > > > > > > 3. apt update > > > > > > 4. apt install nvidia-legacy-340xx-driver firmware-misc-nonfree > > At this point many packages were installed, I didn't get a choice, I am > not sure why. > > Then system failed to boot X, so I scrapped it all. > > > My notebook is a Lenovo T520 with Intel CPU (and internal Intel GPU) > > and also NVidia GPU as external GPU (soldered on mainboard). > > I have a Dell Inspiron 1720. I may have another go in April. You need module-assistant for making sure, you got the kernel headers and compilers you need. Running module-assistant is the easiest way to make sure of it. I could write a new step-by-step procedure for bloddy noobs, but I am sure, I would annoying people with it. Most problem is, people are installing other packages as recommended, because they believe, there are dependencies. Apt does show them. So as I advices, just install only the packages from sid for nvidia, nothing else. If not sure, download them manually and install with dpkg. Just to explain: Enteringt sid into sources list and do an apt update will read the sourcs fropm list., then install only the two packages from sid (the needed dependencies from sid will be automatically installed). After this remove the entry of sid in sources.list and do an apt update again. This will remove all entries from the package list of sid in the cache of apt. Now you can eecute module-assistant and get the kernel headers and compilers for compiling of your runninjg debian/stable. As you have already downloaded the sources from sid, which has the higher version, these will be compiled. If it compiles correctly without any crashes, you are good. Compiling is the main point here. After compilation you must reboot, to unload nouveau driver an load kernel module 340x. To test, remove all login managers temporarly out of the way and in prompt do "startx". If X is now starting you are good, other wise you see, what fails. If you have two graphic cards (one in the CPU mostly Intel, and the other NVidia), you need to switch it using bumblebee and primusrun. If bumblebee and primusrun are installed, you need to reboot, to activate it. Then, when X is started, check it with "primusrun glxgears" in kconsole or xterm as normal user and see the output. Note: If X is NOT started, you may try with 390xx, even when nvidia-detect and also the NVidia website is telling, your chip is 340x. I have two graphic cards, which di NOT run with 340xx (as recommended) but perfectly with 390xx. Hope this helps. Last time I compiled the 390xx is about a month ago, so it maybe something has changed, I did not recheck in the last weeks! Best Hans
Re: nvidia package 340xx
> I should read my own posts. I have now installed Ubuntu 22 with Kernel > 5.4 and it is working with the above Nvidia card. But I have only kicked > the can down the road to April. I wonder if it will be possible to run > Debian 12 or 11 with a 5.4 kernel and nvidia-legacy-340xx-driver? Should work. I am running 6.9.7+bpo-amd64 with 340xx. I made a description, how I did, this should also work on 6.1. kernel. Although I aready sent it here, I repeat it (with some minor additions). Attention: Sometimes, nvidia-detect says, use 340xx-legacy, but I had some cases, where I in real had to use 390xx. So, if 340xx is not working, try 390xx. Do it exactly in this order desribed below and you may read this site before. https://wiki.debian.org/NvidiaGraphicsDrivers[1][2][1] 1. Install module-assistant 2. Enter the line for sid into your /etc/apt/sources.list deb http://deb.debian.org/debian/[2][1] sid main contrib non-free non-free- firmware 3. apt update 4. apt install nvidia-legacy-340xx-driver firmware-misc-nonfree This should install all necessary files and build the kernel module. Here it did work. 5. Do NOT upgrade any other files! Do NOT aot upgrade or aptitude upgrade now although it will install many other packages. Ignore that! It will break your system!! 7. Remove the sid entry from sources.list! (Very important!!!) 8. Do again an apt update. Thus you are not going into the danger, to install any more packages from sid. 9. If you need bumblebee or primusrun, because you have two GPUs (one in the CPU and one extern), then use the packages from stable. This will work! My notebook is a Lenovo T520 with Intel CPU (and internal Intel GPU) and also NVidia GPU as external GPU (soldered on mainboard). I have to use optimus, to get my external GPU (NVidis) running. Hope, this helps. Ah, and last but not least: Big thanks to the lads and guys, who made 340xx and 390xx buildable again, great work! Big big thank you!!! Here on my system, 390xx is working like a charm. Please feel free to ask for more. Good luck! Hans [1] https://wiki.debian.org/NvidiaGraphicsDrivers [2] http://deb.debian.org/debian/
[SOLVED] Re: Virtual machine - booting from USB?
> yes > https://www.baeldung.com/linux/qemu-boot-physical-drive > (minimal answer ;-) ) Hi Didier, thanks for the quick response! This is working perfectly. However, fanca thing is: virtual-manager is working great, but Aqumu got not this option. Obviously both are based on qemu. Well, now as I know, that qemu is working, I will check if I can use also the commandline with qemu. Should be possible! As virtual-manager is not always available or installed (i.e. Windows or MacOS), a batch file on an USB-stick starting qemu will do it. For now I can say: Problem solved and thank you very much for the link. Best Hans
Virtual machine - booting from USB?
Hi folks, does one know, if it is possible to boot from an USB-stick within a virtual machine? I want to boot a multiboot usb stick with YUMI within a virtual machine. Tried Virtualbox (here you can only make a *.vdk from the USB-stick and boot it), as well as virtual-manager (seem also only be capable to boot images) and quemu (with aqemu gui). Last also images, no devices. However, I don't now if this is possible at all, so I allowed me to as here, if one knows, if this is possible with some virtual machine - just before I am trying and searching until my death. Hint YES - I could create an ISO-image from the USB stick and copy this to another USB-stick, then mount it and thenn boot it. This will work! But NO, I do NOT want to create an ISO from the USB-stick, I just want to leave it as it is for some reasons. Short answer like "yes, it wqill wor with" or "no, this is not possible..." will be fine for me. Thanks for reading. Best regards Hans
Re: nvidia driver for GTX 970
> > You don't get security updates for backport kernels, so I'd strongly > oppose it if you're running an exposed server. But for a desktop system > in a normal kind of setup (behind a firewall, or on a private network) > it should be within reasonable expectations of security. Huh, this is an interesting information! I wondered, why there was no new bpo-kerrnel after the discovery of CVE-2023-6546 in April. Kernel 6.1.0- got an update, but 6.5.0-bpo NOT. My question in the forum about this was not stisfactionally answered. But now we now: CVE-2023-6546 is still in 6.5.0-bpo! Thanks for the advice. Best Hans
Re: nvidia driver for GTX 970
Hi Ebon, you said, it is flashing? Or do you have a blamk screen? This can happen, when the resolutionb of the monitor is out of sync. You can try to create an /etc/xorg.conf file, where you can set the resolution. Xorg.conf is not needed any more, as the monitor is telling the resolution and the driver discovers it. But you might get false results. Also you my try not to connect tu HDMI port, if your carrd oor your monitor has VGA or DVI, try these, too. My card has HDMI and DVI, and I am using a cable with HDMI on one side, the other has DVI. Prior I was running another monitor with the GT-960 with an adapter from DVI to VGA on the card side, and VGA on the monitor side. Ah, and one thing: There are different qualities within HDMI cables! I sometimes had to exchange HDMI cables by customers when they use it at sattelite receivers with HDMI output to the TV. Exchanging it and suddenly I got a picture! So, try some other HDMI cable, too. >From your mail I see nothing to be wrong in debian, so far everything looks fine. Oh, another hint: You can also try the tesla driver (it is something 470.xx.xxx), this one should also run perfectly. The 535 needs some special funtions, not all NVidia graphic chips got them. I used both, and there was no performance difference between the two versions. However, the 470.xx version is looking a little bit stabler, but this I can not prove. Just a feeling. Hope this helps! Best Hans
Re: nvidia driver for GTX 970
> What Steam games do you have working under Nvidia? I have watched people on > YouTube play some interesting and modern games using Nvidia + Linux and > with ray-tracing, but they have to do a lot of customisation from what I > could tell. From my experience basic distribution installations do not give > this kind of experience. For eample I anm running Half-Life 2 oor Black Mesa (the new one). No problems, ecept for Black Mesa it lasted some time, untik the shaders were adjusted by Steam. It is running smooth and fluently (1600x1020), double sampling and (mostly) set on highest performance. However, I am running games on Steam mostly in LXQT, but in KDE it works also well. Native games, like my flightsim (X-Plane 12) are also running fluently, much better than in Windows. My CPU is an older AMD FX with 6 cores. 3,4GHz clock. Best Hans
Re: nvidia driver for GTX 970
Hi Ebon, I am running a NVidia GTX-960 iin Debianbookworm and it is working lie a charme. No problems with any of the apps, Greg mentioned. KDE, Steam games and everything elese is working great. FYI I am running a backport kernel, it is 6.9.7+bpo-amd64. If your card is not detected, check, if the neouveau kernel module is blacklisted. There should be an entry in /et/modprobe/ named "nvidia-disable-nouveau.conf", which is creatred during install. If not, either create one manually or delete the kernel nouveau module manually. Ok, let us guess, it is already blacklisted and not loaded. Check., if it is NOT loaded and if nvidia kernel modules ARE loaded: lsmod | grep nouveau lsmod | grep nvidia Is the kernel module "nvidia" running? Well, for testing purposes move any login manager tewmporarly out of the way (these are /usr/ bin/lightdm, /usr/bin/kdm, /usr/bin/sddm and whatever you have.) . When you now reboot, you will get just the console, but if you give the command "startx" as root, X-Server should start. If NOT, it will show you the reason why. Please tell us, what it said. If it is now starting well, you are good and can move your loginmanagers back. After reboot, it should automatically starting the -Server witrh a login greeter. If still not, check, if the kernel does see the hardware. Use the command "lspci" and look, if the graphics card is seen. If yes, then you are good. If this does not help, and you need further assistance, please let us know and provide any information you got, especially all messages, exact bahaviour, what you did and how and so on. List of installed packages: protheus1:~# dpkg --get-selections | grep nvidia | egrep -v deinstall firmware-nvidia-gsp install glx-alternative-nvidia install libegl-nvidia0:amd64install libegl-nvidia0:i386 install libgl1-nvidia-glvnd-glx:amd64 install libgl1-nvidia-glvnd-glx:i386install libglx-nvidia0:amd64install libglx-nvidia0:i386 install libnvidia-cfg1:amd64install libnvidia-egl-gbm1:amd64install libnvidia-egl-wayland1:amd64install libnvidia-egl-wayland1:i386 install libnvidia-eglcore:amd64 install libnvidia-eglcore:i386 install libnvidia-glcore:amd64 install libnvidia-glcore:i386 install libnvidia-glvkspirv:amd64 install libnvidia-glvkspirv:i386install libnvidia-ml1:amd64 install libnvidia-pkcs11-openssl3:amd64 install libnvidia-ptxjitcompiler1:amd64 install libnvidia-ptxjitcompiler1:i386 install nvidia-alternative install nvidia-cuda-mps install nvidia-driver install nvidia-driver-bin install nvidia-driver-libs:amd64install nvidia-driver-libs:i386 install nvidia-egl-common install nvidia-egl-icd:amd64install nvidia-egl-icd:i386 install nvidia-installer-cleanupinstall nvidia-kernel-commoninstall nvidia-kernel-dkms install nvidia-kernel-sourceinstall nvidia-kernel-support install nvidia-legacy-check install nvidia-modprobe install nvidia-settings install nvidia-smi install nvidia-support install nvidia-tesla-alternative:i386 install nvidia-tesla-driver install nvidia-tesla-driver-bin install nvidia-tesla-kernel-source install nvidia-vdpau-driver:amd64 install nvidia-vdpau-driver:i386install nvidia-vulkan-commoninstall nvidia-vulkan-icd:amd64 install nvidia-vulkan-icd:i386 install xserver-xorg-video-nvidia install ---- Good luck! Best regards Hans
Re: Little typo bug - package unknown, kernel version unknown
Thank you for the info. Filed a bugreport. Best Hans > Kernel messages come kernel package, e.g. linux-image-4.19.0-27-amd64. > > Groeten > Geert Stappers
Re: Little typo bug - package unknown, kernel version unknown
Hi Andy, I am quite not sure. I filed a bugreport to the kernel team, as it is only a little typo and does no harm, they can drop it or fix it. Hmm, your idea came also in my mind already, but I did not check for it. Although I owe several Samsung devices, they are all different models. So the kernel will recognize each different. Otherwise I could check, if two devices of the same model behave different. If they create equal answers, there is still the chance, the kernel answers incorrect or the manufacturer answers incorrect. I am not sure, who is telling the menufacturer: the kernel or the device itself. You can be right, the device is telling the manufacturer, but I am not completely sure of it. Best Hans > Is it possible this is the device itself identifying like that? I do > not find "Sasmsung" anywhere on codesearch and the code that prints > that seems to believe what the device tells it… > > Thanks, > Andy
Little typo bug - package unknown
Dear list, I discovered a little typo bug, which mightnot be important, but maybe one knows, which developer can be informed. Wheh connecting a mobile fdrom Samsung to my computer, the message in /var/log/syslog tells: 2024-08-07T13:11:14.047644+02:00 protheus2 kernel: [ 2649.347050] usb 2-1.1: Product: MSM8952 2024-08-07T13:11:14.047647+02:00 protheus2 kernel: [ 2649.347054] usb 2-1.1: Manufacturer: Sasmsung As we know, it should be "Samsung" not "Sasmsung". I believe it does no harm and it is just a typo. However, as I could not get, which package is responsible for it (this showed also in kali and other debian installations), I allow me to ask here. If one knows, please drop the developer a short message. Thank you very much for your help. Best regards Hans
Re: switch users and still use display
Some window managers are offering an option, to change the user (plasma = KDE does it, for example.). It is also possible, to start a new X-session and login with another user. Doing so, you have 2 X-session open. The option is also, to change the user, or, add another user with a new session. Sometimes, I need to start an application as root in X (for example, if I want to edit a configuration file, only rott is allowed to edit) ands I want to use a graphical writer, like kwrite (just an example). Instead of logging out and relogon into the window manager as root, I am starting a shell., and enter "su -p" (this meany, preserve my environment). Thus I can start any graphical application from the shell (starting kwrite with the command) and it will start with root permissions. In earlier times, there was "sux" a wrapper for su, but this is no more available. I never found an official documentation about "su -p", just found it myself, but I read, "su -" shall do the same. It does not. Maybe your question aimed to this scenario, if so, there is my solution. Have fun! Best Hans
Re: info
Am Montag, 22. Juli 2024, 08:07:29 CEST schrieb Francesco Di Lorenzo: > good morning, > i installed debain 12 from your site, and using the usb , I did the > installation, but I don't know why I don't get the desktop enviments , it > is only text. what I can do? > thanks Looks like the X server is not runnning. You need to install the required packages for X. For further help we need information about hardware, especially processor and graphic chip. The more information, the better. Best Hans
Re: CrowdStrike and drivers (was Re: why reliable linux hasn't gained more market share?)
I do not agree to this. Updates should be installed as soon as they are available. Especially security updates. It shows , that within 24 hours after the release of an update, an exploit is available for this security hole. But you should do it corrdectly, like some hospitals did: First check with a canary (a testserver or some unimportant server), then, when everything is working without any problems, roll it out to the rest of the servers. Waiting for some days is a very very bad idea! I admit, that many people do not so, because they are comfortable and this requires more work. But it is the correct way! And really: This is not a new knowledge, this practice is standard since years (or should be everywhere). If one think, he must not do it and rely on the manufacturer, well his decision. If it breaks, i have no pity for him. Best Hans > At the very least, updates should be avoided for a few days after > release, unless they are the exceeding rare 'Oh my God, patch this > yesterday' kind, such as when the malware writers of the world realised > that Windows MetaFiles could contain executables... > > Small businesses cannot really do as you say, but any business large > enough to have logistics problems in fixing all of their machines > quickly should do so.
Re: why reliable linux hasn't gained more market share?
> You missed one: Linux is virtually a virus-free environment, and a > large user base would mean many more people running as root, and it > would become worth the time of malware writers to target Linux. Linux > would become as virus-ridden as Windows. > > It would also become a target for data harvesting, from which Debian, > at least, is refreshingly free. I have no doubt that MS makes more > money from user data sales than it does from sales of domestic versions > of Windows. I do not agree. This is an argument, i am often get confronted with. The more linux, the more malware? No, it isn't. See, linux is the most used OS in the server world. All important companies rely on it. EBay, Google, Amazon, and even Microsof. Its DNS running Linux. Cloudflare and others, too. So, these are really interesting targets, where you can really hurt lots of people. If linux would bre so easy to crack like Windows, the attackers would do. But it isn't. It is (mostly) secure by design. There are millions of "viruses" for Windows, but only a handfull of viruses (or rootkits) for linux. And think of OpenBSD: Only 2 security holes in more than 15 years. How many security holes got Windows in th elast 10-15 years? With all their money, which can buy any super, duper coder look at the result. No, I see it else. It can be done (OpenBSD is showing it). It is the arrogance of Microsoft (and many other companies). It is not the spread of Windows, it is theire bad quality what makes crackers attack this system. Low fruits, you know? And there is another thing, that makes linux better: The developers want to write stable and secure software. It is theire joy and happiness. They do not mourn, when someone is telling a bug or a security hole. They are happy, to fix it. Making theire software, theire "baby" better. In market, the developers MUST do it, for them fixing software is just annoying and more work (for the same money). That is the differnce. Note: I do not want to claim, linux developers are the better coders. But they are coding with theire heart. That makes the difference. It is not the spreading of software. Have fun! Hans
Re: why reliable linux hasn't gained more market share?
Which is not quite correct. As a hamradio (I am one), you are allowed to develop your very owh rf-devices. Transceivers, measure equipment, whatever you like. Many things, we are using today in consumer devices are first developed by radio amateurs (example shorthand "packet radio", which is data over hf). When you have a radio amateur license, you can do lots of things in the air. Sure, there are regulations, you are not allowed to transmit anywhere and your transmit power is reduced to 750W, but this does not technical restrict you. Hamradio is the freedom in the air, you have in coding in linux. Also here are some rules (GPL, ethicness, kindness whatever), but those do not techniocal restrict you in any way. Best regards Hans > Which the current rules for such does not allow, by FCC edicts, only > sealed FCC approved blobs are allowed to play in the rf field. > So don't blame the coders, blame the regukatory agencies. > > > Regards, > > Cheers, Gene Heskett, CET.
Re: why reliable linux hasn't gained more market share?
Hello, well, the thing is: Do we really want to go to more market share? Let's imagine, Debian becomes market relevant, what will happen? Sure, more developers get paid, what is very nice. But not all developers will. Many good developers will not be paid and when the market will rule things, then many good developers will be pushed away or demoralied. Because it will become common, that people will no more cherish theire work. The development of a few people will be cherished, those, who create programs, the market wants. I am using linux since more than 30 years and it is impressive, what people can do, when they can do, what they want and what they like. And look at the quality, look, what has been created since the beginning. This was only possible, because no market forced people, to do things the market wants, not what the developers want. I think, we all can be happy, that we are not dependent from any market, the developers, because theire freedom and theire contentement is not been deminished, and the users, who get very good and high qulitative software to work with. And if you really think, the more you spend, the better the software, you can of course buy software only from the market. Or, you can donate linux developers and/or distributors of your money. Personally(!) I think, the second way is better, because I can speak directly to developers, could (if I would be capable of) fix things myself together with the developers and maybe can even ask him, to implenent some functions especially for me. All things, a market driven software will never offer. So, I think, we can be happy, that linux (and debian) is not market relevant. It will lose its freedom, its high quality and the joy of many people. Sorry, if I did not always find the right expression, I am not native English. Best regards Hans
Re: umask - default user settings?
> The door is closed by default in bookworm. User home directories are > created with 0700 mode, see /usr/share/doc/adduser/README.gz and > /usr/share/doc/adduser/NEWS.Debian.gz As a result, it is necessary to > set ACLs e.g. to run unprivileged LXC containers. That is not the point. The point us, that debian is creating a default user "for your daily work" at installation with umask 022. And we are not talking about experienced users, but of linux beginners. I doubt, they are aware of umask and rights and so. Debian is made for every people, not only for experienced people. Yes, when adduser cares about, this is one good step, but does not touch my argumentation. Also, when some other applicatiions are setting correct rights. Some do, some don't. That is not the point, too. The point is, should't we do it completely and make it standard by default - also and especially during installation to make debian more secure for unexprienced users and linux noobs? Best Hans
Re: umask - default user settings?
I see itthe other way round. No, if you are in the secure area, it is the responsibility of the owner to make it secure by design i.e with dself closing doors where you can not look into or windows with curtains. However, I presume, debian wants to be secure. If no one cares and all agree with this (in my personal opinion!) security whole, I will have to accept this. For myself I found a solution of course, and I just could have not told about it, but I cared for others and tried to put my 2 cents in it, to improve the security of debian. If this is too much, then we can close this issue at once. Shall we? Hans > If you are writing something confidential, it is your responsibility to > lock the door of your office. > > Regards,
Re: umask - default user settings?
Greg, I do not agree. If I am writing a document with private content, then I do not want to let it be read by someone else except me. No one has to read any letters or cv's or maybe documents for my lawyer, my medic, my friends or whatever. And after years there are a lot of documents one is writing, many private things. And i think, no one wants to sharew these with other users on the system! At least, I won't. Best Hans > hobbit:~$ ls -l .ssh > total 72 > ... > -rw--- 1 greg greg 1876 Sep 24 2019 id_rsa > -rw-r--r-- 1 greg greg 394 Sep 24 2019 id_rsa.pub > > The other 99.9% of your files are not secret, so they don't need to > be hidden.
Re: umask - default user settings?
Hi Greg, yes, did already change it. However, this looks like a security hole for me, as I believe, not many people or admins are changing this. IMO debian should change this in the next release, but I doubt it. I will ask the security team for it, they will decide. Have fun! Hans Am Sonntag, 14. Juli 2024, 19:18:07 CEST schrieb Greg Wooledge: > On Sun, Jul 14, 2024 at 19:09:54 +0200, Hans wrote: > > I am wondering, why on a multiuser system like debian the rights for a > > normal user are "rw- r-- r--", (owner: user and ownergroup: usergroup) > > Tradition, and a culture based around sharing. > > The Unix culture of openness and freedom (specifically the freedom to > distribute your work to others) works best if you can say "Hey Betty, > can you take a look at my .bashrc? I can't get my foo() function to > work." Or "Hey friends, I've made some changes to my bar.c file that > you might want to look at." And then they can just read the files > directly from your home directory. > > If you don't like this setting, change it.
umask - default user settings?
Dear list, I am wondering, why on a multiuser system like debian the rights for a normal user are "rw- r-- r--", (owner: user and ownergroup: usergroup) Of course there is a reason for this, but it is not understandable for me. First two are clear: rw for myself, and readable for all users, i am allowing into my own grou. The last one is not clear for me. Why should I allow the rest of the world read my personal documents? These are private and no one else should be able to read them! So I would have expected a setting of "rw- r-- ---" for any files. Before someone argues, "you can change this by editing umask", yes, I know of this of course. But it is not clear for me, why it is set that way by default and not as I would have expected as described above. Sure, there is a reason for this, so I will be happy, if someone could enlighten me. Best Hans
[SOLVED] Re: Results of Testmail_1-3
Hi folks, first of all: No, I can not change my provider nor use another smtp server. second: I thought, this issue involves other people on this list, too, which might be interesting for them. third: I supposed, this issue is caused by debian mailservers, because this issue appears ONLY at the debian list and nowhere else, I tested here. fourth: As this issue seem only affect me, I suggest to close this discussion, because it creates a lot of unnecessary traffic. So I set this to "solved" and won't ask further more. Thank you everyone, for your patience and your help! Best regards and have a nice weekend! Hans
Re: nouveau on old NV GPUs (was: NVidia 340 video driver in Bookworm?)
This should not have been happened. Maybe you dis something in a wrong way? I treid myself and it did not deinstall kde. It is important, not to do any upgrade while the entry for sid is in sources.list. Just install both packages (as told in the wiki), then after this install remove the sid entry at once and repeat an apt update again (this will delte all entries from the sid repo). This step is really important! So you will only get both packages and its dependencies, nothing more. It also will not deinstall kde, if doing so. I suppose, you might have forgotten to do an apt update after installing the two packages, so it looks for me, and of course, then it will deinstall packages with missing dependencies. Solution? Hmm, make sure, the sid entry is removed from sources.list. Then do an apt-get update and apt-get install --reinstall task-kde-desktop (or with your language i.e. task-german-kde-desktop). This should reinstall all necessary packages again. So note: If you do an apt-get update, aptitude update or apt update, you can retrieve to the package list of only packages of the repo, which are active in sources.list. Any of the above commands will set actualise the package lists. Hope, this helps. Best Hans > at least KDE, and now it won't enter run level 5. I added > nouveau.modeset=0 to the "linux" line in grub.cfg, but it's still > running the nouveau driver, or at least that's what inxi -G reports: >
Re: Testmail_3: Reply to one of the mails from The Wanderer
Yes, I saw the DKIM=fail at the first time, but debian said, it is the fault of megamailservers.eu and theire servers are ok. So I contacted megamailservers.eu today, but generally I can do nothing else myself, as I am no admin of any involved mailservers. So, hopefully they will answer. IMO something is wrong, or let's say, soemthing is not working as I expect it. At the moment I have no further clue. So, we will wait. Lets stop for now. But thanks for the help and your time! Best Hans
Re: Testmail_3: Reply to one of the mails from The Wanderer
This ypou received NOT from the list was my fault - forgot to add the address in the To: field. Sorry Hans > ...and the second copy which I received *not* via the list (which I'm > assuming, but haven't verified, was sent by BCC or similar rather than > being a separate unique mail), which I did not see before sending my > previous reply, also had dkim=fail.
Results of Testmail_1-3
So, these are th eresults: 1. A new created maiil does not have a spam tag. 2. Reply to my own mail does also not have a spam tag. 3. Reply to any user mail DOES have a spam tag. So it looks like there is something , which some mailservers do not like. As I am sending only text from me, seldom the text of the users, I suppose, there is something in the header of the mail, which causes this issue. I suppose, I can do nothing else but create a new mail and copy and paste from the received mail of the user. This should avoid the spam tag. Weired thing at all. Hans
Testmail_3: Reply to one of the mails from The Wanderer
Surprisingly Testmail_2 appeared WITHOUT the SPAM tag. This one is a reply of a mail from The Wanderer. I expect it WITH the SPAM tag from the debian list. Hans
Testmail_2: Re: Testmail_1: This is a new created mail!
Am Donnerstag, 4. Juli 2024, 21:59:23 CEST schrieb Hans: > This is a newly created testmail! This one should appear without the SPAM > tag. > > After I get this mail from the list, I resent a reply to this mail named > Testmail_2. > > Hans This is a reply to my own Testmail_1. I expect this one getting WITH the SPAM tag from the debian list. Hans
Testmail_1: This is a new created mail!
This is a newly created testmail! This one should appear without the SPAM tag. After I get this mail from the list, I resent a reply to this mail named Testmail_2. Hans
Re: This is a testmail!
Hi The Wanderer, > Hans, are you certain you composed those three messages the same way, > using the same interface of the same program, and sent them the same > way? No, the first mail was created natively (= a new mail), the one with the "[SOLVED] in the subject was a reply to someones mail from the list and the last mail was also a reply this time of my of my own. It looks like replying to soemone (my normal behaviour) is causing this issue. And it looks like, that I am getting the SPAM tag, not you. Some minutes ago I informed megamailservers.eu of my problem and sent them the mail with the headers, i sent here, too. Hopefully I will get some response. The strange thing is,this issue suddenly apeared from nowhere. I have nothing changed here (except of upgrades). I am running debian bookworm and my mail client is kmail. But that should not be the problem. Best Hans
Re: This is a testmail!
Me again, sorry. Now I got my last mail back with the spam tag! Subject: Re: *SPAM* [SOLVED] Re: This is a testmail! This is the header: X-Spam-Flag: YES X-SPAM-FACTOR: DKIM X-Envelope-From: bounce-debian-user=hans.ullrich=loop...@lists.debian.org DMARC-Filter: OpenDMARC Filter v1.4.1 mail39c50.megamailservers.eu 464C5Iek122979 Authentication-Results: mail39c50.megamailservers.eu; dmarc=none (p=none dis=none) header.from=loop.de Authentication-Results: mail39c50.megamailservers.eu; spf=none smtp.mailfrom=lists.debian.org Authentication-Results: mail39c50.megamailservers.eu; dkim=fail reason="signature verification failed" (1024-bit key) header.d=megamailservers.eu header.i=@megamailservers.eu header.b="QLjumGn/" Return-Path: Received: from bendel.debian.org (bendel.debian.org [82.195.75.100]) by mail39c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 464C5Iek122979 for ; Thu, 4 Jul 2024 12:05:21 + Received: from localhost (localhost [127.0.0.1]) by bendel.debian.org (Postfix) with QMQP id EA3E420682; Thu, 4 Jul 2024 12:05:15 + (UTC) X-Mailbox-Line: From debian-user-requ...@lists.debian.org Thu Jul 4 12:05:15 2024 Old-Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on bendel.debian.org X-Spam-Status: No, score=-10.5 required=4.0 tests=DKIM_INVALID,DKIM_SIGNED, FOURLA,KHOP_HELO_FCRDNS,LDOSUBSCRIBER,LDO_WHITELIST autolearn=unavailable autolearn_force=no version=3.4.6 X-Original-To: lists-debian-u...@bendel.debian.org Delivered-To: lists-debian-u...@bendel.debian.org Received: from localhost (localhost [127.0.0.1]) by bendel.debian.org (Postfix) with ESMTP id C18E42067A for ; Thu, 4 Jul 2024 12:05:07 + (UTC) X-Virus-Scanned: at lists.debian.org with policy bank en-ht X-Amavis-Spam-Status: No, score=-6.301 tagged_above=-1 required=5.3 tests=[BAYES_00=-2, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FOURLA=0.1, KHOP_HELO_FCRDNS=0.399, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no Received: from bendel.debian.org ([127.0.0.1]) by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525) with ESMTP id CNGEsE8xgvQ4 for ; Thu, 4 Jul 2024 12:05:03 + (UTC) X-policyd-weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 HELO_IP_IN_CL_SUBNET=-1.2 (check from: .loop. - helo: .mail194c50.megamailservers. - helo-domain: .megamailservers.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -4.7 Received: from mail194c50.megamailservers.eu (mail208c50.megamailservers.eu [91.136.10.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by bendel.debian.org (Postfix) with ESMTPS id EC67D20677 for ; Thu, 4 Jul 2024 12:05:02 + (UTC) X-Authenticated-User: 01793666...@o2online.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1720094700; bh=5Um9/MplAQNd+svZJOunmBGElnorPOi9odLzGqxgObQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QLjumGn/60xFVhN9BUbajEg0uTOZxqi/Uz8jodz7E1EE2Hi7W3VtjJFW4LGmbJGnC Lt7Nym0B3iEmO+1/fxpnDfmt1lRnzu+Q65akTEd8eaEHbj8G7yo5OCpI4oVjRr7q9o pn0upeaUIrxnepbAwXeozeebIuTSx2zuaH0xvL30= Feedback-ID: hans.ullrich@lo Received: from protheus2.localnet (a89-183-193-109.net-htp.de [89.183.193.109]) (authenticated bits=0) by mail194c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 464C4rxR025870 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 4 Jul 2024 12:04:55 + From: Hans To: debian-user@lists.debian.org Subject: *SPAM* [SOLVED] Re: This is a testmail! Date: Thu, 04 Jul 2024 14:04:53 +0200 Message-ID: <2408526.NG923GbCHz@protheus2> In-Reply-To: <46505217.fMDQidcC6G@protheus2> References: <3645068.R56niFO833@protheus2> <66868718.1030...@fastmail.fm> <46505217.fMDQidcC6G@protheus2> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-VADE-SPAMSTATE: clean X-VADE-SPAMSTATE: clean X-VADE-SPAMSCORE: 0 X-VADE-SPAMSCORE: 0 X-VADE-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeeftddrudelgdegiecutefuodetggdotefrodftvfcurfhrohhfihhlvgem ucfjqffuvffqrffktedpgffpggdqveehtdenuceurghilhhouhhtmecufedtudenucenucfjughrpefhvffufffkjgh fggfgtgejudeftdfjphegsehtufertddttdejnecuhfhrohhmpefjrghnshcuoehhrghnshdruhhllhhrihgthhesl hhoohhprdguvgeqnecuggftrfgrthhtvghrnhephfdvudekheefueevieelgefftdfhtedvlefgfefhieevveejud elhffhleethfeknecukfhppeekvddrudelhedrjeehrddutddtpdekledrudekfedrudelfedruddtleenucevlhh ushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeekvddrudelhedrjeehrddutddtpdhhvghlohepsg gvnhguvghlrdguvggsihgrnhdrohhrghdpmhgrihhlfhhrohhmpegsohhunhgtvgdquggvsghirghnqdhus hgvrhephhgrnhhsrdhulhhlrhhitghhpehlohhophdruggvsehlihhsthhsrdguvggsihgrnhdrohhrghdpnhg spghrtghpthhtohepuddprhgtphhtthhopehhrghnshdruhhllhhrihgthheslhhoohhprdguvg X-VADE-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeeftddrudelgdegjecutefuodetggdotefrodftvfcurfhrohhfihhlvgem ucfjqffuvffqrffktedpqfgfvfdpgf
[SOLVED] Re: This is a testmail!
Am Donnerstag, 4. Juli 2024, 13:58:07 CEST schrieb Hans: Answering myself: At the moment everything is looking fine. Maybe after the big issue yesterday, the mail admins somewhere in the world have fixed the problem? Dunno. Whatever, strange. I will watch this in the future. Let's close this issue for now, so that this list is not too much filled with unusefull spam. However, if this issue appears again, I will allow myself to ask again for help. Thank you all for your quick response! Best regards Hans > Hmm, this is strange. Maybe I wrote my testmail from scratch. > > This one is a reply as it have been, when the issue appeared. > > Strangely my own testmail appeared without the SPAM tag this time. > > Maybe there is a difference, if I am using a reply mail. > > I will watch this and search for more information. > > Hope, not everyone is replying now, only one feedback is enough. > > Thanks for help though. > > Best > > Hans
Re: This is a testmail!
Hmm, this is strange. Maybe I wrote my testmail from scratch. This one is a reply as it have been, when the issue appeared. Strangely my own testmail appeared without the SPAM tag this time. Maybe there is a difference, if I am using a reply mail. I will watch this and search for more information. Hope, not everyone is replying now, only one feedback is enough. Thanks for help though. Best Hans
This is a testmail!
Hi folks, this is a testmail, because I got some trouble with the mailingist. As reported before, I get all ,mails from debian-user@lists.debian.org with tagged with *SPAM added to the subject. This is because of some DKIM failure, as reported before. As I could fix this by setting a special rule for this mailaddresse in spamassassin, I know dicovered another issue. When I am sending a mail to the list, it looks like the subject is completely replaced with only "*SPAM*". I would like to know, when this happens. Either during the transfer from me to the debian server, or when it is sent from the debian server to me. This mail has the subject "This is a testmail!". It would be nice, if someone could tell me, if this mail is tagged with "SPAM" somewhere and if the subject is removed or not. This behaviour appeared suddenly several months ago and I do not know, what, might have changed since then. Thank you for your help. Best regards Hans
Re: nouveau on old NV GPUs (was: NVidia 340 video driver in Bookworm?)
Tried again, somehow there was no subject sent with my last mail. So, well, I believe I got a solution. However, not everyone might be happy with it, but maybe it will work. I am running the kernel 6.7.12+bpo-amd64 on my system. This is a backport kernel, but it might also work with other kernels, too. You also need to install the build environment, the easiest way is to use module-assistant. If you got this set and installed linux-headers and so on, then do the following: First, enter the line for sid into your /etc/apt/sources.list deb http://deb.debian.org/debian/[1] sid main contrib non-free non-free-firmware then do apt update apt install nvidia-legacy-340xx-driver firmware-misc-nonfree This should install all necessary files and build the kernel module. Here it did work. However, I had to use 390xx instead of 340xx, but both built here fine. After it, reboot and try again if it is working. Sometimes, nvidia-detect says, use 340xx-legacy, but I had some cases, where I in real had to use 390xx. So, if 340xx is not working, try 390xx. Note: Do NOT upgrade any other files! I suggest, after installing both packages as above, remove the sid entry from sources.list and do again an apt update. Thus you are not going into the danger, to install any more packages from sid. If you need bumblebee or primusrun, because you have two GPUs (one in the CPU and one extern), then use the packages from stable. This will work! My notebook is a Lenovo T520 with Intel CPU (and internal Intel GPU) and also NVidia GPU as external GPU (soldered on mainboard). I have to use optimus, to get my external GPU. I got my information from this site. https://wiki.debian.org/NvidiaGraphicsDrivers[2][1] Hope, this helps. Ah, and last but not least: Big thanks to the lads and guys, who made 340xx and 390xx buildable again, great work! Big big thank you!!! Here on my system, 390xx is working like a charm. Good luck! Hans [1] https://wiki.debian.org/NvidiaGraphicsDrivers [1] http://deb.debian.org/debian/ [2] https://wiki.debian.org/NvidiaGraphicsDrivers
Re: Re: nouveau on old NV GPUs (was: NVidia 340 video driver in Bookworm?)
Hi van Snyder, I believe I got a solution. However, you may not be happy with it, but maybe it will work. I am running the kernel 6.7.12+bpo-amd64 on my system. This is a backport kernel, but it might also work with other kernels, too. You also need to install the build environment, the easiest way is to use module-assistant. If you got this set and installed linux-headers and so on, then do the following: First, enter the line for sid into your /etc/apt/sources.list deb http://deb.debian.org/debian/ sid main contrib non-free non-free-firmware then do apt update apt install nvidia-legacy-340xx-driver firmware-misc-nonfree This should install all necessary files and build the kernel module. Here it did work. However, I had to use 390xx instead of 340xx, but both built here fine. After it, reboot and try again if it is working. Sometimes, nvidia-detect says, use 340xx-legacy, but I had some cases, where I in real had to use 390xx. So, if 340xx is not working, try 390xx. Note: Do NOT upgrade any other files! I suggest, after installing both packages as above, remove the sid entry from sources.list and do again an apt update. Thus you are not going into the danger, to install any more packages from sid. If you need bumblebee or primusrun, because you have two GPUs (one in the CPU and one extern), then use the packages from stable. This will work! My notebook is a Lenovo T520 with Intel CPU (and internal Intel GPU) and also NVidia GPU as external GPU (soldered on mainboard). I have to use optimus, to get my external GPU. I got my information from this site. https://wiki.debian.org/NvidiaGraphicsDrivers[1] Hope, this helps. Ah, and last but not least: Big thanks to the lads and guys, who made 340xx and 390xx buildable again, great work! Big big thank you!!! Here on my system, 390xx is working like a charm. Good luck! Hans [1] https://wiki.debian.org/NvidiaGraphicsDrivers
Re: balenaEtcher
Am Freitag, 28. Juni 2024, 21:55:42 CEST schrieb Aleix Piulachs: > I’ve been tryed to boot a flash usb with Parrot and balenaEtcher but gives > error is there another app for to boot a flash usb but not the rufus app? Did you tr using the dd command? dd if=/path_to_iso/parrot.iso of=/dev/sdc bs=8192 or ou can also use dcfldd, which additionally is using file verification. Best Hans
Re: how2 format a flash drive
You can easily refotrmat it, either using fdisk or if you want a GUI, use gparted. With fdisk (also you can use cfdisk) I suggest first to delete all partitions, then create new one. Then choose your type (it is 0b for FAT32). Write to disk and quit fdisk. Then format the new partition, for vfat use: mkfs.vfat /dev/sdc1 (or whatever your partition is). Everything must be done as root (of course) so be carefull. Hope this helps. Best Hans
marble or marble-qt?
Hi folks, I am a little confused, because I got marble double on my system. There is marble (package marble) and kde-marble (which is marble-qt), which both look the same when started. Question is, which one should be preferly installed and can one be left? I am running Plasma (KDE), buz I am also using XFCE and LXQT as well. Thanks for a short answer. Best Hans
Re: disable GUI/X?
Just remove any login-manager like gdm, kdm, sddm and lightdm. For testing purposes, you can eaily remove the binaries below /usr/bin/ to somewhere, for example to /root/. Then reboot and it will not boot into X. Startx will work. And if this is not what you want, just move the binaries back to /usr/bin/, reboot and X is starting at boot again. Hope this helps. Best Hans > >>> # systemctl get-default # reports bootup state # systemctl set-default > >>> graphical.target sets GUI as default state # systemctl set-default > >>> multi-user.target brings system up without GUI running > >>> > >>> For a single boot to finish at multi-user, simply append 3 to the end > >>> of the (usually wrapped) linu line after striking E key at the default > >>> Grub menu selection. If already using multi-user.target default, > >>> append 5 to linu line to get a full GUI boot.
Re: *****SPAM***** Re: Package libllvm12:i386 does not exists on Debian ?
Yes, this is, where the entry "i386" is put in. I remember, to execute the command "dpkg --add-architecture i386" a very long time ago. Thus, aptitude now knows about it. Zhanks for making things clearer. Best Hans > Indeed, multi-arch is a dpkg thing. The list of current architectures > is kept in /var/lib/dpkg/arch [1] > > Cheers
Re: *****SPAM***** Re: Package libllvm12:i386 does not exists on Debian ?
I am wondering, why aptitude is showing me (incorrectlly?) libllvm*:i386 and apt-get not. I have no i386 entry in sources.list, but where does aptitude get its information? apt-cache search libllvm | grep i386 aptitude search libllvm | grep i386 p libllvm13:i386 - Modulare Techniken für Compiler und Toolchains, Laufzeitbibliothek p libllvm14:i386 - Modulare Techniken für Compiler und Toolchains, Laufzeitbibliothek i A libllvm15:i386 - Modulare Techniken für Compiler und Toolchains, Laufzeitbibliothek p libllvm16:i386 - Modular compiler and toolchain technologies, runtime library p libllvmspirvlib-14-dev:i386 - bi-directional translator for LLVM/SPIRV -- development files p libllvmspirvlib-15-dev:i386 - bi-directional translator for LLVM/SPIRV -- development files v libllvmspirvlib-x.y-dev:i386 - p libllvmspirvlib14:i386 - bi-directional translator for LLVM/SPIRV -- shared library p libllvmspirvlib15:i386 - bi-directional translator for LLVM/SPIRV -- shared library What did I miss? Hans
Re: Laptop fan freaks out on boot
Am Sonntag, 16. Juni 2024, 04:03:49 CEST schrieb jpeter17359...@tutanota.com: Just a shot: Take a look, if you have the packaget "fancontrol" installed. Then as root start the command "fancontrol" and see, if the vents are recognized. Normally they should stop, then start again. Just follow the instructions. This command is creating the file /etc/fancontrol, which you can later fine tune (i.e. tell, at which temperature the fans will start). On Asus laptops (especiially older laptops like eepc), I had to decide, which kernel module shoulds be used. One is "wmi" (the other one I forgot the neame of (too long ago!). Modern kernels are using wmi, but maybe your cpu does not support it and needs the older one (maybe someone else knows more). There are kernel options, which decide, which module is used. However, this is mostly on my EEEPC, but maybe other older laptops may alos depend on it. Just some ideas, hope this is helping though Best regards Hans > Hello Tomas, > > I looked at the boot.log files, as well as the output from your command, and > didn't see any errors or warnings. > > I'm going to report this issue to sub...@bugs.debian.org. > > The laptop is ten years old, but this behavior is definitely abnormal. > > Best regards, > > Jeff >
Re: systemrescuecd -- a bit off Debian topics
Am Donnerstag, 13. Juni 2024, 00:14:09 CEST schrieb Van Snyder: I found these at gitlab: https://gitlab.com/systemrescue/systemrescue-sources/-/project_members[1] [2] [3] _Francois Dupoux _ _@fdupoux _ Direktes Mitglied von _Francois Dupoux_ Owner Juni 04, 2018 Feb 02, 2019 Juni 13, 2024 [4] [5] _Gerd v. Egidy _ _@gvegidy _ Direktes Mitglied von Francois Dupoux[3] Maintainer März 26, 2019 Jan 03, 2022 Jan 14, 2024 [6] [7] _Marcos Mello _ _@marcosfrm _ SystemRescue[8] von Francois Dupoux[3] Developer Feb 01, 2020 März 17, 2022 Mai 30, 2024 Does this help? Best Hans > Does anybody know how to contact systemrescuece developers? Their web > page https://www.system-rescue.org/ doesn't have a "contact" or "forum" > button. > > My brother has impaired vision. He uses KDE Plasma because he can make > the tool bar large. But I haven't found a way to make the toolbar large > when I boot systemrescuecd. I think the window manager is xfce. Can the > tool bar be made larger? If not, and you have contact with the > systemrescuecd developers, please aske them to provide a way to make > the toolbar and icons larger, for vision-impaired users. > > Van Snyder [1] https://gitlab.com/systemrescue/systemrescue-sources/-/project_members [2] https://secure.gravatar.com/avatar/ 8a14d565c8db63b6c83d3ca49f666b37ade67cf6f6c4bc281169197a0ce75cd9? s=80&d=identicon&width=96 [3] https://gitlab.com/fdupoux [4] https://secure.gravatar.com/avatar/ ee1e7e8edf35c67b068c52eb504889bb249ccae34e4d1ae96849ad00d9a99dcb? s=80&d=identicon&width=96 [5] https://gitlab.com/gvegidy [6] https://secure.gravatar.com/avatar/ 54acaebb5339b2656c056cf3387339124e793d3f7095386756d0f1fed1cc2a18? s=80&d=identicon&width=96 [7] https://gitlab.com/marcosfrm [8] https://gitlab.com/groups/systemrescue
Re: NVidia 340 video driver in Bookworm?
No, the NV6800M needs 340xx driver, not 390xx as I prior posted. However, I have a GF-119 in my Lenovo T520, where nvidia-detect says, it needs 340xx. But, although I got 340xx compiled for the kernel, it did not start. I then build 390xx, which worked like a charm. This happened on my notebook and also on an older graphics card in my desktop pc (forgot, which graphic chip it was). The 340xx I never got compiled in bookworm, even when downloaded the sources from bullseye and downgraded compiler and other things (except of kernel). The issue: During build, the nvidia-sources were looking for some files, which were no more existent in the kernel headers since that version. So the build failed. I asked the developers of the kernel headers, to fix this, but they claimed, that NVidia has to fix it, not the developers. One can now argument for both sides. 1. Either tell Nvidia, "hey fix your old drivers to our new headers, we removed some libs!" or 2. Tell the developers "Hey, please put back the libs, so that the kernel module of this old driver can be build again!" In real life no one wants to care of it! Nvidia not, because this costs money and the developers not, because this is Nvidia and proprietrary (what is not quite correct, because the kernel-module, which is the part, that can not be build, is open-source). Before you try: It is also not possible, to download the driver from the NVidia site directly, because you will run into the same issue again: It can not be build! Personally I can not understand, why this is not beeing fixed. It is not a problem with the kernel-module itself (I mean, no bug in the function), but it just can not be build. This is the least, I would expect! However, this is just my own very personal Opinion and no one shall be feel blamed here with! Hope, this makes a little bit clearer. Oh, and of course, modern cards supported by 470 and higher, of course this can be build! But they do not support older cards (legacy cards). Best Hans > Did the 470 driver work for the GeForce 8600M? I tried to install the > 390 driver, but it said "This driver will ignore your GPU" so I didn't > finish the installation.
[SOLVED] Re: Debian bookworm fails to install
Hello! For those, who are interested in my discovering with bootcd, I attached a screenshot of the message, the installer told and why grub can not be installed. It might explain more. However, I suppose, there are not many people in the world, building a live-system + installer + bootcd on it and want to install this. I believe, the package bootcd is only known by very few people at all. But as we are always want to improve things, I feel it important, to tell about this problem. As I said before: Dunno, whom I should file a bugreport! Anyway, take a look at the picture and you know more. For me, it looks like a dependency problem Have fun! Hans
Re: NVidia 340 video driver in Bookworm?
Am Freitag, 7. Juni 2024, 22:29:30 CEST schrieb Van Snyder: Hi! Sadly to tell, that I treid hard to get 340.xx running in Bookworm. The problem is: You can not get it build with the actual kernel sources. I checked and the developers missed some dependencies, the NVidia driver needs at build time. You can get running it, if you are using an old kernel, like th eone from buster, maybe bullseye. In these kernels the dependencies and the libs, the sources are searching, are existent. However, maybe you can trick the build by adding the needed dependencies and things, the driver is searching. But I dunno, if this is a good idea. I also tried the orginal sources from nvidia.com, but here the same dependency problem appeared. In some former mails I asked the kernel developers for help, but there was no big interest in fixing things with closed source drivers (however, the kernel module is not closed source as far as I know). Most people are pointing to nouveau, but this is pita. Development in nouveau is also not much any more people told. Thus, with this old graphics card in linux is a problem, although they are in many notebooks people still use (I am running a Lenovo T520, several years old, but still fast enough). It has also a NVidia-card built in which needs 340.xx but I can not use it due to the lack of the kernel driver. Just a hint: Sometimes the nvidia-config module says, you need 340.xx, but this is not always true. My card (with th eolder kernel) was running 390.xx, although th esystem told me, I have to use 340.xx. 390.xx was running like a charm, 340.xx crashed. So it lied. Sorry, that I can help no further and for the bad news, but do not try too much - I fear, you will fail! Have a nice day! Hans > Has anybody been able to install the NVidia 340.108 video driver in > Debian 12? > > The messages I found said "Support for it ended in 2019. Use nouveau." > > But I seem to have trouble with nouveau. When I was running Debian 10 > on a Dell Vostro 1700 laptop with NVidia GeForce 8400M graphics, I had > been able to install the driver, and had no trouble. I made the mistake > of installing Debian 12.5 on the same partition, so I don't have the > Debian 10 install anymore. It freezes so completely that the keyboard > doesn't work, so I can't switch to a TTY screen. Even if I "ssh" to it > from my desktop, I can't kill and restart the graphics. I have a script > to restart KDE, but it does nothing. Even "init 3" doesn't do the > trick. I have to hold down the power key to reboot. I don't think it's > a hardware problem that amazingly manifested simultaneously with a new > install. > > Here's some too-late advice I've given to myself: Never blow away your > old install that appears to be working. If you don't have a new disk, > and you have room on the old one, make new boot and root partitions. > Mark only the new boot partition as the bootable one. Hook both boot > partitions to grub.
Re: [SOLVED] Re: Debian bookworm fails to install
Looks like a typo from me. apt-cache search grub-efi-amd | grep signed grub-efi-amd64-signed - GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) grub-efi-amd64-signed-template - GRand Unified Bootloader, Version 2 (Signaturvorlage für EFI-AMD64) It is grub-efi-amd64-signed. Sorry for that. I checked after install: If I want to install package bootcd after installation, no packages will be deinstalled, just several added. Not sure, what is the difference, between the installation process and the finished installation. Best Hans > > I can't find the package grub-efi-amd64-bin-signed. > Where should I look? > > Cheers, > David.
[SOLVED] Re: Debian bookworm fails to install
Got it! Found the reason and a fix for it. Just not easy to find. It is an dependency-problem! What happened? Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul exist in my live- system. During build this made no problems and all dependencies are ok. But - during install it appears, that there is a dependency conflict with the installer as bootcd needs grub-efi-amd64- bin. However, when bootcd wants to install, this package will be installed, too as it is dependent. So far, so well. BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed and forces it to deinstall, which, you guess it, the debian-installer needs. And so the grub-installer crashes! Now the question, who should be asked for help? Maintainers of bootcd? Maintainers of debian- installer? Or Maintainers of packages? I do not know, and as long as I do not know, I can not file a bugreport as none of them (and this is fully correct and understandable) is responsible from his sight on. However, the problem can easily be reproduced. Thanks for reading this, hope it helps. For me, this issue can be closed. Best regards Hans
Re: Debian bookworm fails to install
Am Freitag, 7. Juni 2024, 18:24:11 CEST schrieb Michael Kjörling: Hi Michael, > On 7 Jun 2024 18:01 +0200, from hans.ullr...@loop.de (Hans): > > For my own purposes I am building a live-debian ISO with installer. > > How are you doing this? I am starting with lb config (to get a straight live-build environment). After this I am edititing all entries in ~/config/bootstrap | binary | common from "bullseye" to "bookworm". At last I am editing the entry for the name of the image from "live-image" to "RustDesk-live- image" (I want it so be named). Then lb config --purge. After this, I am starting with my own shell script, which contents this line: ... lb config --purge lb config --debian-installer live --bootappend-live "boot=live username=myname hostname=my_hostname..." (keyboard definitions and so on) lb build This worked, but from one day to another no more, and this is strange! I also did a fresh live-build-environment installation, then it worked 3 or 4 times, and then it broke again. > > Can you post a script (or something similar) which reliably > demonstrates the issue when executed within a fresh Debian system? > The issue is not in the Debian itself, but it happens, when I want to install it. It happens as well on a native system as in Virtualbox itself. Maybe I could upload the ISO somewhere, it can be used in Virtualbox and shows the crash there, too. However, the ISO is 700MB and you need 8GB harddrive in Virtualbox. Think, not a goo idea. > > I also tried to install grub manually in the console during installation > > process, using "grub-installer /target", but this did neither work nor > > show > > much usefull information. > > Should we take this to mean that it did show _some_ "useful > information"? If so, what _did_ it show? No, it did not show any usefull information. Messages like "grub-installer failed" is no usefull information! No reason why... > > It appears that you are trying something; having some issue; see > symptoms; draw conclusions; and then tell us about your conclusions > and ask for a solution to your issue so as to be able to continue with > what you're trying to do. But without us being able to see what you > are doing and what happens when you do, _in full_, it's nearly > impossible to guess from your conclusions what might cause the issue > you're having in the first place. > Yeah, I know. If I got more information for myself, maybe I could find the reason for myself, too. But the installer does not show > Show us _exactly_ what's happening, as far as you are able. At a > minimum, make it easy for others to recreate a situation in which you > see the specific problem. > > In other words, a minimal (non)working example. At the moment, I try to use the installer from bullsyeye and the system of bookworm. It can be set in the live-build configurations. Maybe it is a problem with the debian-bookworm repo (mirroring in process, whatever) and tomorrow it will magiacally work again. So, I suppose, we should wait. I will try some things here and maybe I can fix it though. Thanks for help anyway. Best regards Hans
Debian bookworm fails to install
Hi folks, I am running into an issue, I can not explain. Let me please shortly describe: For my own purposes I am building a live-debian ISO with installer. As I am finetuning some things (not related to the system itself), I am building several ISOs a day. The live-build is set to bookworm (not bullseye, as lb config does). However, everything is going fine., the live-system is booting well. But: When I want to install it, the installer always breaks, when it wants to install grub. (grub-installer fails). As I am doing always a fresh install with completely formatting the harddrive, it can not be explained, why this happens. And more strange: When I build one version, it is working well. Changing nothing, and building again, suddenly the installer crashes at grub installation and then it will never work again. To declare: I can build several times, and every installation is working well, and suddenly without any reason, it breakes. Doing then using one version before (the last one, which worked well), it is still working, but the next build is crashing. Ok, I think you understood, what I meant. Well, one reason I could imagine, that the debian mirror, I add during installation process is changing. I am using "deb.debian.org", but when using another mirror in my near, I am running into the same issue. I also tried to install grub manually in the console during installation process, using "grub-installer /target", but this did neither work nor show much usefull information. Any idea, why this is happening? I saw similar messages in some forums, but they are all related to Debian 10, which is rather old (and I suppose, these bugs are fixed). Thanks for any hints and help! Best regards Hans
Re: Question About Free File Transfering Apps
rsync - which is biderectional and uses checksums for correct transfer. Best Hans
Re: *****SPAM***** Re: Uninstalling a package and its entourage
Am Montag, 27. Mai 2024, 17:51:23 CEST schrieb to...@tuxteam.de: > On Mon, May 27, 2024 at 04:59:55PM +0200, Nicolas George wrote: > > Eben King (12024-05-27): > > > Is there an easier way to uninstall a package and everything it brought > > > in > > > at one swell foop? Thanks. > > > > The packages you did not choose to install but were installed as a > > consequence are shown by apt-get when you do almost anything: > > > > The following packages were automatically installed and are no longer required: > > > > ...and there is `apt-get autoremove' for that. > > cheers You can also try: aptitude purge package_name and, maybe it is alrady deinstalle, you can purge any configurations: aptitude purge ~c Have fun! Hans
Re: moving some packages back to bookworm stable
Doing "apt-get upgrade" will only upgrade all installed packages, but no new ones (even, if they are needed). Better is to do an "apt-get full-upgrade", which will install the whole system from stable to testing. However, this might also uninstall some wanted packages, thus often it is calles the "intelligent" upgrade. Intelligent does not mean, the upgrade is intelligent, but the one doing this upgrade (mostly the person, who is root) should be intelligent. Downgrading is not an easy way, but managable. But it is a lot of intelligent work. How can you do this? This is, how I am figured out (best way for me!) First, remove the entry from stable off your sources.list. Then start aptitude and update the list. Next manually search all packages you want to downgrade to the needed versions. The last apt-get or aptitude log should help. Mark all installed versions to "remove" (magenta coluur) and needed versions to "install" (green colour). Now, dive manually into all dependencies (these are marked with the red coulour) and do the same as above (mark the installed version first "remove" then the correct as "install"). Important: Check that ALL dependencies are correct and no libs or anything else is set with red colour. This process must be done very, very correct! After this press "g" (which is for "install now") and if everything was set correct, all packages are now downgraded. Note: If you have missed something, you have to restart again! >From my experiences this doing so is still faster, than to setup a new system. Hope this helps. Good luck! Best Hans
live-build: what do live-task-* do?
Hello everyone, I am playing around with live-build. So I see several packages called "live-task-*" (for example live-task-xfce), but I can not see any changes in the live-build tree, when I install them or not. Checked through the manuals, but I found no information, what I have to do with it. Yes, live-task-xfce shall add XFCE to the live-build ISO, but I can not see any difference by adding just the entry "live-task-xfce" into the file "live.list.chroot" below ~/config/package.list and installing the package. What did I miss? Yes, I see, these are metapackages and want to install more packages (what I really NOT want on my building computer). The logic of this behaviour is not quite clear for me. I suppose, it shall show me and let me test, which packages are installed into the live-ISO. But if I do not want them on my building computer, I just need to add the entry into ~/config/package.list/live.list.chroot and it will work. Am I correct? Personally I think this is not a good way, as installing a package like task-live-xfce will install all xfce-packages,too. No good idea for several reasons. But someone might have good reasons for this. Whatever, the question is: What are these live-task-packages for and how shall they be handled correctly? Thank you for enlightening me! Best regards Hans
Will te UUID or blkid of a device change?
Hi folks, just aquestion. I am booting a lie system from USB-stick. In this live system I am creating an ISO-file, which I then want to dd onto another USB-stick. As I am doing this with a script, I want to make sure, that the correct USB- stick is used. Thus I can do by using the UUID of the target stick like dd if=/path/to/myfile.iso of=UUID="123456-abcd-" This is working. Now my question: Whenever I dd to the target stick, does the UUID change? I know, the UUID of the partitions are changing, but what is with the device itself? Or is there a better way? Maybe by using a label? I read also about blkid, but does this change, too when dd to the device? At all, is my idea possible at all or are ALL UUIDs changing, whenever I do a dd? If yes, then how can this be prohibited, if any. Thanks for any help. Best Hans
Re: Dell Vosto 1700 and NVidia
Try to use a configuration file /etc/X11/xorg.conf. Yes, I know, the modern drivers do not need it any more, but when you want to force some settings, this can help. I attach mine at this message, which was running fine so far and has all the settings inside, you might want to use. This file was used also with a NVidia card GF8400M. Please note, that when you need to run with the proprietrary driver (which is downloadable as package from debian/oldstable, you need to run an old kernel. Otherwise the kernel module will not build. The 340xx legacy driver is the correct one for this graphic chip. My experiences with the nouveau driver from the kernel ended with unstability and bad peformance. If everything crashes, you can still run the vesa driver, but try first 340xx. Oh yes, in the xorg.conf I send with, the driver must be named "nvidia", it is already set. You also need the dependend libgl-nvidia for this driver. Check the old repos from debian. Something else? Well, you can place the "xorg.conf" below /etc/X11/ or below / usr/share/X11/ . Hint: To test the xorg.conf uninstall all login-managers, like sddm, lightdm, kdm or gdm. I suggest, just move /usr/bin/kdm, /usr/bin/gdm, /usr/bin/lightdm and similar to another direcory, for example /root. Then boot and test with the command "startx". If X is starting, you are good, if not, you can see, what happens and if it starts, but hangs, you can stop X using either CTL+C or CTR+ALT+BACKSPACE. Hope this helps! Good luck, Hans > I have an old Dell Vostro 1700 running Debian Trixie. It has an NVidia > G86M (GeForce 8400M) graphics chip. I installed the NVidia 340 driver > (which is difficult to find). > > I attached a HP 14" monitor to the VGA socket. > > When I booted, it came up with side-by-side displays. I could move > windows from one to the other. > > When I closed the cover and re-opened it, instead of waking up, it re- > started X, but this time with displays mirrored. > > I ran nvidia-settings to move the HP monitor. It complained about not > being able to set a mode. I've tried many times since without success. > > I tried running the KDE Display Settings, but that put it into a > restart-X loop. > > Any ideas? > > Van Snyder Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection
mail tags in kmail?
Dear list, does anyone know, where kmail is storing its tags for mails? The tags I mean are those like "already read". Background: When I rsync the folder with my mails, which is here ~/.kde/ share/apps/kmail/mail , to another computer, then all new mails are tagged as "not read" on the target computer in kmail, although they were read on the source computer in kmail. Thus I believe, I did not rsync the tags, and they are stored somwhere else. Does one know where? I hope, it is not in akonadi, as this is to feasable to fiddly for me and implies too great danger to crash the whole thing. Thanks for any answer. Hans
Security hole in kernel fixed?
Dear developers, in April 2024 the security hole CVE-2023-6546 was discovered in linux-image, and I believe, it is fixed in kernel 6.1.0 (from debian/stable) as soon after this a new kernel was released. However, there is no new kernel 6.5.0-*-bpo released at that time, so my question: Does anyone know, if this fix was also integrated in kernel 6.5.0-*.bpo ? Thanks for your answer. Best Hans
Re: How to run automatically a script as soon root login
Am Montag, 13. Mai 2024, 13:24:17 CEST schrieb Greg Wooledge: > On Mon, May 13, 2024 at 07:36:07AM +0200, Richard wrote: > > .profile Sorry, dumb question: Depending of the shell, the user is using (let's say, he will use bash), can the script not be added into ~/.bashrc? If yes, second dumb question: Coiuld it be ANY script or command? (also running as non-rootuser, like adding "runuser -u myuser command_whatever"). Just some thoughts Best Hans
Re: Trouble/bug with initramfs-tools adding encrypted swap partition
Am Dienstag, 23. April 2024, 22:26:17 CEST schrieb Richard: Hi Richard, this is, what I am doing when this happens: 1. booting into a live system (any new is working, I prefer kali-linux) 2. If you are using encrypted filesystems, open it. But you have to name it like it is named in / etc/crypttab of the defective system 3. Now mount the device with root-filesystem to /mnt 4. If you have /boot as a separated partition, mount it to /mnt/boot 5. Now mount needed system directories to /mnt mount --bind /sys /mnt/sys mount --bind /proc /mnt/proc mount --bind /dev /mnt/dev 6. If everything is mounted correct, you can chroot into the mounted system chroot /mnt 7. Now you can create a new initrd update-initramfs -u 8. exit the chroot and reboot. Note: 1. if you have encrypted filesystems, check in the chroot the files /etc/crypttab /etc/cryptsetup-initramfs/conf-hook In conf-hook check the last line, the parm "ASKPASS=Y" should be commented out. 2. You can check the UUID of every partition with the command blkid /dev/sda1 and compare it with the entries in /etc/fstab, /etc/crypttab and everywhere else it is used. 3. In chroot, you can of course also create a new initrd, using update-initramfs -c -k all 4. Please remember, when you have encrypted partitions, then the UUID of the device is other, than the partitions, you later mount. Example: blkid /dev/sda3 UUID=1234556-dfre-3456. Now cryptsetup luksOpen /dev/sda3 crypt_sda3 blkid /dev/mapper/crypt_sda3 UUID=9876g54-765g-87hg Watch this, when changing any UUIDs in /etc/fstab or anywhere else. Last but not least: Hope this helps, good luck! Best Hans
Re: *****SPAM***** Marking as spam
Am Donnerstag, 18. April 2024, 17:21:41 CEST schrieb rtnetz...@windstream.net: To make clear: The first time I replied, I forgot to remove the spam tag. But the "Sorry" mail I did send without the spam tag. However, I get it WITH the spamtag, as all mails get the DCIM=false tag in the header (created by the debian servers) and megamailservers.eu add the SPAM tag. Those, who receive their mails on another way, are not affected, but I am. Thus, I get some mails from the debian list with SPAM tag and some without, depending how I received it. I can not fix this (as already described in another thread on this list here), so I had to create a whitelist rule in my spamrules. However, yes, you can expect from me, that I remove the SPAM tag, when I reply of mails. If I reply, I am not sure, if the spam tag is recreated, whilst the DCIM=false tag might be kept in the reply mails (did not examine this). Of course, I will watch to remove the spam tag when replying in the future. Promised! Best Hans > As I understand what he wrote, the SPAM tag is added after the message > leaves his control. > > - Original Message - > From: "Nicolas George" > To: "debian-user" > Sent: Thursday, April 18, 2024 11:13:44 AM > Subject: Re: *SPAM* Marking as spam [was: *****SPAM* Re: > LibreOffice removed from Debian] > Hans (12024-04-18): > > As I can not fix it > > You can manually remove “*SPAM*” from the mail when you reply. > > You could even automate it on your end.
Sorry
Am Donnerstag, 18. April 2024, 17:08:53 CEST schrieb Hans: Sorry, the spam tag appears because of DCIM in the header. Not my fault. Best Hans > Am Donnerstag, 18. April 2024, 11:53:38 CEST schrieb to...@tuxteam.de: > Hi Tomas, > > this is by debian servers, I talked about this for a while. Because the > debian servers mark some things in the header, megamailservers.eu mark them > as spam and add SPAM to the headline. > > As I can not fix it and debian admins will also not do, and I just answered > to the debian mail, you see the spam mark in the headline. > > I am no motre thinking of it, because everything was said in another theread > in this list. > > For myself I made a rule in spamassassin, that mails from debian are > whitelisted, although they are marked as spam and although they are > appearing with SPA in the headline - as I know, they are NO spam! > > Hope, this explains it. > > Best > > Hans > > > Hi, Hans > > > > is it your mail setup adding that *SPAM* decoration to the > > subject? > > > > Just curious... > > > > cheers
Re: *****SPAM***** Marking as spam [was: *****SPAM***** Re: LibreOffice removed from Debian]
Am Donnerstag, 18. April 2024, 11:53:38 CEST schrieb to...@tuxteam.de: Hi Tomas, this is by debian servers, I talked about this for a while. Because the debian servers mark some things in the header, megamailservers.eu mark them as spam and add SPAM to the headline. As I can not fix it and debian admins will also not do, and I just answered to the debian mail, you see the spam mark in the headline. I am no motre thinking of it, because everything was said in another theread in this list. For myself I made a rule in spamassassin, that mails from debian are whitelisted, although they are marked as spam and although they are appearing with SPA in the headline - as I know, they are NO spam! Hope, this explains it. Best Hans > Hi, Hans > > is it your mail setup adding that *SPAM* decoration to the > subject? > > Just curious... > > cheers
Re: *****SPAM***** Re: LibreOffice removed from Debian
I only hope, it will not happen the same fate like usermin and webmin happened to: It was once removed from the repoi with th ereason "spagehetti code, bad code" and then no one ever took a look again to it, although many, many years of coding passed by. And webmin and usermin are still developed! I suppose, it is much easier, to remove a package, than to fix it. Once removed, it will soon be forgotten. This is not mourning, please note, just things, I am just reflect my watchings. And for libreoffice I suppose, it is planned, to change from 7.6 to 24.4, which will be a major jump. Don't anger, if I do not find the correct Englisg idioms! Best Hans
[SOLVED] Re: config files - newline possible?
Hi Greg, ah, I wasn't aware of this. This is really great news! And it will help me much. You made my day! Thank you very much. Best regards Hans > On Thu, Apr 11, 2024 at 08:42:20PM +0200, Hans wrote: > > in my case it is the config freom from bootcdwrite, which is > > bootcdwrite.conf. > <https://manpages.debian.org/bookworm/bootcd/bootcdwrite.conf.5.en.html> > says: > > This file will be sourced as shell file. > > So, you may use any valid "shell" (presumably sh) syntax, including > backslash-newline for continuation.
Re: config files - newline possible?
Hi Tomas, in my case it is the config freom from bootcdwrite, which is bootcdwrite.conf. The parm is NOT_TO_CD and as there are many and partly long pathnames, the line has increased rather long. So I want to shorten it. But as it was said: there is no general way for this. So I just try some things out for this, and the next time again. Thought I have something missed, but does not look so. Thanks for all the help, I think this case caqn be closed. I will wait for one or two days and then mark this case as closed. Cheers Hans > As Nicolas George says, "config-file" is too generic a term. > If the above is a variable assignment, then you can escape the > newlines with a backslash, like so > > Do_not_write="path1/subfolder \ > path1/subfolder2 \ > ..." > > Note that the backslash has to be the last character in the > line. No extra whitespace after that (this is somewhat > fragile). I prefer to put such things in here docs: > > read -d '' Do_not_write <<"__END" > this > that > the other > __END > > echo "Do_not_write" > => > this > that > the other > > Put attention to the quotes. In bash, type "help read" to learn > about the options (it is a builtin, it has to). > > Cheers
config files - newline possible?
Hi folks, O know in shell scripts it is possible, to seperate a looong line of commands into several short lines. But can this be done in config-files, too? I have a files with the syntax like this: Do_not_write="/path1/subfolder /path1/subfolder2 ... /pathX/subfolderX" And as there are many paths, the line is very long. Is there aay, to make one line to several lines? In bash (I believe), it is a backslash sign, which leads to the next line, but does this also work in configuration files? Thanks for enlightening me. Best Hans
[SOLVED Re: network-priority?
Hi all, thank you for the fast response. Your answers did help much and made everything clear. Have a nice weekend! Best Hans
network-priority?
Hi folks, again an easy thing, I did not understand and where I did not find a clear answer in the web. Question: In network-manager I find "network-priority" set to "0". Is zero the highes priority or the lowest? Lets imagine, i have 3 wifi (wifi-1, wifi-2 and wifi-3). wifi-1 one should be the first, I want to connect, then wifi-2 and last wifi-3. How it is to set? wifi-1 = 0 wifi-2 = 1 wifi-2 = 2 or 2,1,0? Or are the numbers code for behaviour? (Here I think like numbers at files, where 577 = r-x,rwx,rwx) A short answer is very ok. Best Hans
Re: making Debian secure by default
Hello, personally I think, the best way is to plan, what you want to do with your system. What is its task. How secure it shall be. And then just think of: What can happen? For example: Can someone boot wirt an external medium? Do more than one people got admin rights? How do people access? Can the server be stolen? And so on. Make a list, do brainsorming with other people. Learn from other hacks. And then act for every point you made. Think, how can this and this and this attack be inhibited, how can it be noticed and is there an alarm and so on. For my personal experience, I never saw an attack in the past, which was not prepared. Before are runninng portscans or simple bruteforce attacks. Here I am talking of activists and script kiddies, not APT's. APT's are much more difficult to defend and to discover, they can, but very, very difficult. A good point to start is the doc "securing debian", and then, after you did this, think of, what you have forgotten and what did the docu not tell. IT-Security is no software, it is a process, and you will have to learn for years, which is normal. The attackers learn, the defenders, too. There is no straight, golden way, every server is different, and so are its defence. As I said, its a concept, and this can change during the years. Hope this helps a little bit. Best regards Hans
Re: Filsystemkorruption i ext4?
Hi Jesper, RAID 1 is mirroring. I suppose, a reason for the failure might be a timing problem. I do not know for sure, if yous system has got a real RAID-controller or if it is made by software. The real controller should not produce write errors, however maybe at heavy load it might happen. I never used RAID 1 myself, as I am a fancy guy and am no friend of RAID 1. It is just, when there is an error on one drive, it is on the other, too. My fancy solution was, using one drive and mirror this frequently every 30 minutes using rsync. IMO doing so, I have several options: 1. If the harddrive is defective, I can boot the other one. 2. If the software is defective, I have 30 minutes, to discover the failure (every good logging system should alarm this in time) 3. I have a running backup available. 4. I can exchange the defective harddrive during the running system. 5. After exchange, i can examine, what happened (hardware failure, malware, whatever). Many people will now laugh at me, but doing so, worked for me at best. So I reached an uptime of more than 700 days, but this might not be based on my work, but the work of all the debian developers! As I said before, i am not very experienced with RAID 1, other people might know much more. Personally I believe, RAID is mostly used with Windows, as Windows does not have these nice tools like rsync or syslog and all the things, that make linux and debian so great. Have a nice eastern! Best Hans > Sorry - I should have left more of the previous mails quoted. I have > previously tested the RAID1 consistency (ok), fixed the file system > (found 3 files with incorrect block count), and now also tested the > RAM.And since it seems unlikely that it is a bug in ext4 (in Debian > Bullseye), I don't quite understand how such an inconsistency can occur. > Thanks for your response, Jesper > > > If so, I suggest to boot a live system like Knoppix or similar, then run > > your test by using > > > > e2fsck -y /dev/sda1 > > > > or wherever your filesystem resides. > > > > Please pay attention: If you have encrypted filesystems, then first open > > the encryption, do NOT mount the filesystem and then check it, for > > example: > > > > cryptsetup luksOpen /dev/sda1 data1 > > > > then enter the password and now you can run > > > > e2fsck -y /dev/mapper/data1 > > > > Note: the word "data1" is only an example, you can name it, whatever you > > want like "space", "soap", "bullet", "henry" or whatever. > > > > Hope this helps. > > > > Best > > > > Hans > > > >> [Sorry - I accidentally sent this too quickly in an incomplete state. > >> Second try here:] > >> > >>> On Wed, Mar 20, 2024, 11:28 AM Jesper Dybdal > >>> > >>> wrote: > >>> I think I'll let memtest86+ run overnight one of the coming nights. > >>> > >>> Unless it is simply a RAM error, then it is a bit scary... > >> > >> I've now let memtest86+ run for 9 hours, during which it did 14 passes > >> of all its tests. It found nothing wrong. > >> > >> On 2024-03-20 22:58, Nicholas Geovanis wrote: > >>> I have seen that a couple times, unlikely but possible. Maybe review > >>> your RAM configuration too, ensure that the sticks are on the same > >>> supported refresh rate and distributed across the slots in an approved > >>> way. > >> > >> There is only one RAM stick (of 16 GB), so there should be no problems > >> of that kind. > >> > >> I'm afraid I won't find an explanation of that file system corruption :-( > >> > >> Thanks to Franco and Nicholas for your responses, > >> Jesper
Re: Filsystemkorruption i ext4?
Am Donnerstag, 28. März 2024, 14:49:37 CET schrieb Jesper Dybdal: Hello, memtest86+ is for testing RAM, but do you not want to test ext4 filesystem? If so, I suggest to boot a live system like Knoppix or similar, then run your test by using e2fsck -y /dev/sda1 or wherever your filesystem resides. Please pay attention: If you have encrypted filesystems, then first open the encryption, do NOT mount the filesystem and then check it, for example: cryptsetup luksOpen /dev/sda1 data1 then enter the password and now you can run e2fsck -y /dev/mapper/data1 Note: the word "data1" is only an example, you can name it, whatever you want like "space", "soap", "bullet", "henry" or whatever. Hope this helps. Best Hans > [Sorry - I accidentally sent this too quickly in an incomplete state. > Second try here:] > > > On Wed, Mar 20, 2024, 11:28 AM Jesper Dybdal > > > > wrote: > > I think I'll let memtest86+ run overnight one of the coming nights. > > > > Unless it is simply a RAM error, then it is a bit scary... > > I've now let memtest86+ run for 9 hours, during which it did 14 passes > of all its tests. It found nothing wrong. > > On 2024-03-20 22:58, Nicholas Geovanis wrote: > > I have seen that a couple times, unlikely but possible. Maybe review > > your RAM configuration too, ensure that the sticks are on the same > > supported refresh rate and distributed across the slots in an approved > > way. > > There is only one RAM stick (of 16 GB), so there should be no problems > of that kind. > > I'm afraid I won't find an explanation of that file system corruption :-( > > Thanks to Franco and Nicholas for your responses, > Jesper
[SOLVED] Re: variables in bash
Hi, thank you all for the fast response. It helped a lot and made everything clear. The problem is solved. Have a nice eastern. Best Hans
variables in bash
Hi folks, just an easy question: What is the difference (if any) between the following two variables in a shellfile in bash: 1. mypath=/home/user1/Tools/ and $mypath or 2. mypath="/home/user1/Tools/" and $mypath Is this in bash the same? Do other shells (sh, zsh, whatever) handle these two different? Thanks for any answer, can be short! Best regards Hans
