Requests for -current (14.2-->15.0)

USUARIONUEVO · 09-26-2018, 03:10 PM

Thunar-1.8.2
https://archive.xfce.org/src/xfce/th...-1.8.2.tar.bz2

USUARIONUEVO · 09-26-2018, 04:18 PM

sqlite-3.25.2
https://www.sqlite.org/2018/sqlite-src-3250200.zip

gmgf · 09-27-2018, 12:41 AM

hplip-2.18.9:

https://developers.hp.com/hp-linux-i.../release_notes
https://sourceforge.net/projects/hpl...-3.18.9.tar.gz

rust-1.29.1:

https://static.rust-lang.org/dist/ru...9.1-src.tar.gz

gmgf · 09-27-2018, 01:26 PM

apr-1.6.5:

http://www.apache.org/dist/apr/CHANGES-APR-1.6
http://apache.mirrors.ovh.net/ftp.ap...r-1.6.5.tar.gz

franzen · 09-27-2018, 01:58 PM

Hi,
i just installed -current on a new Acer Extensa laptop, and eliloconfig failed. Cause is the Acer Efi, it doesn't honor /boot/efi/EFI/Slackware, only /boot/efi/EFI/boot is working, where elilo.efi needs to be renamed to bootx64.efi.
I made a patch which makes it more easy when upgrading to a newer kernel, where the usage is: BROKEN_EFI=yes eliloconfig

Code:

--- eliloconfig.orig	2018-09-27 18:20:08.625000000 +0200
+++ eliloconfig	2018-09-26 19:41:43.437456374 +0200
@@ -29,6 +29,13 @@
 # The EFI System Partition is expected to be mounted on /boot/efi before
 # running this script.
 
+if [ -n "$BROKEN_EFI" ]; then
+  MENU_DIR=boot
+  LOADER=bootx64.efi
+else
+  MENU_DIR=Slackware
+  LOADER=elilo.efi
+fi
 TMP=/var/log/setup/tmp
 
 # Set the OS root directory (called T_PX for some unknown reason).
@@ -125,28 +132,28 @@
   exit
 fi
 
-mkdir -p $T_PX/boot/efi/EFI/Slackware 1> /dev/null 2> /dev/null
-cat << EOF > $T_PX/boot/efi/EFI/Slackware/elilo.conf
+mkdir -p $T_PX/boot/efi/EFI/$MENU_DIR 1> /dev/null 2> /dev/null
+cat << EOF > $T_PX/boot/efi/EFI/$MENU_DIR/elilo.conf
 chooser=simple
 delay=1
 timeout=1
 #
 EOF
-cp -a $T_PX/boot/elilo-x86_64.efi $T_PX/boot/efi/EFI/Slackware/elilo.efi 1> /dev/null 2> /dev/null
-cp $T_PX/boot/vmlinuz $T_PX/boot/efi/EFI/Slackware 1> /dev/null 2> /dev/null
-cat << EOF >> $T_PX/boot/efi/EFI/Slackware/elilo.conf
+cp -a $T_PX/boot/elilo-x86_64.efi $T_PX/boot/efi/EFI/$MENU_DIR/$LOADER 1> /dev/null 2> /dev/null
+cp $T_PX/boot/vmlinuz $T_PX/boot/efi/EFI/$MENU_DIR 1> /dev/null 2> /dev/null
+cat << EOF >> $T_PX/boot/efi/EFI/$MENU_DIR/elilo.conf
 image=vmlinuz
         label=vmlinuz
 EOF
-touch -r $T_PX/boot/vmlinuz $T_PX/boot/efi/EFI/Slackware/vmlinuz
+touch -r $T_PX/boot/vmlinuz $T_PX/boot/efi/EFI/$MENU_DIR/vmlinuz
 if [ -r $T_PX/boot/initrd.gz ]; then
-  cp $T_PX/boot/initrd.gz $T_PX/boot/efi/EFI/Slackware 1> /dev/null 2> /dev/null
-  touch -r $T_PX/boot/initrd.gz $T_PX/boot/efi/EFI/Slackware/initrd.gz
-  cat << EOF >> $T_PX/boot/efi/EFI/Slackware/elilo.conf
+  cp $T_PX/boot/initrd.gz $T_PX/boot/efi/EFI/$MENU_DIR 1> /dev/null 2> /dev/null
+  touch -r $T_PX/boot/initrd.gz $T_PX/boot/efi/EFI/$MENU_DIR/initrd.gz
+  cat << EOF >> $T_PX/boot/efi/EFI/$MENU_DIR/elilo.conf
         initrd=initrd.gz
 EOF
 fi
-cat << EOF >> $T_PX/boot/efi/EFI/Slackware/elilo.conf
+cat << EOF >> $T_PX/boot/efi/EFI/$MENU_DIR/elilo.conf
         read-only
         append="root=$ROOT_DEVICE vga=normal ro"
 EOF
@@ -198,7 +205,7 @@
   efibootmgr -q -B -b $(echo $line | cut -b5-8)
 done
 
-efibootmgr -q -c -d $EFI_DEVICE -p $EFI_PARTITION -l "\\EFI\\Slackware\\elilo.efi" -L "Slackware"
+efibootmgr -q -c -d $EFI_DEVICE -p $EFI_PARTITION -l "\\EFI\\$MENU_DIR\\$LOADER" -L "Slackware"
 
 efibootmgr -v | rev | cut -f 2- | rev | grep Boot0 | grep Slackware | while read line ; do
   # Reject entries that don't exactly match as not our business
@@ -206,7 +213,7 @@
     continue
   fi
   ENTRY="$(efibootmgr -v | grep "^$(echo $line | cut -b1-8)")"
-  if echo $ENTRY | grep -q -F "\EFI\Slackware\elilo.efi" ; then
+  if echo $ENTRY | grep -q -F "\EFI\$MENU_DIR\$LOADER" ; then
   dialog --title "EFI BOOT ENTRY INSTALLED" \
   --backtitle "ELILO (EFI Linux Loader) installation" \
   --msgbox "A Slackware boot entry has been installed to your EFI boot

Johannes

volkerdi · 09-27-2018, 02:09 PM

Quote:

Originally Posted by franzen

Hi,
i just installed -current on a new Acer Extensa laptop, and eliloconfig failed. Cause is the Acer Efi, it doesn't honor /boot/efi/EFI/Slackware, only /boot/efi/EFI/boot is working, where elilo.efi needs to be renamed to bootx64.efi.

Let me guess though - it honors /EFI/Microsoft just fine, right? I wonder how it likes /EFI/redhat, which is the location where they put their bootloader.

I suspect that this firmware is not properly following the UEFI spec. If I ordered such a machine, I would probably return it.

franzen · 09-27-2018, 04:17 PM

Quote:

Originally Posted by volkerdi

Let me guess though - it honors /EFI/Microsoft just fine, right? I wonder how it likes /EFI/redhat, which is the location where they put their bootloader.

I did test that, /EFI/Microsoft and /EFI/redhat both don't work.

Quote:

I suspect that this firmware is not properly following the UEFI spec.

It seems it forgets about that efi menu which lists Slackware after eliloconfig, but after a reboot:

Code:

root@darkstar:~# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,2001,2002,2003
Boot0000* Linpus lite	HD(1,GPT,6588d04a-9404-471d-947b-d685d34a1607,0x800,0x95801)/File(\EFI\BOOT\BOOTX64.EFI)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

Linpus Linux was preinstalled as i ordered the machine without windows.

Quote:

If I ordered such a machine, I would probably return it.

It's messy, yes, but it was affordable and will do good enough for my parents.
Still, there might be a lot of messy efi firmwares around, so i thought about suggesting the patch.

Didier Spaier · 09-27-2018, 04:38 PM

As an aside other firmwares also seem to only allow booting via the Simple File Protocol and furthermore use the Removable Media Boot Behavior even for a non-removable media, hence only accept the default path \EFI\BOOT\{machine type shortname}.EFI, in case of x64 \EFI\BOOT\BOOTx64.EFI

We can just hope that the specification will be less partially implemented by firmware providers over time...

volkerdi · 09-27-2018, 07:02 PM

Quote:

Originally Posted by Didier Spaier

As an aside other firmwares also seem to only allow booting via the Simple File Protocol and furthermore use the Removable Media Boot Behavior even for a non-removable media, hence only accept the default path \EFI\BOOT\{machine type shortname}.EFI, in case of x64 \EFI\BOOT\BOOTx64.EFI

So the thing to put at \EFI\BOOT\BOOTX64.EFI would probably be rEFInd, eh?

Didier Spaier · 09-27-2018, 11:37 PM

Quote:

Originally Posted by volkerdi

So the thing to put at \EFI\BOOT\BOOTX64.EFI would probably be rEFInd, eh?

If we want multi-boot with such a limited firmware that could be it, as it is able to scan its environment to find the OS loaders every time it starts, or more generally a boot manager able to handle multi-boot internally. So that could be grub as well or even elilo (if we accept its limitations) as both are able to read a config file at startup to find the OS loaders or load the OS themselves (that can have changed since last boot). But not an EFI stub, for instance, unless we accept to recompile the kernel every time we want to change the command line and run only one system

With such a firmware another possibility is to actually put the OS loader in the ESP of a removable device, but then you'd need one (say, an USB stick) for each system you want to start.

As an aside all these multi-boot boot managers are actually doing the firmware's boot menu job...

gmgf · 09-28-2018, 12:32 AM

Again, new librsvg-2.44.6:

http://ftp.gnome.org/pub/gnome/sourc...vg-2.44.5.news
http://ftp.gnome.org/pub/gnome/sourc...vg-2.44.6.news
http://ftp.gnome.org/pub/gnome/sourc...-2.44.6.tar.xz

SCerovec · 09-28-2018, 01:38 AM

Quote:

Originally Posted by Didier Spaier

If we want mulii-boot with such a limited firmware that could be it, as it is able to scan its environment to find the boot loaders every time it starts, or more generally a boot manager able to handle multi-boot internally. So that could be grub as well or even elilo (if we accept its limitations) as both are able to read a config file at startup to find the OS loaders or load the OS themselves (that can have changed since last boot). But not an EFI stub, for instance, unless we accept to recompile the kernel every time we want to change the command line and run only one system

With such a firmware another possibility is to actually put the OS loader in the ESP of a removable device, but then you'd need one (say, an USB stick) for each system you want to start.

As an aside all these multi-boot boot managers are actually doing the firmware's boot menu job...

rEFInd has even some sanity checks during it's run time, and quite extensive set of rules in the config file on the EFI partition.

shastah · 09-28-2018, 04:44 PM

eudev installs 64-btrfs.rules without substituting @rootbindir@ placeholder, so kernel complains:

Code:

[   15.232446] udevd[856]: failed to execute '/lib/udev/@rootbindir@/udevadm' '@rootbindir@/udevadm trigger -s block -p ID_BTRFS_READY=0': No such file or directory

Fix is here: https://github.com/gentoo/eudev/comm...5fb3e6e518474d

dchmelik · 09-29-2018, 12:06 AM

Quote:

Originally Posted by Alien Bob

Do I hear a grudging approval of Plasma 5?

Darth Vader had said its KATE is good for developing. Yes and no. It has many additions/improvement, but lost the tab bar I preferred, which was buggy anyway. The one left is just inadequate, so I've switched to NotepadQQ.

I've tried KDE5 several times over the last three years or so that you've made testing releases, and every time, I've switched back to KDE4, not because I don't like new things, but because KDE5 just seems inadequate. It never could handle as big a load of files/programs open at once as KDE4, and after some hours or days, the panel or kicker always ends up freezing so no more input is possible even for tens of minutes. Sometimes it's just from running as many programs as KDE4 can easily handle, or sometimes it's from opening several large images in GIMP or Inkscape that might use up almost or barely over half my 64GB RAM. So far I think KDE5 would just not be usable. It might work okay on other distros for average users such as my parents use, but of course, they don't have as many programs open as me... if they did, I'd guess they have the exact same problems.

Alien Bob · 09-29-2018, 04:21 AM

dchmelik, did you raise bug reports for these issues with large numbers of open files, and/or large file editing?
If there are no bug reports with details provided by knowledgeable users, no developer will ever know that something needs fixing.