LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 07-03-2020, 04:29 PM   #5326
Markus Wiesner
Member
 
Registered: Mar 2016
Distribution: Slackware
Posts: 64

Rep: Reputation: 105Reputation: 105

Quote:
Fri Jun 26 19:18:25 UTC 2020
a/sysklogd-2.1.2-x86_64-1.txz: Upgraded.
Make sure to move the .new init script and config into place for this.
Please remove the left over -n in rc.syslog as it's now the only echo in syslogd_start:
Code:
    echo -n "Starting syslogd daemon:  /usr/sbin/syslogd ${SYSLOGD_OPTS}"
 
Old 07-03-2020, 06:01 PM   #5327
Markus Wiesner
Member
 
Registered: Mar 2016
Distribution: Slackware
Posts: 64

Rep: Reputation: 105Reputation: 105
And one more The new PAM enabled mariadb package contains /etc/security/user_map.conf. This should probably also be handled as a .new file like the other files /etc/security/?
 
Old 07-04-2020, 12:55 AM   #5328
BigTig
Member
 
Registered: Aug 2015
Posts: 49

Rep: Reputation: Disabled
Isn't python-setuptools-48.0.0 supposed to install to:
usr/lib64/python3.8
instead of usr/lib/python3.8
on slackware64?
 
Old 07-04-2020, 01:10 AM   #5329
lancsuk
Member
 
Registered: Jul 2019
Location: Burnley / UK
Distribution: Slackware current
Posts: 30

Rep: Reputation: 21
Quote:
Originally Posted by cwizardone View Post
That was quick.
Firefox-78.0.1, has been released.

Thunderbird-68.10.0, is also available.
I've rebuild mozilla-firefox with a couple of patches.

https://bugzilla.mozilla.org/show_bug.cgi?id=1530052

appmenu patch from ubuntu repos
https://launchpad.net/~mozillateam/+....debian.tar.xz

unpatched
Click image for larger version

Name:	Screenshot_2020-07-04_07-01-29.jpg
Views:	88
Size:	271.5 KB
ID:	33568

patched
Click image for larger version

Name:	Screenshot_2020-07-04_07-39-16-appmenu.jpg
Views:	80
Size:	264.8 KB
ID:	33569

I was wondering to have it as an optional feature or better as a fork?
 
2 members found this post helpful.
Old 07-04-2020, 05:21 AM   #5330
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,802

Rep: Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713
Quote:
Originally Posted by BigTig View Post
Isn't python-setuptools-48.0.0 supposed to install to:
usr/lib64/python3.8
instead of usr/lib/python3.8
on slackware64?
the 49.1.0 version, install lib in lib64

https://pypi.org/project/setuptools/
 
1 members found this post helpful.
Old 07-04-2020, 06:37 AM   #5331
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,802

Rep: Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713
libuv-1.38.1:

https://dist.libuv.org/dist/v1.38.1/...v1.38.1.tar.gz
 
Old 07-04-2020, 07:43 AM   #5332
I.G.O.R
Member
 
Registered: Dec 2017
Distribution: Slackware
Posts: 213

Rep: Reputation: 23
The directory "/var/tmp" is usually empty, but in general some applications may use it as temporary directory. For example, I know that "nvi" writes there.

What if to bind-mount it like already was done with "/run"?

tmp-bind-mount-patch.txt

Code:
--- a/scripts/rc.S
+++ b/scripts/rc.S
@@ -370,9 +370,10 @@
 fi
 
 # This should be empty as it's just a mountpoint now:
-rm -rf /var/run/*
-# Bind mount /run to /var/run:
+rm -rf /var/{run,tmp}/*
+
 mount -o bind /run /var/run
+mount -o bind /tmp /var/tmp
 
 # Enable swapping again.  This is needed in case a swapfile is used,
 # as it can't be enabled until the filesystem it resides on has been

Last edited by I.G.O.R; 07-04-2020 at 07:44 AM.
 
Old 07-04-2020, 08:22 AM   #5333
Yoga The Yogin
LQ Newbie
 
Registered: Aug 2019
Distribution: Slackware
Posts: 2

Rep: Reputation: Disabled
FHS

Quote:
Originally Posted by I.G.O.R View Post
The directory "/var/tmp" is usually empty, but in general some applications may use it as temporary directory. For example, I know that "nvi" writes there.

What if to bind-mount it like already was done with "/run"?

Attachment 33570

Code:
--- a/scripts/rc.S
+++ b/scripts/rc.S
@@ -370,9 +370,10 @@
 fi
 
 # This should be empty as it's just a mountpoint now:
-rm -rf /var/run/*
-# Bind mount /run to /var/run:
+rm -rf /var/{run,tmp}/*
+
 mount -o bind /run /var/run
+mount -o bind /tmp /var/tmp
 
 # Enable swapping again.  This is needed in case a swapfile is used,
 # as it can't be enabled until the filesystem it resides on has been
This should be done with care. According to https://en.wikipedia.org/wiki/Filesy...archy_Standard the /var/tmp is supposed to survive reboots. You should find out, if all your software is fine with loosing files from /var/tmp.

Best Regards

Yoga The Yogin
 
3 members found this post helpful.
Old 07-05-2020, 02:56 AM   #5334
I.G.O.R
Member
 
Registered: Dec 2017
Distribution: Slackware
Posts: 213

Rep: Reputation: 23
mkfs.ext4

"64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify."

Is it intentional to omit 64bit option in "/etc/mke2fs.conf"
 
1 members found this post helpful.
Old 07-05-2020, 09:34 AM   #5335
DarkVision
Member
 
Registered: Jul 2007
Posts: 198

Rep: Reputation: Disabled
Just a suggestion, maybe not needed, but discussed years ago here and here and here...

At least the recently released audacity-2.4.2, which is based on cmake, can automatically find the system lib "lame" with this patch (of course you can force audacity to use the system lib...). Without this patch, when using automatic dependency checking, the internal copy will be used even if "lame" is installed. Unsure if this also helps other applications to automatically find the "lame" library...

If interested, here is a patch for the lame.SlackBuild from -current:

Code:
diff -U3 -d -r -N lame.orig/lame.SlackBuild lame/lame.SlackBuild
--- lame.orig/lame.SlackBuild	2019-09-30 01:48:31.148502575 +0200
+++ lame/lame.SlackBuild	2020-07-05 15:47:41.029021668 +0200
@@ -85,6 +85,12 @@
   \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
   -exec chmod 644 {} \+
 
+# Add pkgconfig file.
+cat $CWD/lame.pkgconfig.patch | patch -p1 --verbose || exit 1
+
+# Rebuild configure...
+autoreconf -vif
+
 # Configure:
 CFLAGS="$SLKCFLAGS" \
 ./configure \
@@ -103,6 +109,10 @@
 make $NUMJOBS || make || exit 1
 make install DESTDIR=$PKG || exit 1
 
+# Add pkgconfig file:
+mkdir -p $PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig
+install -m 644 -o root -g root lame.pc $PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig
+
 # Remove .la file:
 rm -f $PKG/usr/lib${LIBDIRSUFFIX}/*.la
 
diff -U3 -d -r -N lame.orig/lame.pkgconfig.patch lame/lame.pkgconfig.patch
--- lame.orig/lame.pkgconfig.patch	1970-01-01 01:00:00.000000000 +0100
+++ lame/lame.pkgconfig.patch	2020-07-05 10:06:01.792658235 +0200
@@ -0,0 +1,36 @@
+--- orj/lame-3.100/configure.in	2017-08-15 23:16:31.000000000 +0800
++++ lame-3.100/configure.in	2018-09-21 20:38:03.424180971 +0800
+@@ -18,7 +18,7 @@
+ dnl FRONTEND_LDADD
+ 
+ AC_PREREQ(2.69)
+-AC_INIT([lame],[3.100],[lame-dev@lists.sf.net])
++AC_INIT([lame],[3.100],[lame-dev@lists.sf.net],[],[http://lame.sourceforge.net])
+ AC_CONFIG_SRCDIR([libmp3lame/lame.c])
+ AC_LANG([C])
+ 
+@@ -1260,6 +1260,8 @@
+ 		 macosx/Makefile \
+ 		 macosx/English.lproj/Makefile \
+ 		 macosx/LAME.xcodeproj/Makefile \
+-		 vc_solution/Makefile])
++		 vc_solution/Makefile \
++		 lame.pc
++])
+ 
+ AC_OUTPUT
+--- /dev/null	2018-08-30 19:17:36.415023615 +0800
++++ lame-3.100/lame.pc.in	2018-09-22 00:08:20.465546180 +0800
+@@ -0,0 +1,12 @@
++prefix=@prefix@
++exec_prefix=@exec_prefix@
++libdir=@libdir@
++includedir=@includedir@
++
++Name: @PACKAGE_NAME@
++Description: High quality MPEG Audio Layer III (MP3) encoder
++URL: @PACKAGE_URL@
++Version: @VERSION@
++Libs: -L${libdir} -lmp3lame
++Libs.private: @CONFIG_MATH_LIB@
++Cflags: -I${includedir}
Attached Files
File Type: txt lame.add_pkgconfig.patch.txt (2.0 KB, 0 views)
 
1 members found this post helpful.
Old 07-05-2020, 12:35 PM   #5336
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,253

Rep: Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950
Quote:
Originally Posted by I.G.O.R View Post
mkfs.ext4

"64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify."

Is it intentional to omit 64bit option in "/etc/mke2fs.conf"
Pulled from /etc/mke2fs.conf:

Code:
[fs_types]
        ext4 = {
                features = has_journal,extent,huge_file,flex_bg,dir_nlink,extra_isize
                auto_64-bit_support = 1
                inode_size = 256
        }
Per man mke2fs.conf:

Code:
       auto_64-bit_support
              This relation is a boolean which specifies whether mke2fs(8) should automatically add the 64bit feature if the number
              of blocks for the file system requires this feature to be enabled.  The resize_inode feature is also  automatically
              disabled since it doesn't support 64-bit block numbers.
So it looks like the system didn't enable 64bit since the number of blocks didn't require it. It is only needed on partitions larger than 16TB. When those partitions exist, mkfs.ext4 will automatically enable 64bit.

What is the context of your message? What were you trying to accomplish that led to that message being issued? That might give Pat some insight on whether it should be forced for everyone, or if admins should make that decision and manually format 16TB or smaller drives as 64bit when needed.
 
Old 07-05-2020, 01:19 PM   #5337
I.G.O.R
Member
 
Registered: Dec 2017
Distribution: Slackware
Posts: 213

Rep: Reputation: 23
Quote:
Originally Posted by bassmadrigal View Post
What is the context of your message? What were you trying to accomplish that led to that message being issued? That might give Pat some insight on whether it should be forced for everyone, or if admins should make that decision and manually format 16TB or smaller drives as 64bit when needed.
Just mkfs.ext4 command issues this warning all the time unless you explicitly specify "-O 64bit". I don't think this behavior is seen in other distros. It's harmless, but annoying.

Last edited by I.G.O.R; 07-05-2020 at 01:20 PM.
 
Old 07-05-2020, 02:20 PM   #5338
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,442

Rep: Reputation: 454Reputation: 454Reputation: 454Reputation: 454Reputation: 454
wireless-regdb-2020.04.29
https://mirrors.edge.kernel.org/pub/...0.04.29.tar.xz
 
Old 07-05-2020, 10:14 PM   #5339
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,253

Rep: Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950Reputation: 4950
Quote:
Originally Posted by I.G.O.R View Post
Just mkfs.ext4 command issues this warning all the time unless you explicitly specify "-O 64bit". I don't think this behavior is seen in other distros. It's harmless, but annoying.
Looks like this is a patch that Pat chose to include right before 14.2 was released due to limitations with certain bootloaders.

Code:
+--------------------------+
Wed May 25 04:20:09 UTC 2016
a/e2fsprogs-1.43-x86_64-2.txz:  Rebuilt.
  Do not use 64-bit by default on ext4, since some bootloaders cannot handle
  it yet.  But use "auto_64-bit_support = 1", which will enable 64-bit if the
  number of blocks for the file system requires the feature to be enabled.
After some sleuthing on google, I found it was due to reports that grub and syslinux were broken when Pat pushed an update to -current (14.2's development) for e2fsprogs that upstream had made 64bit the default for ext4. A later post from Pat stated that it also broke lilo, but according to that post, he's open to patches or reports that the issues are resolved (someone replied in that thread that they were able to boot a 64bit ext4 with lilo using virtualbox, but maybe Pat missed it or he wants more confirmation).
 
Old 07-06-2020, 01:40 AM   #5340
I.G.O.R
Member
 
Registered: Dec 2017
Distribution: Slackware
Posts: 213

Rep: Reputation: 23
Quote:
Originally Posted by bassmadrigal View Post
Looks like this is a patch that Pat chose to include right before 14.2 was released due to limitations with certain bootloaders.

Code:
+--------------------------+
Wed May 25 04:20:09 UTC 2016
a/e2fsprogs-1.43-x86_64-2.txz:  Rebuilt.
  Do not use 64-bit by default on ext4, since some bootloaders cannot handle
  it yet.  But use "auto_64-bit_support = 1", which will enable 64-bit if the
  number of blocks for the file system requires the feature to be enabled.
After some sleuthing on google, I found it was due to reports that grub and syslinux were broken when Pat pushed an update to -current (14.2's development) for e2fsprogs that upstream had made 64bit the default for ext4. A later post from Pat stated that it also broke lilo, but according to that post, he's open to patches or reports that the issues are resolved (someone replied in that thread that they were able to boot a 64bit ext4 with lilo using virtualbox, but maybe Pat missed it or he wants more confirmation).
I don't know about grub, but I can confirm that syslinux (4.07) cannot boot from ext4 formatted with "-O 64bit. As I remember, latest version 6.03 or 6.04 should be ok with it.
 
  


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 09:16 AM.

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