LinuxQuestions.org
Help answer threads with 0 replies.
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 08-27-2019, 06:12 AM   #3646
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,674

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872

Quote:
Originally Posted by Lockywolf View Post
Adding a few modules for booting is not going to make things much more complicated,
The problem is: there are still quite a few kernel modules that are mutual exclusive (you can load OR the other) or that break the kernel when the hardware doesn't have support for it.
So "-huge" will be able to boot MOST systems but certainly not all, even with the addition of "a few modules". A custom kernel with "exactly the modules YOUR system needs" is always the best option. My "backup" kernel is a huge one, though
 
Old 08-27-2019, 06:53 AM   #3647
Lockywolf
Member
 
Registered: Jul 2007
Posts: 391

Rep: Reputation: 109Reputation: 109
Quote:
Originally Posted by ehartman View Post
The problem is: there are still quite a few kernel modules that are mutual exclusive (you can load OR the other) or that break the kernel when the hardware doesn't have support for it.
So "-huge" will be able to boot MOST systems but certainly not all, even with the addition of "a few modules". A custom kernel with "exactly the modules YOUR system needs" is always the best option. My "backup" kernel is a huge one, though

Which modules does uas.ko and friends conflict with?

By no means I ever intended to make a kernel bootable everywhere. I don't think that my USB drive is that exotic. Just a conventional piece of hardware from a hight street store.
 
Old 08-27-2019, 09:49 AM   #3648
Lockywolf
Member
 
Registered: Jul 2007
Posts: 391

Rep: Reputation: 109Reputation: 109
I have tried to build a quasihuge kernel in the following way:

1)I made a list of all the modules available in the kernel tree by
Code:
find /lib/modules/$(uname -r)/ -name '*.ko' -exec basename -s '.ko' {} \;
and added semicolons between names

2)Built an initrd tree as
Code:
mkinitrd -c -k $(uname -r) -m $(cat modulelist.txt) -f f2fs -r /dev/sda3
3)Filled the initrd-tree path in /usr/src/linux/.config as

Code:
CONFIG_INITRAMFS_SOURCE="/boot/initrd-tree"
The resulting kernel turned out to be 180 Mb uncompressed and 140 Mb bzipped. Had to enlarge my /boot/efi partition.

As a result: elilo refuses to boot such an enormous kernel, just crashes. Slackware also has grub though, so I installed grub to efi, and indeed, grub can boot the 'enormous kernel' successfully. However, the initramfs as built with mkinitrd and Kconfig, turns out, tries to insmod all the modules out there, regardless of whether they are of any use or not, so the image eventually panicked after loading some conflicting modules.

I don't intend to continue my experiments, as I am quite happy with the default huge kernel. (I only needed to boot from a removable drive once, just to copy the GPT.) However, I believe it is possible to write a SlackBuild which would build a "huge but modularized" image. The key would be to essentially diff huge's and generic's .configs and add all the corresponding modules to the -m key as parameters, and compile the resulting initrd-tree right into the kernel. The result should be fairly equivalent to the old -huge kernel.
 
Old 08-27-2019, 10:31 AM   #3649
Yoga The Yogin
LQ Newbie
 
Registered: Aug 2019
Distribution: Slackware
Posts: 2

Rep: Reputation: Disabled
rc.6 and rc.K NFSv4 umount proposal

Hi guys!

I've encountered an issue when rebooting or shutting down / halting machine with Slackware current. It hangs on message "Unmounting local file systems:" when NFSv4 mounts are not umounted manually before rebooting / halting system. It seems to be an issue with mount output which reports NFSv4 mounts as "type nfs4". The same issue with umount and -t option. mount -t nfs works fine, eg. it mounts NFSv4 mounts without an issue. For me, it helped when I added nfs4 to few lines in rc.6 and rc.K sysvinit scripts.
rc.6:
Code:
--- rc.6	2018-12-30 21:25:19.000000000 +0100
+++ rc.6.patched	2019-08-21 15:34:07.677251421 +0200
@@ -124,7 +124,7 @@
 # Kill any processes (typically gam) that would otherwise prevent
 # unmounting NFS volumes:
 unset FUSER_DELAY
-for dir in $(/bin/mount | grep 'type nfs ' | sed -e 's|.* on ||g' | cut -d ' ' -f 1) ; do
+for dir in $(/bin/mount | grep -e 'type nfs4\? ' | sed -e 's|.* on ||g' | cut -d ' ' -f 1) ; do
   echo "Killing processes holding NFS mount $dir open..."
   # Background this to prevent fuser from also blocking shutdown:
   /usr/bin/fuser -k -M -m "$dir" &
@@ -137,7 +137,7 @@
 
 # Unmount any NFS, SMB, or CIFS filesystems:
 echo "Unmounting remote filesystems:"
-/bin/umount -v -a -l -f -r -t nfs,smbfs,cifs | tr -d ' ' | grep successfully | sed "s/:successfullyunmounted/ has been successfully unmounted./g"
+/bin/umount -v -a -l -f -r -t nfs,nfs4,smbfs,cifs | tr -d ' ' | grep successfully | sed "s/:successfullyunmounted/ has been successfully unmounted./g"
 
 # Try to shut down pppd:
 PS="$(ps ax)"
@@ -156,7 +156,7 @@
 
 # Bring down the networking system, but first make sure that this
 # isn't a diskless client with the / partition mounted via NFS:
-if ! /bin/mount | /bin/grep -q 'on / type nfs' ; then
+if ! /bin/mount | /bin/grep -q -e 'on / type nfs4\?' ; then
   if [ -x /etc/rc.d/rc.inet1 ]; then
     /etc/rc.d/rc.inet1 stop
   fi
and rc.K:
Code:
--- rc.K	2018-07-23 23:35:14.000000000 +0200
+++ rc.K.patched	2019-08-27 16:25:31.495349706 +0200
@@ -60,7 +60,7 @@
 # Kill any processes (typically gam) that would otherwise prevent
 # unmounting NFS volumes:
 unset FUSER_DELAY
-for dir in $(/bin/mount | grep 'type nfs ' | sed -e 's|.* on ||g' | cut -d ' ' -f 1) ; do
+for dir in $(/bin/mount | grep -e 'type nfs4\? ' | sed -e 's|.* on ||g' | cut -d ' ' -f 1) ; do
   echo "Killing processes holding NFS mount $dir open..."
   # Background this to prevent fuser from also blocking shutdown:
   /usr/bin/fuser -k -M -m "$dir" &
@@ -73,7 +73,7 @@
 
 # Unmount any NFS, SMB, or CIFS filesystems:
 echo "Unmounting remote filesystems:"
-/bin/umount -v -a -l -f -r -t nfs,smbfs,cifs | tr -d ' ' | grep successfully | sed "s/:successfullyunmounted/ has been successfully unmounted./g"
+/bin/umount -v -a -l -f -r -t nfs,nfs4,smbfs,cifs | tr -d ' ' | grep successfully | sed "s/:successfullyunmounted/ has been successfully unmounted./g"
 
 # Shut down PCMCIA devices:
 if [ -x /etc/rc.d/rc.pcmcia ] ; then
Feel free to use it (and perhaps add it to next current if you decide so).

Best regards,

Yoga The Yogin
 
2 members found this post helpful.
Old 08-27-2019, 11:10 AM   #3650
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,910

Rep: Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171Reputation: 6171
Quote:
Originally Posted by Lockywolf View Post
Would it be possible to consider them for inclusion in the -huge kernel as "=y"?
No, for the same sort of reason that this wasn't possible:

https://www.linuxquestions.org/quest...ml#post6018914
 
2 members found this post helpful.
Old 08-27-2019, 01:20 PM   #3651
Lockywolf
Member
 
Registered: Jul 2007
Posts: 391

Rep: Reputation: 109Reputation: 109
Quote:
Originally Posted by volkerdi View Post
No, for the same sort of reason that this wasn't possible:

https://www.linuxquestions.org/quest...ml#post6018914
I think that hid is not actually needed, only uas.ko. not sure if it is any better though
 
Old 08-27-2019, 01:33 PM   #3652
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,069

Rep: Reputation: 160Reputation: 160
Quote:
Originally Posted by Lockywolf View Post
I have tried to build a quasihuge kernel in the following way:

1)I made a list of all the modules available in the kernel tree by
Code:
find /lib/modules/$(uname -r)/ -name '*.ko' -exec basename -s '.ko' {} \;
and added semicolons between names

2)Built an initrd tree as
Code:
mkinitrd -c -k $(uname -r) -m $(cat modulelist.txt) -f f2fs -r /dev/sda3
3)Filled the initrd-tree path in /usr/src/linux/.config as

Code:
CONFIG_INITRAMFS_SOURCE="/boot/initrd-tree"
The resulting kernel turned out to be 180 Mb uncompressed and 140 Mb bzipped. Had to enlarge my /boot/efi partition.

As a result: elilo refuses to boot such an enormous kernel, just crashes. Slackware also has grub though, so I installed grub to efi, and indeed, grub can boot the 'enormous kernel' successfully. However, the initramfs as built with mkinitrd and Kconfig, turns out, tries to insmod all the modules out there, regardless of whether they are of any use or not, so the image eventually panicked after loading some conflicting modules.

I don't intend to continue my experiments, as I am quite happy with the default huge kernel. (I only needed to boot from a removable drive once, just to copy the GPT.) However, I believe it is possible to write a SlackBuild which would build a "huge but modularized" image. The key would be to essentially diff huge's and generic's .configs and add all the corresponding modules to the -m key as parameters, and compile the resulting initrd-tree right into the kernel. The result should be fairly equivalent to the old -huge kernel.
The size of 140MB does seem unreasonably large.

For my main working system, I have all the kernel modules (including some 3rd party like nvidia and virtualbox) in a 91MiB lz4 compressed squashfs image. I always load this into memory with the initrd and there has never been a problem.

For my home router whose whole system (slackware64-14.2) is in a 3GiB lzo compressed squashfs image, I load both the system and kernel modules images into memory.

So this might be an ugly but efficient way to do that.
 
Old 08-27-2019, 02:04 PM   #3653
MDKDIO
Member
 
Registered: Mar 2004
Location: Sweden
Distribution: Slackware 14.2 & Current
Posts: 120

Rep: Reputation: 17
Exiv2 0.27.2
https://www.exiv2.org/download.html

(current is at 0.26 at the moment)

Source:
https://www.exiv2.org/builds/exiv2-0.27.2-Source.tar.gz
 
Old 08-27-2019, 03:21 PM   #3654
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,442

Rep: Reputation: 454Reputation: 454Reputation: 454Reputation: 454Reputation: 454
man-db-2.8.7
http://mirrors.up.pt/pub/nongnu/man-...b-2.8.7.tar.xz
 
Old 08-28-2019, 02:17 AM   #3655
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware
Posts: 764

Rep: Reputation: 501Reputation: 501Reputation: 501Reputation: 501Reputation: 501Reputation: 501
Thunderbird, php

Thunderbird 68.0
https://www.thunderbird.net/en-US/th.../releasenotes/
https://ftp.mozilla.org/pub/thunderb....source.tar.xz

PHP 7.3.9
http://us3.php.net/distributions/php-7.3.9.tar.xz

Last edited by mats_b_tegner; 08-28-2019 at 02:53 AM.
 
1 members found this post helpful.
Old 08-28-2019, 05:27 AM   #3656
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,428

Rep: Reputation: Disabled
No hurry. I just posted an issue and others have been reported in the same mailing list.

EDIT: it's a known issue (cf bugs 1490598 and 1577142) which makes really hard for an end-user to add a language pack from TB. Not nice at all.

Last edited by Didier Spaier; 08-28-2019 at 07:48 AM.
 
2 members found this post helpful.
Old 08-28-2019, 07:26 AM   #3657
teoberi
Member
 
Registered: Jan 2018
Location: Romania
Distribution: Slackware64-current (servers) / Ubuntu (workstations)
Posts: 187

Rep: Reputation: 119Reputation: 119
Dovecot release v2.3.7.2
 
1 members found this post helpful.
Old 08-28-2019, 09:16 AM   #3658
fpetrucio
LQ Newbie
 
Registered: Aug 2019
Location: Aracaju, Sergipe - Brazil
Distribution: Slackware
Posts: 8

Rep: Reputation: Disabled
My requests

My requests:
  • Qt 5.13+
  • Qt Creator 4.9+
  • KDE 5 or [ no KDE ]
 
2 members found this post helpful.
Old 08-28-2019, 10:03 AM   #3659
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware
Posts: 764

Rep: Reputation: 501Reputation: 501Reputation: 501Reputation: 501Reputation: 501Reputation: 501
Quote:
Originally Posted by Didier Spaier View Post
No hurry. I just posted an issue and others have been reported in the same mailing list.

EDIT: it's a known issue (cf bugs 1490598 and 1577142) which makes really hard for an end-user to add a language pack from TB. Not nice at all.
Okay, that's good to know. I guess TB 68.0 isn't quite ready for prime time then.
 
1 members found this post helpful.
Old 08-28-2019, 01:53 PM   #3660
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware
Posts: 764

Rep: Reputation: 501Reputation: 501Reputation: 501Reputation: 501Reputation: 501Reputation: 501
Ruby 2.6.4
https://www.ruby-lang.org/en/news/20...-6-4-released/
https://cache.ruby-lang.org/pub/ruby...y-2.6.4.tar.xz
 
  


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 03:55 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
Open Source Consulting | Domain Registration