LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-22-2019, 05:54 PM   #2701
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,107

Rep: Reputation: 329Reputation: 329Reputation: 329Reputation: 329

httpd-2.4.38

sources --> http://www.apache.org/dist/httpd/httpd-2.4.38.tar.bz2
changes --> http://www.apache.org/dist/httpd/CHANGES_2.4.38

read changes, some CVE FIXES
CVE-2019-0190
CVE-2018-17189
CVE-2018-17199
 
Old 01-22-2019, 09:47 PM   #2702
Nobby6
LQ Newbie
 
Registered: Jul 2012
Posts: 16

Rep: Reputation: Disabled
Apache httpd 2.4.38 is released

http://httpd.apache.org/download.cgi#apache24
 
Old 01-24-2019, 03:31 AM   #2703
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,779

Rep: Reputation: Disabled
Thumbs up

Code:
Wed Jan 23 22:02:34 UTC 2019
...
a/mkinitrd-1.4.11-x86_64-9.txz:  Rebuilt.
  Automatically generate an initial ramdisk from the installer.
  Added 'geninitrd' script to generate an initial ramdisk for the kernel that
  /boot/vmlinuz-generic (and/or /boot/vmlinuz-generic-smp) points to.
Very nice, huge thanks!

Maybe in a not-so-distant future we can get rid of the huge kernel and have the initrd automatically generated after each upgrade of the kernel shipped by Slackware?

Last edited by Didier Spaier; 01-24-2019 at 03:34 AM.
 
1 members found this post helpful.
Old 01-24-2019, 05:19 AM   #2704
GazL
Senior Member
 
Registered: May 2008
Posts: 4,952
Blog Entries: 15

Rep: Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559Reputation: 2559
Quote:
Originally Posted by Didier Spaier View Post
Maybe in a not-so-distant future we can get rid of the huge kernel and have the initrd automatically generated after each upgrade of the kernel shipped by Slackware?
It would probably be quite easy to turn geninitrd into a geninitrds and have it mkinitrd for each bzImage file that doesn't have a corresponding initrd file. I already do something similar here, but tailored to how I layout my EFI partition.

Code:
#!/bin/bash
#
#  Copy initrd and vmlinuz files to the UEFI partition for the
#  ELILO bootloader.  Generate the initrd file with mkinitrd if
#  it does not yet exist.
#

do_update()
{
  # Some minimal sanity checks:
  if [ ! -f "$bzImage_file" ]; then
    echo "  error: $bzImage_file is not a file." >&2
    return 1
  fi
  if [ ! -d "$elilo_dir" ]; then
    echo "  error: $elilo_dir is not a directory" >&2
    return 1
  fi
  if [ ! -d "/lib/modules/$kversion" ]; then
    echo "  error: missing kernel modules directory: /lib/modules/$kversion" >&2
    return 1
  fi

  # Generate an initrd if missing:
  if [ ! -e "$initrd_file" ]; then
    echo "  building initrd: $initrd_file"
    mkinitrd -F -c -k "$kversion" -o "$initrd_file" >/dev/null
  fi

  # Update/install elilo kernel files:
  echo "  copying files to $elilo_dir/"
  mount -o remount,rw /boot/efi
  cp "$bzImage_file" "$elilo_dir/vmlinuz"
  cp "$initrd_file" "$elilo_dir/initrd.gz"
  mount -o remount,ro /boot/efi
}


for kernel in $( realpath -q --relative-to=/boot /boot/vmlinuz* | sort -u )
do

  case "$kernel" in
    vmlinuz-*-local)    elilo_dir=/boot/efi/EFI/Slackware/local
                        kversion=${kernel#vmlinuz-}
                        ;;
    vmlinuz-generic-*)  elilo_dir=/boot/efi/EFI/Slackware/generic
                        kversion=${kernel#vmlinuz-generic-}
                        ;;
    *)                  echo "aborted."
                        exit 1
                        ;;
  esac
  bzImage_file=/boot/$kernel
  initrd_file=/boot/initrd-$kversion.gz

  o_md5=$(md5sum "$elilo_dir/vmlinuz")
  n_md5=$(md5sum "/boot/$kernel")

  if [ "${o_md5%% *}" != "${n_md5%% *}" ]; then
    echo "$kernel: OUT OF DATE - updating ELILO boot files.,."
    do_update
  else
    echo "$kernel: OK"
  fi

done

################################################################ end. #
The remounting of /boot/efi is a bit quick and dirty. I really should check/restore its current state before/after doing the update, but I never got around to that as I always keep it 'ro'.


For this to work, I subdivide my /boot/efi/EFI/Slackware like this:
Code:
/boot/efi/EFI/Slackware/
├── elilo.conf
├── elilo.efi
├── generic
│** ├── initrd.gz
│** └── vmlinuz
├── local
│** ├── initrd.gz
│** └── vmlinuz
...
Before writing that, the other option I considered was to add a mkinitrd invocation to the kernel package's doinst.sh, but I decided I didn't like that idea (my -local packages are kernel and modules combined so that would have worked for them, but slackware splits them into two packages and the modules might not have been installed when that doinst.sh runs)

Last edited by GazL; 01-24-2019 at 05:31 AM.
 
1 members found this post helpful.
Old 01-24-2019, 09:07 AM   #2705
AlexSlack
Member
 
Registered: Jul 2012
Location: El Salvador
Distribution: Slackware-current
Posts: 38

Rep: Reputation: 21
Question Huge Kernel

Quote:
Originally Posted by Didier Spaier View Post
Maybe in a not-so-distant future we can get rid of the huge kernel and have the initrd automatically generated after each upgrade of the kernel shipped by Slackware?
On some computers after installation I just run eliloconfig, if there is no initrd.gz on /boot it does not generate code on elilo.conf for initrd, so I just need to copy kernel-huge on every update to efi partition. On older computers I just run lilo after kernel update since I am using huge kernel.

I am needing initrd is only on servers with new hardware, Is there any issue using huge kernel?

Thanks.
 
Old 01-24-2019, 11:09 AM   #2706
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,779

Rep: Reputation: Disabled
Quote:
Originally Posted by AlexSlack View Post
Is there any issue using huge kernel?
No, most of the time.

However, there are cases when more than one kernel driver claim a device, and it can happen that the one that gets it is not the one you would prefer.

Also a generic kernel is lighter that a huge one (read: needs less space in RAM once loaded), even if you add the weight of the loaded kernel modules. This often doesn't matter, but can in some use cases.

But installing just one generic kernel (maybe two if you want a backup in case the newest fails to boot) is easier to manage, at least if the new initrd is automatically built and installed, as allowed by the last change.

Also, if this allows to a have less symlinks in /boot there is another benefit for grub users which is to generate less redundant boot entries in grub.cfg whenever you run update-grub or directly grub-config.

As an aside, the last Slint that I am testing fails to boot on a machine in UEFI mode using eLiLo (as I did until now), both in a VM (I have tried using qemu as well as VirtualBox) and in bare metal, and this stands for both the installer and the installed system, so I think that I will have to use grub only when in UEFI mode from now.

I don't know if this issue with eLiLo is linked to the size of the initrd (admittedly huge for Sint's installer) or of the kernel I use (tried both 4.19.16 and 4.19.17) or something else, but am not sure I can afford the time needed to investigate then (maybe?) solve this issue.

Last edited by Didier Spaier; 01-24-2019 at 11:12 AM.
 
2 members found this post helpful.
Old 01-24-2019, 09:02 PM   #2707
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,869

Rep: Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584Reputation: 3584
Quote:
Originally Posted by Didier Spaier View Post
As an aside, the last Slint that I am testing fails to boot on a machine in UEFI mode using eLiLo (as I did until now), both in a VM (I have tried using qemu as well as VirtualBox) and in bare metal, and this stands for both the installer and the installed system, so I think that I will have to use grub only when in UEFI mode from now.

I don't know if this issue with eLiLo is linked to the size of the initrd (admittedly huge for Sint's installer) or of the kernel I use (tried both 4.19.16 and 4.19.17) or something else, but am not sure I can afford the time needed to investigate then (maybe?) solve this issue.
I am running 14.2 with a 4.19.12 generic kernel (using Pat's config) and an initrd that was generated with /usr/share/mkinitrd/mkinitrd_command_generator.sh that comes in at 7.3MB using elilo (stock version 3.16, although, I replaced eliloconfig with the one from -current since I was installing on an NVMe device) on UEFI and I haven't ran into any issues.

If you think it may be tied to newer 4.19 kernels than 4.19.12, I can try to find a time to build and test those... (probably won't happen until at least this weekend).
 
Old 01-25-2019, 04:59 AM   #2708
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,701

Rep: Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665
meson-0.49.1:

https://github.com/mesonbuild/meson/...-0.49.1.tar.gz
 
Old 01-25-2019, 11:08 AM   #2709
AlexSlack
Member
 
Registered: Jul 2012
Location: El Salvador
Distribution: Slackware-current
Posts: 38

Rep: Reputation: 21
Post

Quote:
Originally Posted by Didier Spaier View Post
As an aside, the last Slint that I am testing fails to boot on a machine in UEFI mode using eLiLo (as I did until now), both in a VM (I have tried using qemu as well as VirtualBox) and in bare metal, and this stands for both the installer and the installed system, so I think that I will have to use grub only when in UEFI mode from now.
I use Slackware current on VirtualBox, the EFI implementation is not saving the permanent data so if I want to use EFI boot I have to copy elilo executable as EFI/BOOT/BOOTX64.EFI instead of EFI/Slackware/elilo.efi and copy the configuration and kernel to EFI/BOOT on the efi partition (I think is easier than UEFI scripts), this is a work around on virtual machines (was the same with qemu) the only backward is that you cant have multiple efi boot (unless you do it with elilo) but it is a very rare configuration on a virtual machines.

References:
https://forums.virtualbox.org/viewtopic.php?t=63225
https://forums.virtualbox.org/viewtopic.php?t=61970
 
1 members found this post helpful.
Old 01-25-2019, 11:35 AM   #2710
TurboBlaze
Member
 
Registered: Jan 2018
Location: Russian Federation, Lipetsk region, Dankov
Distribution: Porteus
Posts: 45

Rep: Reputation: Disabled
xdg-open fails to open URLs in Slackware-current with LXDE

xdg-open (xdg-utils-1.1.3-noarch-1.txz) fails to open URLs in Slackware-current with LXDE
For example try in LXTerminal (LXDE) to open http://www.slackware.com
Code:
/usr/bin/xdg-open http://www.slackware.com
I have done patch for fix this bug
Code:
--- /usr/bin/xdg-open	2018-05-16 20:39:00.000000000 +0000
+++ /tmp/xdg-open	2019-01-25 20:16:01.165768339 +0000
@@ -941,12 +941,6 @@
     # pcmanfm only knows how to handle file:// urls and filepaths, it seems.
     if pcmanfm --help >/dev/null 2>&1 -a is_file_url_or_path "$1"; then
         local file="$(file_url_to_path "$1")"
-
-        # handle relative paths
-        if ! echo "$file" | grep -q ^/; then
-            file="$(pwd)/$file"
-        fi
-
         pcmanfm "$file"
     else
         open_generic "$1"
Thanks to https://ask.fedoraproject.org/en/que...fedora-27lxde/
Attached Files
File Type: txt xdg-open.txt (521 Bytes, 0 views)
 
Old 01-25-2019, 12:48 PM   #2711
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,701

Rep: Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665
gnutls-3.6.6:

https://lists.gnupg.org/pipermail/gn...ry/004484.html
https://www.gnupg.org/ftp/gcrypt/gnu...s-3.6.6.tar.xz
 
Old 01-25-2019, 01:10 PM   #2712
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,779

Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
If you think it may be tied to newer 4.19 kernels than 4.19.12, I can try to find a time to build and test those... (probably won't happen until at least this weekend).
Thanks, however I have actually no no idea about what is causing the issue.
 
Old 01-25-2019, 01:19 PM   #2713
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,779

Rep: Reputation: Disabled
Quote:
Originally Posted by AlexSlack View Post
I use Slackware current on VirtualBox, the EFI implementation is not saving the permanent data so if I want to use EFI boot I have to copy elilo executable as EFI/BOOT/BOOTX64.EFI instead of EFI/Slackware/elilo.efi and copy the configuration and kernel to EFI/BOOT on the efi partition (I think is easier than UEFI scripts), this is a work around on virtual machines (was the same with qemu) the only backward is that you cant have multiple efi boot (unless you do it with elilo) but it is a very rare configuration on a virtual machines.

References:
https://forums.virtualbox.org/viewtopic.php?t=63225
https://forums.virtualbox.org/viewtopic.php?t=61970
Thanks, however this is not the issue here, rather with eLiLo the machine, be it virtual or nor, reboots after having loaded the kernel and initrd.

As an aside, for VirtalBox (and any machine that doen't save the UEFI settings) another workaround is to just write the file startup.nsh in EFI in the ESP with just one line, like e.g. EFI\Slackware\elilo.efi

Then if the firmware includes an EFI shell (The VirtualBox VM do), the UEFI shell should be started if everything else fails, and in turn look for statup.nsh in all ESP and when it finds one execute it, which in this case starts the elilo.efi boot manager.

Last edited by Didier Spaier; 01-25-2019 at 02:11 PM.
 
Old 01-28-2019, 12:41 PM   #2714
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,701

Rep: Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665
Again new Thunar-1.8.4:

https://git.xfce.org/xfce/thunar/log/?h=xfce-4.14
http://archive.xfce.org/src/xfce/thu...-1.8.4.tar.bz2
 
1 members found this post helpful.
Old 01-28-2019, 01:03 PM   #2715
TurboBlaze
Member
 
Registered: Jan 2018
Location: Russian Federation, Lipetsk region, Dankov
Distribution: Porteus
Posts: 45

Rep: Reputation: Disabled
Anybody knows why Thunar contains .la files?
Slackware-current does not contains .la files or I'm wrong?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:27 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration