Requests for current-next (15.0-->15.1)

marav · 06-10-2023, 04:19 AM

KDE Frameworks 5.107.0

Announcements:
https://kde.org/announcements/frameworks/5/5.107.0/

reddog83 · 06-10-2023, 11:25 AM

GJS 1.76.1

Quote:

Version 1.76.1
--------------

- Various fixes ported from the development branch.

- Closed bugs and merge requests:
* gnome-shell crashes on exit in js::gc::Cell::storeBuffer [#472, !834, Daniel
van Vugt]
* Memory leak with GError [#36, !837, Marco Trevisan]
* GVariant return values leaked [#499, !837, Marco Trevisan]
* GBytes's are leaked when passed as-is to a function [#539, !837, Marco
Trevisan]
* Transformated GValues are leaking temporary instances [#540, !837, Marco
Trevisan]
* GHash value infos are leaked [#541, !837, Marco Trevisan]
* "flat" arrays of GObject's are leaked [#542, !837, Marco Trevisan]
* Gjs console leaks invalid option errors [#544, !837, Marco Trevisan]
* gjs can't print null [#545, !841, Angelo Verlain]

https://download.gnome.org/sources/g...-1.76.1.tar.xz
https://download.gnome.org/sources/g...76.1.sha256sum

allend · 06-12-2023, 08:47 AM

A couple of outstanding minor nits with the ntp package that I would like to see addressed.
1. A typo in etc/ntp.conf.new

Code:

# Sample /etc/ntp.conf:  Configuration file for ntpd.
 
 #
 # Undisciplined Local Clock. This is a fake driver intended for backup
 # and when no outside source of synchronized time is available. The
 # default stratum is usually 3, but in this case we elect to use stratum
-# 0. Since the server line does not have the prefer keyword, this driver
+# 10. Since the server line does not have the prefer keyword, this driver
 # is never used for synchronization, unless no other other
 # synchronization source is available. In case the local host is
 # controlled by some external source, such as an external oscillator or
 # another protocol, the prefer keyword would cause the local host to
 # disregard all other synchronization sources, unless the kernel
 # modifications are in use and declare an unsynchronized condition.
 #
 server	127.127.1.0	# local clock
 fudge	127.127.1.0 stratum 10

as first suggested here.

2. Amendment of etc/logrotate.d/ntp.new

Code:

     missingok
     rotate 4
     postrotate
-    [ -x /etc/rc.d/rc.ntpd ] && /etc/rc.d/rc.ntpd restart
+    ! [ -x /etc/rc.d/rc.ntpd ] || /etc/rc.d/rc.ntpd restart
     endscript
 }

as discussed here.

dchmelik · 06-12-2023, 07:59 PM

Quote:

Originally Posted by marav

/sbin/upgradepkg, L 109
[...] ROOT=/some/path upgradepkg ....

What I meant then is it'd be good it installpkg, removepkg, upgradepkg could all do '<command> --root' and 'ROOT=/path <command>'.

UrbanDesimator · 06-12-2023, 10:49 PM

Quote:

Originally Posted by Jeebizz

For 15.1 would it be feasible, and not too complicated to have the installer give you the choice to install LILO or GRUB , or ELILO or GRUB (in UEFI mode) ?

Just my 2 penith.
I think that advanced users will just skip lilo and elilo if they use grub2 and drop to shell at installer end and setup grub2 to their liking.

I think that how Pat and the team keep often some of most important parts very simple with limited options. Giving new users/novice's a much easier install and higher probability of successful install, if your legacy boot use lilo, or uefi boot use elilo.

Most people tying Slackware in 2023 will have at least 1 other device with internet access to get info/help to make the right choices.

My first install went great in 1999 I followed all instructions which were nice and simple I have the Pentium2 pc booting and getting to login. But I had no idea and wasnt included in the instructions what username to login with. Totally stumped me I tried all sorts admin user poweruser I came from win98, it took 2 weeks to get the answer as I had wiped win98 from my harddrive with no CD "funny shiny round things" to reinstall win98. I had to wait for a friend of my dads to post me his spare cd. then wipe slackware reinstall win98 use dial up modem to get on internet and search for the answer and was gobsmacked when it was root lol.
I have a USB drive and DVD's with cuurrent iso's on just incase.

Any way just my thoughts
UrbanDesimator

LuckyCyborg · 06-13-2023, 05:32 AM

Quote:

Originally Posted by UrbanDesimator

Just my 2 penith.
I think that advanced users will just skip lilo and elilo if they use grub2 and drop to shell at installer end and setup grub2 to their liking.

I think that how Pat and the team keep often some of most important parts very simple with limited options. Giving new users/novice's a much easier install and higher probability of successful install, if your legacy boot use lilo, or uefi boot use elilo.

Most people tying Slackware in 2023 will have at least 1 other device with internet access to get info/help to make the right choices.

It's not true that LILO and/or ELILO gives a simpler handling of bootloader(s) ...

In fact, there's no script made for GRUB2, something named grub2config

How I for one I see the logic of a grub2config ?

First page, a dialog to chose if the GRUB2 will be installed in legacy BIOS mode and/or UEFI mode. Or both, when it's available (and used) the UEFI mode.

Second page, if it's chosen (also) the legacy mode, to ask where to install the bootloader. In MBR or in a partition. Additionally, when it's used GPT, to ask which partition will be used to install the stage2 of GRUB2 . Meaning 2 input lines.

Third page, if it's chosen (also) the UEFI mode, to ask if the bootloader will be installed in "removable" mode (/EFI/BOOT/BOOTX64.EFI with no UEFI list entry) or not (/EFI/SLACKWARE/GRUBX64.EFI) and the associated ID, which means usually SLACKWARE.

Fourth page, with options of configuration: TIMEOUT, enable (or not) the RECOVERY entries, the usage (or not) of UUIDs (I've seen people freaking out when they see them) . I for one I would prefer to have also a option for SAVEDEFAULT - it's very useful for me that GRUB2 can remember the last used boot entry.

Fifth page, for additional parameters to pass to default and the other kernels. Meaning 2 input lines, with optional content.

Finally, the summary page and the installation per se.

A logic like this covers both the UEFI and legacy BIOS modes. No need to learn 2 types of configuration - one for each bootloader, no need to copy files around, no need to touch again the UEFI partition unless you upgrade GRUB2, no need to manually handle the initrd configuration on bootloader, etc.

In fact, does not matter what me or you did 30 years ago. IF we dare to think a bit out of box, the GRUB2 is a simpler solution (as user handling) than the ancient bootloaders abandoned even by their fathers 9 years ago.

saxa · 06-13-2023, 08:54 AM

How one should contribute to the slackware installer ? Is it sending the patch here or if I want to develop a new module (BTRFS) ho should I start submitting it for inclussion ?

I think we could stick with a default partitioning scheme too, this would facilitate to the user (especilally the not expert ones) a suggested partitioning scheme or a default one.

GazL · 06-13-2023, 08:56 AM

Did GRUB2 ever get around to adding LUKS2/Argon2 support, or is that still an issue?

Didier Spaier · 06-13-2023, 09:51 AM

Quote:

Originally Posted by GazL

Did GRUB2 ever get around to adding LUKS2/Argon2 support, or is that still an issue?

Support for the LUKS2/Argon2 with the PBKDF2 key derival function has been provided since commit 365e0cc3.

Not sure about the Argon2i and Argon2id key derival functions though (I just asked on the ML). As an aside Daniel Kiper posted yesterday "I am going to do code freeze this week."

LuckyCyborg · 06-13-2023, 11:18 AM

Quote:

Originally Posted by GazL

Did GRUB2 ever get around to adding LUKS2/Argon2 support, or is that still an issue?

BUT, did LILO and ELILO have a proper support for LUKS2/Argon2 ?

I ask this because seems that we demand GRUB2 to be a ballistic missile with a precision of 10m on targets at 15000 km, when the alternatives are a crossbow and a sledgehammer.

LuckyCyborg · 06-13-2023, 11:21 AM

Quote:

Originally Posted by saxa

How one should contribute to the slackware installer ? Is it sending the patch here or if I want to develop a new module (BTRFS) ho should I start submitting it for inclussion ?

I think we could stick with a default partitioning scheme too, this would facilitate to the user (especilally the not expert ones) a suggested partitioning scheme or a default one.

I guess that the best way is to post your patches in a thread of this forum - I am not aware about a GIT repository of Slackware where you can send pull requests.

Regarding a default partitioning scheme, probably is better to avoid them. There are and (in the past was even more) people who worked in this kind of thing, and they said that when the installer starts to make decisions on behalf of user, the users expect the installer to think like a human.

GazL · 06-13-2023, 12:53 PM

Quote:

Originally Posted by LuckyCyborg

BUT, did LILO and ELILO have a proper support for LUKS2/Argon2 ?

ELILO is completely self-contained within its directory of the EFI partition so it doesn't care what the rootfs is on. It's only grub2 that tries to read stuff from the rootfs.

Didier Spaier · 06-13-2023, 01:13 PM

Quote:

Originally Posted by LuckyCyborg

Regarding a default partitioning scheme, probably is better to avoid them. There are and (in the past was even more) people who worked in this kind of thing, and they said that when the installer starts to make decisions on behalf of user, the users expect the installer to think like a human.

The Slint installer let the user choose between a default partitioning scheme (taking over a whole drive) called "auto partitioning mode" and a "manual partitioning mode", because why not?

The template is simple: an ESP, a BIOS Boot partition and the main partition formatted with BTRFS with two sub-volumes: one for / and one for /home. But if the drive is big enough users may add an additional partition in it (also BTRFS formatted). They are also allowed to include in /etc/fstab partitions on other drives, of type Linux on Windows, as in "manual" mode.

LuckyCyborg · 06-13-2023, 01:31 PM

Quote:

Originally Posted by GazL

ELILO is completely self-contained within its directory of the EFI partition so it doesn't care what the rootfs is on. It's only grub2 that tries to read stuff from the rootfs.

IF you want a standalone GRUB2 EFI binary which does not read stuff from rootfs, there's grub-mkstandalone even in Slackware.

It can generates a big EFI binary which contains everything, where you can include an initial (and small) configuration file, looking to final config file installed along with the grubx64.efi or any other place, according with your taste.

If you wish, you can make a /EFI/Slackware/grubx64.efi which look for config file as /EFI/Slackware/grub.cfg, then to use kernels from the same directory.

This grub-mkstandalone can generate another types of GRUB2 binaries, but I for one I have tested only the 64bit UEFI target.

LuckyCyborg · 06-13-2023, 01:50 PM

Quote:

Originally Posted by Didier Spaier

The Slint installer let the user choose between a default partitioning scheme (taking over a whole drive) called "auto partitioning mode" and a "manual partitioning mode", because why not?

The template is simple: an ESP, a BIOS Boot partition and the main partition formatted with BTRFS with two sub-volumes: one for / and one for /home. But if the drive is big enough users may add an additional partition in it (also BTRFS formatted). They are also allowed to include in /etc/fstab partitions on other drives, of type Linux on Windows, as in "manual" mode.

And for the people who does not like BTRFS, but the ol'good EXT4FS, what solution you have?

Don't tell me that's an "advanced" demand from the user.