April 2023 - openSUSE Users - openSUSE Mailing Lists

Re: four or maybe six modules
by Per Jessen 01 Apr '23

01 Apr '23

gebser(a)mousecar.com wrote: > It's been a very long time since I messed with modules. And I never > enjoyed running insmod or modprobe and then-- probably-- having to run > rmmod... and that was back when there were four or maybe six modules > to deal with. Now we have > > # lsmod|wc -l > 177 Here only 71 with the latest TW (i586). Only 59 on a Raspi. On the openSUSE mailing list server, only 40. There are also times when modules are loaded unnecessarily. I think even the 2.2 series kernel had more than four or five modules :-) Much will depend on what you do with your Linux systems, how many you have and how varied they are. How much you dabble with the hardware. -- Per Jessen, Zürich (15.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

4 10

[oS-en] Hardware "bug" on Lenovo L14 Gen 3 AMD laptop.
by Carlos E. R. 01 Apr '23

01 Apr '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When the machine is sleeping 8aka suspend to ram), if I connect or disconnect the mains, the machine awakes, even if the lid is closed (Leap 15.5). Andrei posted some reading material that mentioned inhibiting some events from waking the machine, so I definitely have to explore that. But just mentioning the issue here so it is known. - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCgsKxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVL4wAn0X/vCRjfEKW0J1dFqc7 f41yXlgKAJ9RmiEeE0FcINsxU3gSI0wqi0Rppw== =b6mH -----END PGP SIGNATURE-----

1 0

Re: Heads up: removing the mkinitrd wrapper
by Per Jessen 01 Apr '23

01 Apr '23

Carlos E. R. wrote: > On 2023-03-30 18:42, Per Jessen wrote: >> Carlos E. R. wrote: >> >>> Or, copy the old script to /usr/local/sbin, unless that is not >>> advisable. >> >> Or - oh horror - move with the times. > > I think I'm entitled to be recognized as an old fart by now :-p I'm sure you are, but does that prevent you from moving with the times? >> I still think the main point is that you don't actually dabble with >> building initrds yourself, you are happy to follow instructions to do >> so, when needed. In the future, no one is going to direct you to run >> mkinitrd, so what is the point of having an alias. > > Per, > > You may have read from me and Andrei the multiples scenarios in which > people have to run mkinitrd manually. I have been in most of them. No, I have totally missed that. I thought you were talking about having to create initrds manually. For the last couple of years, I have not been in a single situation where I _had_ to run mkinitrd. dracut was very useful though. -- Per Jessen, Zürich (16.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

7 11

Re: [oS-EN] Question on full disk encription
by David C. Rankin 01 Apr '23

01 Apr '23

On 3/28/23 08:01, cagsm wrote: > On Tue, Mar 28, 2023 at 12:42 PM Carlos E. R. > <robin.listas(a)telefonica.net> wrote: >> new laptop here, and I decided to install Leap 15.4 with full disk >> encryption, no LVM (a feature I wanted to have for years, so I'm happy). >> It asks for the password twice (contrary to my customs, I'm using plymouth). >> It asks once before grub loads. Well, ok, there is no separate /boot, so >> it has to read "/" which is encrypted. Nice. >> But after selecting the boot entry in grub, it asks again. Once, despite >> being 3 partitions ("/", "/boot" and swap). Ok. > > doesnt the official opensuse pages state about the situation about > double entry of passphrases. i have double passphrase questionaire as > well with 15.4 fresh install via the propsed partition setup on a > notebook. btrfs or something and the snapshot filesystem stuff and > all. not expert though > >> <https://en.opensuse.org/SDB:Encrypted_root_file_system#Avoiding_to_type_the…> The page says: <quote> Warning: Do this only if you have an encrypted root partition **that includes /boot** (no separate /boot partition)! The key added to the initrd can be used to decrypt your root partition, therefore having the initrd on an unencrypted /boot partition would defeat encrypting your root partition. </quote> How do you handle the case of a separate /boot partition? -- David C. Rankin, J.D.,P.E.

4 10