LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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-29-2019, 09:59 PM   #3526
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,913

Rep: Reputation: 668Reputation: 668Reputation: 668Reputation: 668Reputation: 668Reputation: 668

Thats not look nice on lvm2 config time.

Quote:
configure: WARNING: unrecognized options: --enable-applib, --with-lvm1, --with-clvmd-pidfile
configure: WARNING: Support for thin provisioning is limited since some thin provisioning tools are missing!
configure: WARNING: You should also install latest thin_check vsn 0.7.0 (or later) for lvm2 thin provisioning
configure: WARNING: Support for cache is limited since some cache tools are missing!
configure: WARNING: You should install latest cache_check vsn 0.7.0 to use lvm2 cache metadata format 2
 
1 members found this post helpful.
Old 07-30-2019, 02:40 AM   #3527
Lockywolf
Member
 
Registered: Jul 2007
Posts: 574

Rep: Reputation: 167Reputation: 167
In 'extra', in the java/jdk slackbuild, the /etc/profile.d/jdk.sh has the following line:

Code:
export MANPATH="${MANPATH}:${JAVA_HOME}/man"
This line is not really useful there. If anywhere, this may be set in /etc/man-db

This confuses applications which rely on MANPATH. (For example, this can be checked with xman.)
If MANPATH is set, which turns out to be ONLY /usr/lib64/java/man , xman only shows MANs from there.
By default, mandb unsets MANPATH using a cron task:

Code:
/etc/cron.daily/man-db: unset MANPATH
Would it be possible to remove MANPATH from /etc/profile.d/jdk.sh ?
 
Old 07-30-2019, 04:45 AM   #3528
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,255

Rep: Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334
A better fix would be to only add to MANPATH when MANPATH is already set. Wrap it in a if [ -n "$MANPATH" ]; then ... ;fi, or similar.

P.S. If you still want a MANPATH set in profile, add this to somewhere near the top of it:
Code:
MANPATH=$( MANPATH='' /usr/bin/manpath -q )  &&  export MANPATH
I use this.

Last edited by GazL; 07-30-2019 at 04:47 AM.
 
Old 07-30-2019, 08:23 AM   #3529
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,674

Rep: Reputation: 886Reputation: 886Reputation: 886Reputation: 886Reputation: 886Reputation: 886Reputation: 886
Quote:
Originally Posted by GazL View Post
P.S. If you still want a MANPATH set in profile
I use the simple line
Code:
test "${MANPATH}" || export MANPATH=`man -w`
which sets a default MANPATH when there is none there yet.
 
Old 07-30-2019, 01:56 PM   #3530
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware
Posts: 946

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
ImageMagick 6.9.10-58 is out
https://imagemagick.org/download/Ima...9.10-58.tar.lz
https://imagemagick.org/download/Ima...-58.tar.lz.asc
One single change as fas as I can tell from the ChangeLog:
Quote:
2019-07-29 6.9.10-58 Cristy <quetzlzacatenango@image...>
* Release ImageMagick version 6.9.10-58, GIT revision 14723:fffbce8:20190729.
2019-07-27 6.9.10-58 Cristy <quetzlzacatenango@image...>
* Improve GetNextToken() performance.
 
1 members found this post helpful.
Old 07-30-2019, 10:42 PM   #3531
Lockywolf
Member
 
Registered: Jul 2007
Posts: 574

Rep: Reputation: 167Reputation: 167
Can we have the following script added to, perhaps, texinfo package?

/etc/cron.daily/update-texinfo-dir.sh
Code:
#!/bin/sh
cd /usr/info/
rm -rf ./dir
find . -name '*info*' -exec install-info {} ./dir \;
 
Old 07-30-2019, 10:49 PM   #3532
Lockywolf
Member
 
Registered: Jul 2007
Posts: 574

Rep: Reputation: 167Reputation: 167
git 2.22.0

https://codeload.github.com/git/git/tar.gz/v2.22.0
 
Old 07-30-2019, 11:50 PM   #3533
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,558

Original Poster
Rep: Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314
Quote:
Originally Posted by Lockywolf View Post
Can we have the following script added to, perhaps, texinfo package?

/etc/cron.daily/update-texinfo-dir.sh
Code:
#!/bin/sh
cd /usr/info/
rm -rf ./dir
find . -name '*info*' -exec install-info {} ./dir \;
If I were going to do it, I'd do this instead:
Code:
#!/bin/sh
rm -f /usr/info/dir
find /usr/info -type f -name "*info*" -exec install-info {} /usr/info/dir \; 2>/dev/null
 
2 members found this post helpful.
Old 07-31-2019, 01:06 AM   #3534
Lockywolf
Member
 
Registered: Jul 2007
Posts: 574

Rep: Reputation: 167Reputation: 167
Quote:
Originally Posted by rworkman View Post
If I were going to do it, I'd do this instead:
Code:
#!/bin/sh
rm -f /usr/info/dir
find /usr/info -type f -name "*info*" -exec install-info {} /usr/info/dir \; 2>/dev/null
That would be much better. My sh-programming skills are terrible.
 
1 members found this post helpful.
Old 07-31-2019, 06:24 AM   #3535
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 441

Rep: Reputation: 305Reputation: 305Reputation: 305Reputation: 305
Quote:
Originally Posted by rworkman View Post
If I were going to do it, I'd do this instead:
Code:
#!/bin/sh
rm -f /usr/info/dir
find /usr/info -type f -name "*info*" -exec install-info {} /usr/info/dir \; 2>/dev/null
Instead of daily recovering everything, isn't that a job for per-package doinst.sh?

Code:
info_install () {
if [ -x /usr/bin/install-info ]; then
  chroot . /usr/bin/install-info /usr/info/$1.gz /usr/info/dir 2> /dev/null
fi
}

info_install bla.info
 
1 members found this post helpful.
Old 07-31-2019, 07:00 AM   #3536
andrew.46
Senior Member
 
Registered: Oct 2007
Distribution: Slackware
Posts: 1,273

Rep: Reputation: 448Reputation: 448Reputation: 448Reputation: 448Reputation: 448
Problem with Kindle devices under Calibre with the current -current kernel. Details are in this bug report:

https://bugzilla.kernel.org/show_bug.cgi?id=203973

With a simple patch reversion of the following suspect commit:

Code:
commit 5b6619b4d206662f0f6df20fa660f468f56bb75d
Author: Hou Tao <houtao1@huawei.com>
Date:   Tue May 14 15:44:32 2019 -0700

    fs/fat/file.c: issue flush after the writeback of FAT
    
    [ Upstream commit bd8309de0d60838eef6fb575b0c4c7e95841cf73 ]
    
    fsync() needs to make sure the data & meta-data of file are persistent
    after the return of fsync(), even when a power-failure occurs later.  In
    the case of fat-fs, the FAT belongs to the meta-data of file, so we need
    to issue a flush after the writeback of FAT instead before.
    
    Also bail out early when any stage of fsync fails.
    
    Link: http://lkml.kernel.org/r/20190409030158.136316-1-houtao1@huawei.com
    Signed-off-by: Hou Tao <houtao1@huawei.com>
    Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Jan Kara <jack@suse.cz>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
I know the kernel is usually not patched but this is something to be aware of with -current...
 
1 members found this post helpful.
Old 07-31-2019, 09:44 AM   #3537
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,419

Rep: Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571Reputation: 1571
calibre is not included in -current by default
 
Old 07-31-2019, 11:23 AM   #3538
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,558

Original Poster
Rep: Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314Reputation: 1314
Quote:
Originally Posted by franzen View Post
Instead of daily recovering everything, isn't that a job for per-package doinst.sh?

Code:
info_install () {
if [ -x /usr/bin/install-info ]; then
  chroot . /usr/bin/install-info /usr/info/$1.gz /usr/info/dir 2> /dev/null
fi
}

info_install bla.info
Yes, but there's no provision to *ever* run install-info with the --delete option, so the dir file eventually has stale entries.

All that said, I abhor the GNU info system and often kill it entirely on my machines. :-)
 
2 members found this post helpful.
Old 07-31-2019, 11:35 AM   #3539
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,255

Rep: Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334Reputation: 4334
Quote:
Originally Posted by rworkman View Post
All that said, I abhor the GNU info system and often kill it entirely on my machines. :-)
They're a little more bearable when viewed using info mode in emacs rather than the standalone viewer...

but only a little!
 
Old 07-31-2019, 12:37 PM   #3540
Lockywolf
Member
 
Registered: Jul 2007
Posts: 574

Rep: Reputation: 167Reputation: 167
Quote:
Yes, but there's no provision to *ever* run install-info with the --delete option, so the dir file eventually has stale entries.
Also people tend to forget doing the install, or do installs on their own machines, and package wrong 'dir', or even overwrite the 'dir' file completely with an index of a single package.

I mean, GNU info is perhaps not the best system in the world, but any documentation is better than no documentation, and Emacs is referring to it all the time.

Updating the index daily doesn't seem so heavy, and locate is also reindexed, so it should be roughly the same load.
 
  


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 04:50 PM

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

All times are GMT -5. The time now is 04:31 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